High-confidence secret in CodeBuild PLAINTEXT environment variable

Severity
Critical
Service
Secrets exposure
Check ID
SECRETS_CODEBUILD_ENV_HIGH

What this check finds

A CodeBuild project PLAINTEXT environment variable matches a high-confidence credential pattern. PLAINTEXT env vars are visible in build logs and readable by any principal with codebuild:BatchGetProjects. Use PARAMETER_STORE or SECRETS_MANAGER types instead.

Passing looks like: No secrets in CodeBuild environment variables.

How to fix it

Change the environment variable type from PLAINTEXT to PARAMETER_STORE or SECRETS_MANAGER in the CodeBuild project configuration and store the value in SSM SecureString or Secrets Manager.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to High-confidence secret in CodeBuild PLAINTEXT environment variable
FrameworkControls
NIST SP 800-53 Rev5 (Moderate)
  • IA-5 Authenticator Management
NIST Cybersecurity Framework 2.0
  • PR.AA-01 Identities and credentials are managed
ISO/IEC 27001:2022 Annex A
  • A.5.17 Authentication information

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More Secrets exposure checks

All Secrets exposure checks

Find out what is actually exposed in your AWS environment.

Connect one AWS account and run your first security assessment.

No credit card · Agentless · Read-only