Ensure scanners are in place to identify and prevent sensitive data in code

MediumLevel 2Automatedgitlab

Description

Detect and prevent sensitive data in code, such as confidential ID numbers, passwords, etc. Having sensitive data in the source code makes it easier for attackers to maliciously use such information. In order to avoid this, designate scanners to identify and prevent the existence of sensitive data in the code.

How it is checked

Audit method: Shell command

shell

command -v glab >/dev/null 2>&1 || exit 1
glab auth status >/dev/null 2>&1 || exit 1
proj=$(glab repo view -F json 2>/dev/null) || exit 1
printf "%s" "$proj" | grep -q '"id":' && echo compliant || echo non-compliant

Expected output: compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Remediation: For every repository in use, designate scanners to identify and prevent sensitive data in code by performing the following: 1. On GitLab, navigate to the main page of the repository. 2. Enable secret detection for this project.

Properties

Operating systems: Any
Tags: devsecopsgitlab
Reference: CIS GitLab Benchmark v1.0.1 - 1.5.1 Ensure scanners are in place to identify and prevent sensitive data in code

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

shell

tmaegis scan --target gitlab --level 2