RS.CO-02 Internal and external stakeholders are notified of incidents
Internal and external stakeholders are notified of incidents. Control from NIST Cybersecurity Framework 2.0 framework, domain: RS - Respond.
5
artefacts
1
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Notification audit trail · SIEM / log platform
periodic reviewEvidence produced at each review
- Customer notification records · Document repository
governing documentDocuments that govern the control
- Incident notification policy and timing matrix · Policy repository / GRC workspace
- Internal stakeholder communication templates · Policy repository / GRC workspace
- Regulator notification templates with jurisdiction matrix · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Notification timing tracked but missed
- Templates generic across jurisdictions
- Customer notification delayed by legal review
- Audit trail incomplete
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 sheetRS.AN-08 An incident's magnitude is estimated and validated · RS.CO-03 Information is shared with designated internal and external stakeholders