TMA-GITHUB-2.1.1
Ensure each pipeline has a single responsibility
Description
Ensure each pipeline has a single responsibility in the build process. Build pipelines generally have access to multiple secrets depending on their purposes. There are, for example, secrets of the test environment for the test phase, repository and artifact credentials for the build phase ... 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 pipeline, ensure it has only one responsibility in the build process. Expected state: Divide each multi-responsibility pipeline into multiple pipelines, each having a single responsibility with the least privilege. Additionally, create all new pipelines with a sole purpose going forward.
How it is fixed
Fix method: Guidance or infrastructure patch
Divide each multi-responsibility pipeline into multiple pipelines, each having a single responsibility with the least privilege. Additionally, create all new pipelines with a sole purpose going forward.
Properties
- Operating systems
- Any
- Tags
- githubbuild-pipelines
- Reference
- CIS GitHub Benchmark v1.2.0 - 2.1.1 Ensure each pipeline has a single responsibility