Ensure all copies (forks) of code are tracked and accounted for

FaibleNiveau 1Revue manuellegitlab

Description

Track every fork of code and ensure it is accounted for. A fork is a copy of a repository. On top of being a plain copy, any updates to the original repository itself can be pulled and reflected by the fork under certain conditions. A large number of repository copies (forks) become difficult to manage and properly secure. New and sensitive changes can often be pushed into a critical repository without developer knowledge of an updated copy of the very same repository. If there is no limit on doing this, then it is recommended to track and delete copies of organization repositories as needed.

Méthode de vérification

Méthode d'audit: Revue manuelle

Cette recommandation ne peut pas être vérifiée automatiquement. Une analyse la liste avec ces instructions lorsque vous passez --include-manual.

Verify that the following steps are done regularly to track and examine forks. - Navigate to the project home page. - Find the 'Fork' button, and select the number next to it. - Examine the forks listed there.

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

Track forks and examine them by performing the following on a regular basis: - Navigate to the project home page. - Find the 'Fork' button, and select the number next to it. - Examine the forks listed there.

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: devsecopsgitlab
Référence: CIS GitLab Benchmark v1.0.1 - 1.2.5 Ensure all copies (forks) of code are tracked and accounted for