RS.MI-01 Incidents are contained
Incidents are contained. Control from NIST Cybersecurity Framework 2.0 framework, domain: RS - Respond.
5
artefacts
0
held by a system
3
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
none for this control
periodic reviewEvidence produced at each review
- Network isolation tooling deployment evidence · Source control / CI pipeline
- 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
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
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