TMAegisBeta
More rules for gitlab

GitLab

TMA-GITLAB-1.5.2

Ensure scanners are in place to secure Continuous Integration (CI) pipeline instructions

MediumLevel 2Manual reviewgitlab

Description

Detect and prevent misconfigurations and insecure instructions in CI pipelines Detecting and fixing misconfigurations or insecure instructions in CI pipelines decreases the risk for a successful attack through or on the CI pipeline. The more secure the pipeline, the less risk there is for potential exposure of sensitive data, a deployment being compromised, or external access mistakenly being granted to the CI infrastructure or the source code.

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 every project: - Identify if one or more CI configuration files exist - Review CI configuration files for misconfigurations or insecure instructions - Review whether the absence of any CI configuration is itself a misconfiguration

How it is fixed

Fix method: Guidance or infrastructure patch

For every project identified during the Audit as having misconfigured or insecure CI instructions: - Update the CI instructions - Consider using Scan Execution Policies at the project or group level to enforce security scans - Consider using the Compliance Framework feature to enforce pipeline configuration - Consider procuring and enabling a CI instructions scanning tool to identify and prevent misconfigurations and insecure instructions and scans all CI pipelines.

Properties

Operating systems
Any
Tags
ci-cddevsecopsgitlab
Reference
CIS GitLab Benchmark v1.0.1 - 1.5.2 Ensure scanners are in place to secure Continuous Integration (CI) pipeline instructions