TMAegis
More rules for gitlab

GitLab

TMA-GITLAB-1.5.3

Ensure scanners are in place to secure Infrastructure as Code (IaC) instructions

MediumLevel 2Manual reviewgitlab

Description

Detect and prevent misconfigurations or insecure instructions in Infrastructure as Code (IaC) files, such as Terraform files. Detecting and fixing misconfigurations and/or insecure instructions in IaC (Infrastructure as Code) 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 can 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.

Audit: For every repository that holds IaC instructions files, verify that a scanning tool such as GitLab's Infrastructure as Code scanning is configured to identify and prevent misconfigurations and insecure instructions. 1. On GitLab, navigate to the main page of the repository. 2. Review the CI pipeline configuration to verify that IaC scanning has been enabled on this project.

How it is fixed

Fix method: Guidance or infrastructure patch

Remediation: For every repository that holds IaC instructions files, configure GitLab's Infrastructure as Code scanning (or another IaC scanning tool) to identify and prevent misconfigurations and insecure instructions. 1. On GitLab, navigate to the main page of the repository. 2. Enable IaC scanning for this project.

Properties

Operating systems
Any
Tags
devsecopsgitlab
Reference
CIS GitLab Benchmark v1.0.1 - 1.5.3 Ensure scanners are in place to secure Infrastructure as Code (IaC) instructions