RS.MI-01 Incidents are contained
Incidents are contained. Control from NIST Cybersecurity Framework 2.0 framework, domain: RS - Respond.
Source: NIST CSF 2.0, RS.MI-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
- Network isolation tooling deployment evidence · Source control / CI pipeline
periodic reviewEvidence produced at each review
- Containment effectiveness review post incident · Document repository
- Approval records for containment actions with business impact · Document repository
governing documentDocuments that govern the control
- Containment playbook by incident type · Document repository
- Account suspension workflow · Policy repository / GRC workspace
First move
Common gaps auditors find
- Containment delayed pending approvals
- Tooling exists but operators untrained
- Effectiveness review absent
- Approvals not captured
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-05 The criteria for initiating incident recovery are applied · RS.MI-02 Incidents are eradicated