Check ID:
Provider: GitHub
Service:
Severity: HIGH
Categories:
Resource type:
repository_secret_scanning_enabledProvider: GitHub
Service:
repositorySeverity: HIGH
Categories:
secretsResource type:
NotDefinedWhat this check verifies
GitHub repository configuration for secret scanning-which detects secrets (API keys, tokens, passwords) in commits and Git history-is evaluated to determine if detection is active.Risk
Without secret scanning, exposed credentials can persist unnoticed, enabling:- Unauthorized access to cloud and third-party services
- Supply-chain compromise via tampered pipelines
- Data exfiltration and repo takeover
Recommendation
Enable secret scanning (and push protection where available) across repositories.- Store secrets in a dedicated secrets manager, never in code
- Define custom patterns and enable generic detection for org-specific secrets
- Rotate and revoke exposed credentials quickly
- Enforce least privilege and add defense-in-depth monitoring
Remediation
- CLI
- Terraform
- Dashboard steps
References
Where this check fires
This check runs on every scheduled scan against your GitHub account. Findings appear at Cloud Security → Findings filterable byCheck ID = repository_secret_scanning_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to GitHub checks