Ensure all code projects are tracked for changes in visibility status

FaibleNiveau 1Revue manuellegitlab

Description

Ensure every change in visibility of projects is tracked. Visibility of projects determines who can access a project and/or fork it: anyone, designated users, or only members of the organization. If a private project becomes public, this may point to a potential attack, which can ultimately lead to data loss, the leaking of sensitive information, and finally to a supply chain attack. It is crucial to track these changes in order to prevent such incidents.

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.

Méthode de correction

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

Ensure that every change in project visibility is investigated by performing the following regularly. As an administrator: - Navigate to the Admin Area. - In the sidebar, select Monitoring > Audit Events. - Review the log for Actions with the content 'Changed visibility from Private to Public' or 'Changed visibility from Internal to Public'. - Ensure every change is reasonable and secure and is investigated if it is not. - (Optional) Use Instance Audit Event Streaming (https://docs.gitlab.com/ee/administration/audit_event_streaming/#instance- streaming-destinations) to send visibility change events to a third party alerting tool. Integrate these alerts in to your change management and/or incident response processes.

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: devsecopsgitlab
Référence: CIS GitLab Benchmark v1.0.1 - 1.2.6 Ensure all code projects are tracked for changes in visibility status