TMA-GITHUB-1.5.1
Ensure scanners are in place to identify and prevent sensitive data in code
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. security_and_analysis.secret_scanning.status must be enabled (admin access needed to read it). Uses the GitHub REST/GraphQL API through gh api (read-only). The repository comes from GH_REPO or the current git checkout (gh's {owner}/{repo} resolution, GH_HOST for GitHub Enterprise Server); the organization comes from GH_ORG (default: the repository owner). Fails when gh is missing or unauthenticated (gh auth login or GH_TOKEN); organization settings and branch protection need an owner/admin token.
How it is checked
Audit method: Shell command
command -v gh >/dev/null 2>&1 || exit 1
gh auth status >/dev/null 2>&1 || exit 1
info=$(gh api 'repos/{owner}/{repo}' --jq '.full_name + " " + .default_branch' 2>/dev/null) || exit 1
R=${info% *}; B=${info#* }
[ -n "$R" ] && [ -n "$B" ] || exit 1
v=$(gh api "repos/$R" --jq '.security_and_analysis.secret_scanning.status' 2>/dev/null) || exit 1
[ "$v" = enabled ] && echo compliant- Expected output
compliant
How it is fixed
Fix method: Guidance or infrastructure patch
Settings > Code security > Secret scanning > Enable (gh api -X PATCH repos/<owner>/<repo> -f security_and_analysis[secret_scanning][status]=enabled).
Properties
- Operating systems
- Any
- Tags
- githubsource-code
- Reference
- CIS GitHub Benchmark v1.2.0 - 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.
tmaegis scan --target github --level 2