Are emergency (break-glass) accounts in place, protected, monitored and tested at least twice a year?
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Question 8 of the assessment asks: Are emergency (break-glass) accounts in place, protected, monitored and tested at least twice a year? If your identity provider fails or a policy locks everyone out, a tested emergency account is the only way back in.
Start the assessment ยท All 40 questions
Why it matters
If your identity provider fails or a policy locks everyone out, a tested emergency account is the only way back in.
Answers and what each is worth
| Answer | Value |
|---|---|
| Yes, protected, alerted and tested | 1 |
| Exist but untested or unmonitored | 0.5 |
| No or not known | 0 |
How to check it in each cloud
- AWS
- Check that the break-glass IAM users or roles exist, that a CloudWatch or EventBridge alert fires on their use, and note the last test date.
- Azure
- Check that two cloud-only emergency accounts are excluded from Conditional Access policies by design and have a sign-in alert in Azure Monitor.
- Google Cloud
- Check for a documented emergency super administrator in Cloud Identity with hardware keys stored offline, and a Cloud Logging alert on its use.
The fix
Create two emergency accounts with long unique credentials, alert on every sign-in and test them twice a year. Effort: low.
Where it comes from
- Microsoft cloud security benchmark PA-5: Set up emergency access
- NIST SP 800-53 Rev. 5 AC-2: source
Related pages
Sources
- Microsoft cloud security benchmark PA-5, read 16 Nov 2026
- NIST SP 800-53 Rev. 5 AC-2, read 16 Nov 2026
Last reviewed 16 Nov 2026.