Secrets detection
Secrets detection articles
Credentials in git history, CI logs and image layers: finding them, rotating them and proving the rotation happened.
Secrets detection finds API keys, tokens and passwords committed to git history or baked into container image layers. These articles cover where leaked credentials hide, what to do in the first hour after one is found, and how to prove the rotation actually happened.
- Security logging: test what leaves your applicationReview security logging with synthetic secrets, export-path checks and failure tests while preserving useful evidence for incident investigation. · Sujan Singh
- Secret rotation: verify every consumer switchedPlan secret rotation around consumer inventory, controlled cutover and revocation evidence so an updated secret does not leave old credentials usable. · Sujan Singh
- Leaked secret response: rotate, trace, then prevent repeatsDeleting a leaked secret from HEAD is not remediation. The response that works: rotate first, trace affected images, keep evidence and gate repeats. · Sujan Singh
- Secrets detection beyond HEAD: git history, CI logs, imagesSecrets detection that only scans HEAD misses real leaks. Where credentials hide in git history, CI logs and image layers, and how to verify them safely. · Sujan Singh
See it on your stack
See connected security in action.
Explore the workflow with your engineering, security and compliance teams. No repository access is needed for the initial demonstration.