RS.MA-04 Incidents are escalated or elevated as needed
Incidents are escalated or elevated as needed. 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
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Escalation decision logs · SIEM / log platform
periodic reviewEvidence produced at each review
- After action reviews on escalation timing · Document repository
governing documentDocuments that govern the control
- Escalation procedure with named roles · Policy repository / GRC workspace
- Escalation tree tested through drills · Document repository
- Executive notification protocols · Document repository
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
- Escalation tree outdated
- Drills omit night and weekend conditions
- Decision logs incomplete
- Reviews skip escalation analysis
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.MA-03 Incidents are categorized and prioritized · RS.MA-05 The criteria for initiating incident recovery are applied