RS.MI-02 Incidents are eradicated
Incidents are eradicated. Control from NIST Cybersecurity Framework 2.0 framework, domain: RS - Respond.
5
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
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
- Malware removal verification records · Endpoint management (MDM / EDR)
- Persistence removal evidence · Document repository
governing documentDocuments that govern the control
- Eradication procedure by attack technique · Policy repository / GRC workspace
- Re imaging and rebuilding policy · Policy repository / GRC workspace
- Post eradication validation testing · Document repository
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
- Eradication relies on antivirus signatures only
- Persistence checks superficial
- Re imaging avoided for time pressure
- Validation testing not retained
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 sheet