GitLab
TMA-GITLAB-1.2.5
Ensure all copies (forks) of code are tracked and accounted for
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.
How it is checked
Audit method: Manual review
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.
How it is fixed
Fix method: Guidance or infrastructure patch
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.
Properties
- Operating systems
- Any
- Tags
- devsecopsgitlab
- Reference
- CIS GitLab Benchmark v1.0.1 - 1.2.5 Ensure all copies (forks) of code are tracked and accounted for