Ensure changes to pipeline files are tracked and reviewed

LowLevel 1Manual reviewgitlab

Description

Track and review changes to pipeline files. Pipeline files are sensitive files. They have the ability to access sensitive data and control the build process, thus it is just as important to review changes to pipeline files as it is to verify source code. Malicious actors can potentially add harmful code to these files, which may lead to sensitive data exposure and hijacking of the build environment or artifacts.

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 file, ensure changes to it are being tracked and reviewed. - On the left sidebar, select Code > Repository. - Check if a .gitlab-ci.yml file is at the root of your repository - If it exists, all changes will be tracked via Git. - In the upper-right corner, select History to review the history of the gitlab-ci.yml file

How it is fixed

Fix method: Guidance or infrastructure patch

For each pipeline file, track changes to it and review them. - 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: ci-cddevsecopsgitlab
Reference: CIS GitLab Benchmark v1.0.1 - 2.3.4 Ensure changes to pipeline files are tracked and reviewed