TMA-GITLAB-2.3.1
Ensure all build steps are defined as code
Description
Use pipeline as code for build pipelines and their defined steps. 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 back to a previous pipeline configuration in order to pinpoint the affected change should a malicious incident occur.
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.
Verify that all build steps are defined as code and stored in a version control system. - On the left sidebar, select Code > Repository. - Check if a .gitlab-ci.yml file is at the root of your repository
How it is fixed
Fix method: Guidance or infrastructure patch
Convert pipeline instructions into code-based syntax and upload them to the organization's version control platform. - On the left sidebar, select Code > Repository. - Above the file list, select the branch you want to commit to. If you’re not sure, leave master or main. Then select the plus icon () and New file: - For the Filename, type .gitlab-ci.yml. - Select Commit changes.
Properties
- Operating systems
- Any
- Tags
- devsecopsgitlab
- Reference
- CIS GitLab Benchmark v1.0.1 - 2.3.1 Ensure all build steps are defined as code