Credential Leakage
Pronunciation: krih-DEHN-chul LEE-kuhj
Definition
Credential leakage is the unintended exposure of passwords, keys, tokens, certificates, or secrets to unauthorized people, systems, or locations. Credential leakage occurs when reusable authentication or authorization material becomes accessible outside its intended control boundary. Sources include source repositories, logs, browser storage, screenshots, support tickets, backups, malware, misconfigured storage, phishing, and insecure messaging.
Overview
Meaning and scope
Credential leakage is the unintended exposure of passwords, keys, tokens, certificates, or secrets to unauthorized people, systems, or locations. Credential leakage occurs when reusable authentication or authorization material becomes accessible outside its intended control boundary. Sources include source repositories, logs, browser storage, screenshots, support tickets, backups, malware, misconfigured storage, phishing, and insecure messaging.
Mechanism and operation
A leaked credential may remain dangerous even without confirmed misuse, especially when it has broad scope, long validity, or access to production. Response requires revoking or rotating the credential, invalidating sessions, reviewing dependent secrets, investigating use, and correcting the exposure path. Prevention includes secret scanning, managed vaults, short-lived identities, least privilege, and avoiding credentials in ordinary application data. For Credential Leakage, the trust decision should establish the unintended exposure of passwords, keys, tokens, certificates, or secrets to unauthorized people, systems, or locations and bind the result to the requested action and protected resource.
Practical payment example
A developer accidentally includes an API key in a public repository. The incident process revokes the key, examines access logs and rotates dependent secrets rather than merely deleting the exposed line.
Operational checks
Teams should test issuance, storage, validation, expiry, revocation, recovery, and privileged override for unintended exposure of passwords, keys, and tokens, rather than checking only a successful request. Logs concerning the Credential Leakage context and unintended exposure of passwords, keys, and tokens should support investigation without exposing reusable secrets or unnecessary personal data.
Distinctions and limits
Deleting the visible copy does not invalidate versions already cloned, cached, indexed, or collected by an attacker. A leaked credential must be revoked or rotated immediately; removing the exposed copy cannot make an already copied secret safe.
Related reading
Related definitions: Credential, authentication.
Example
A developer accidentally includes an API key in a public repository. The incident process revokes the key, examines access logs and rotates dependent secrets rather than merely deleting the exposed line.
Comparison
Deleting the visible copy does not invalidate versions already cloned, cached, indexed, or collected by an attacker. A leaked credential must be revoked or rotated immediately; removing the exposed copy cannot make an already copied secret safe.
Key Takeaway
A leaked credential must be revoked or rotated immediately; removing the exposed copy cannot make an already copied secret safe.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)
- FATF Documentation: Virtual Assets — FATF (2026-07-30)