TMAegis
More rules for gitlab

GitLab

TMA-GITLAB-5.1.5

Scan Infrastructure as Code (IaC)

MediumLevel 2Manual reviewgitlab

Description

Detect and prevent misconfigurations or insecure instructions in Infrastructure as Code (IaC) files, such as Terraform files. Infrastructure as Code (IaC) files are used for production environment and application deployment. These are sensitive parts of the software supply chain because they are always in touch with customers, and thus might affect their opinion of or trust in the product. Attackers often target these environments. Detecting and fixing misconfigurations and/or insecure instructions in IaC files decreases the risk for data leak or data theft. It is important to secure IaC instructions in order to prevent further problems of deployment, exposed assets, or improper configurations, which might ultimately lead to easier ways to attack and steal organization data.

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 Infrastructure as Code (IaC) instructions file, verify that scanners are set to identify and prevent misconfigurations and insecure instructions.

How it is fixed

Fix method: Guidance or infrastructure patch

For every Infrastructure as Code (IaC) instructions file, set scanners to identify and prevent misconfigurations and insecure instructions.

Properties

Operating systems
Any
Tags
devsecopsgitlab
Reference
CIS GitLab Benchmark v1.0.1 - 5.1.5 Scan Infrastructure as Code (IaC)