IR-2 Preparation - setup incident notification
Set up incident notification so security alerts from the cloud platform and from the environment reach the correct contact in the incident response organisation.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), IR-2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Test records confirming notifications are received · Document repository
- Review cadence for contact accuracy · Document repository
governing documentDocuments that govern the control
- Security contact configured on each subscription or account · Policy repository / GRC workspace
- Distribution list or on-call rota behind that contact · Document repository
First move
Common gaps auditors find
- contact set to an individual who has left
- notifications routed to a mailbox with no on-call coverage
- contacts configured on some subscriptions only
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetIR-1 Preparation - update incident response plan and handling process · IR-3 Detection and analysis - create incidents based on high-quality alerts