Infrastructure
Secret leakage
Exposed credentials, secret leakage
Passwords, access tokens, certificates or private keys are exposed through source code, logs or repositories.
Fiche de sensibilisationPrête à diffuser à vos équipes ou clients
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
Secrets copied to insufficiently protected locations can be discovered and abused quickly.
REAL-WORLD EXAMPLE
« A production API token remains accessible in a Git repository's commit history. »
Typical sequence
- 1Publish or leak the secret
- 2A third party discovers it
- 3Access protected systems or resources
Warning signs
- Credentials included in a commit
- Token values present in logs
- Secret-scanner alert
How to protect yourself
- Use a dedicated secrets manager
- Scan changes before committing
- Prefer temporary identities and short-lived credentials
If you think you are affected
Immediately revoke and replace the exposed secret; removing it from a file does not invalidate an already disclosed credential.
Last updated: 8 October 2026