domains / families / security / implementing-secret-scanning-with-gitleaks
implementing-secret-scanning-with-gitleaks
separate
'This skill covers implementing Gitleaks for detecting and preventing
When to use
- When developers may accidentally commit API keys, passwords, tokens, or private keys to repositories
- When establishing pre-commit gates that prevent secrets from entering the git history
- When scanning existing repository history for previously committed secrets that need rotation
- When compliance requirements mandate secret detection across all source code repositories
- When migrating from manual secret audits to automated continuous scanning
When not to use
- detecting secrets in running applications or memory
- managing secrets after detection
- scanning container images
Skill page
Source