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.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
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
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
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