NIST Cybersecurity Framework 2.0
RS - Respond

NIST Cybersecurity Framework 2.0 NIST-CSF-RS.MI-02: Incidents are eradicated

Incidents are eradicated. Control from NIST Cybersecurity Framework 2.0 framework, domain: RS - Respond.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 49 controls across 26 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 4 controls

  • IR-2 Incident Response Training
  • IR-4 Incident Handling
  • IR-4(1) Automated Incident Handling Processes
  • SI-3 Malicious Code Protection

FedRAMP Moderate · 4 controls

  • IR-2 Incident Response Training
  • IR-4 Incident Handling
  • IR-4(1) Automated Incident Handling Processes
  • SI-3 Malicious Code Protection

ISO 27001:2022 · 4 controls

  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 8.7 Protection against malware
  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 4 controls

  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence
  • 8.7 Protection against malware
  • ISM-0917 Handling malicious code infections
  • ISM-1213 Traffic capture after intrusion remediation
  • ISM-1732 Coordinated remediation during a planned outage

NIST SP 800-53 Rev 5 · 3 controls

SOC 2 · 3 controls

  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC7.5 CC7.5 Recovering from security incidents
  • ASD37-16 Antivirus software with signatures (Limited)
  • ASD37-36 System recovery capabilities (Very Good)
  • SEC04-BP04 Initiate remediation for non-compliant resources
  • SEC10-BP02 Develop incident management plans

HIPAA Security Rule · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

PCI DSS 4.0 · 2 controls

  • 10.7.3 10.7.3 Respond promptly to critical security control failures
  • 5.2.2 5.2.2 Anti-malware detects and handles all known malware

APRA CPS 234 · 1 control

  • ASBv3-IR-6 Containment, eradication and recovery - automate the incident handling

C5 (Germany) · 1 control

CIS Controls v8 · 1 control

  • CIS-10.1 Deploy and Maintain Anti-Malware Software

CMMC 2.0 · 1 control

ISO 27701:2019 · 1 control

  • 6.13.1 Management of information security incidents and improvements

NIS2 Directive · 1 control

  • RS.MI-2 RS.MI-2: Incidents are mitigated
  • RS.MI-2 RS.MI-2: Incidents are mitigated

NIST SP 800-172 · 1 control

  • 3.14.4e Refresh Systems and Components from a Trusted Baseline
  • RS.MI-02 RS.MI-02 Incidents eradicated across all affected hosts and services

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in RS - Respond

You are reading one control. How much of NIST Cybersecurity Framework 2.0 have you already done?

NIST Cybersecurity Framework 2.0 NIST-CSF-RS.MI-02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST Cybersecurity Framework 2.0 your existing evidence covers. Hold ISO 27001:2022 and 73 of 106 NIST Cybersecurity Framework 2.0 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 174 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 49 it maps to, and the evidence behind each claim, over MCP and REST.