RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is…
The incident response plan is executed in coordination with relevant third parties once an incident is declared
Source: NIST CSF 2.0, RS.MA-01. 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
- Vendor activation log during real incidents · SIEM / log platform
periodic reviewEvidence produced at each review
- Retainer contract evidence for IR vendor · Vendor register / contract repository
- Joint exercise records with the IR vendor · Vendor register / contract repository
governing documentDocuments that govern the control
- Incident response plan with third party invocation · Vendor register / contract repository
- Coordination procedure with law enforcement · Policy repository / GRC workspace
First move
Common gaps auditors find
- Retainer in place but contact path untested
- Coordination with law enforcement absent
- Joint exercises infrequent
- Activation log 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.CO-03 Information is shared with designated internal and external stakeholders · RS.MA-02 Incident reports are triaged and validated