2.3.1 Ensure all build steps are defined as code
ID |
cis_sscs/steps_as_code |
Severity |
low |
Category |
build_pipelines/pipeline_instructions |
Levels |
|
Optional |
false |
Tags |
build, pipeline, slsa-1, slsa-2, slsa-3, slsa-4, supply-chain |
Rationale
Storing pipeline instructions as code in a version control system means automation of the build steps and less room for human error, which could potentially lead to a security breach.
Additionally, it creates the ability to revert to a previous pipeline configuration in order to pinpoint the affected change should a malicious incident occur.