RS.MI-02 Incidents are eradicated
Incidents are eradicated. Control from NIST Cybersecurity Framework 2.0 framework, domain: RS - Respond.
Source: NIST CSF 2.0, RS.MI-02. 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
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
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