Break-glass access
A tightly controlled emergency path to privileged access when normal authentication or approval systems are unavailable.
Break-glass accounts or procedures exist for when the IdP is down, conditional access is misconfigured, or an incident needs immediate admin action. Typical controls: a small number of accounts excluded from normal SSO dependencies, phishing-resistant credentials (FIDO2 keys) held in a safe, split knowledge or dual control, and alerting on every use.
The tension is that break-glass bypasses the controls you built. So it must be loud: page the security team on login, record the session, require a written justification afterwards, and rotate credentials after use.
Failures: break-glass accounts nobody tested that fail when needed, accounts that quietly became daily admin logins, and credentials stored in the same system that is down.
Learn it properly
Also used in
- Secure design principles that still holdSecEng · Foundations of Security EngineeringFree
- Design an SSO identity providerHLD · Design problems: Access & identityFree
- Workload identity and federationSecEng · Identity & Access EngineeringPro
- Cloud IAM: least privilege that survives contact with teamsSecEng · Cloud & Platform SecurityPro
- Kubernetes security: hard to get in, harder to get outSecEng · Cloud & Platform SecurityPro
- Data protection: KMS, envelope encryption, tokenisationSecEng · Cloud & Platform SecurityPro
- Incident response engineeringSecEng · Detection & Response EngineeringPro
- Forensics and evidence engineeringSecEng · Detection & Response EngineeringPro