Do alerts fire, and reach a person, for root or global administrator sign-ins, policy changes, new keys and disabled logging?
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Question 38 of the assessment asks: Do alerts fire, and reach a person, for root or global administrator sign-ins, policy changes, new keys and disabled logging? Logs that nobody reads do not shorten an attack, while alerts on a handful of events do.
Start the assessment ยท All 40 questions
Why it matters
Logs that nobody reads do not shorten an attack, while alerts on a handful of events do.
Answers and what each is worth
| Answer | Value |
|---|---|
| Yes, all four route to on-call | 1 |
| Some are alerted | 0.5 |
| No or not known | 0 |
How to check it in each cloud
- AWS
- Check EventBridge or CloudWatch metric filters for root login, IAM policy changes, CreateAccessKey and StopLogging, and their targets.
- Azure
- Check Azure Monitor alert rules and Entra ID Protection notifications for administrator sign-ins and role changes.
- Google Cloud
- Check Cloud Logging log-based alerts for SetIamPolicy, service account key creation and sink changes.
The fix
Create alerts for those four events and send them to the on-call channel. Effort: medium.
Where it comes from
- Microsoft cloud security benchmark LT-2: Enable threat detection for identity and access management
- NIST SP 800-53 Rev. 5 AU-6: source
Related pages
Sources
- Microsoft cloud security benchmark LT-2, read 16 Nov 2026
- NIST SP 800-53 Rev. 5 AU-6, read 16 Nov 2026
Last reviewed 16 Nov 2026.