TMA-GITLAB-2.1.7
Ensure build secrets are limited to the minimal necessary scope
Descripción
Build tools providers offer a secure way to store secrets that should be used during the build process. These secrets will often be credentials used to access other tools, for example for pulling code or for uploading artifacts. Access to these secrets can be defined on various scopes. To protect these critical assets it is important to choose the most restrictive scope necessary. Allowing over permissive access to these secrets may affect on their exposure. For example if a secret is defined in an organization level, and users can create new repositories, there is a scenario where a user can create a new repo and run a controlled build just to exfiltrate these secrets.
Cómo se verifica
Método de auditoría: Revisión manual
Esta recomendación no se puede verificar automáticamente. Un escaneo la lista con estas instrucciones cuando se pasa --include-manual.
In the gitlab-ci.yml file, review the secrets permission scope defined in either a file or in an external secrets manager.
Cómo se corrige
Método de corrección: Guía o parche de infraestructura
In the gitlab-ci.yml file, review the secrets defined in either a file or in an external secrets manager and change over permissive scopes to more restrictive ones based on the required access.
Propiedades
- Sistemas operativos
- Cualquiera
- Etiquetas
- devsecopsgitlab
- Referencia
- CIS GitLab Benchmark v1.0.1 - 2.1.7 Ensure build secrets are limited to the minimal necessary scope