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.
Source: NIST CSF 2.0, RS.MA-04. 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 NIST CSF 2.0 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
- 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
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