TMA-GITHUB-2.1.7
Ensure build secrets are limited to the minimal necessary scope
Description
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.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --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.
How it is fixed
Fix method: Guidance or infrastructure patch
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.
Properties
- Operating systems
- Any
- Tags
- githubbuild-pipelines
- Reference
- CIS GitHub Benchmark v1.2.0 - 2.1.7 Ensure build secrets are limited to the minimal necessary scope