Ensure build secrets are limited to the minimal necessary scope

AltaNivel 2Revisión manualgithub

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. 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 ... Reported as a manual review item: no reliable read-only gh api check exists for this control.

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.

For each build tool in use, review the secrets defined and the permission scopes they are assigned. Expected state: For each build tool, review the secrets defined and their permissions scope and change over permissive scopes to more restrictive ones based on the required access.

Cómo se corrige

Método de corrección: Guía o parche de infraestructura

For each build tool, review the secrets defined and their permissions scope and change over permissive scopes to more restrictive ones based on the required access.

Propiedades

Sistemas operativos: Cualquiera
Etiquetas: githubbuild-pipelines
Referencia: CIS GitHub Benchmark v1.2.0 - 2.1.7 Ensure build secrets are limited to the minimal necessary scope