NIST Cybersecurity Framework 2.0
RS - Respond

NIST Cybersecurity Framework 2.0 NIST-CSF-RS.MI-01: Incidents are contained

Incidents are contained. 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 63 controls across 29 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 9 controls

FedRAMP High · 7 controls

  • IR-2 Incident Response Training
  • IR-4 Incident Handling
  • IR-4(1) Automated Incident Handling Processes
  • IR-9 Information Spillage Response (IR-9)
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))
  • SI-7(7) Integration of Detection and Response

FedRAMP Moderate · 7 controls

  • IR-2 Incident Response Training
  • IR-4 Incident Handling
  • IR-4(1) Automated Incident Handling Processes
  • IR-9 Information Spillage Response (IR-9)
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))
  • SI-7(7) Integration of Detection and Response

CIS Controls v8 · 4 controls

  • CIS-13.4 Perform Traffic Filtering Between Network Segments
  • CIS-13.7 Deploy a Host-Based Intrusion Prevention Solution
  • CIS-13.8 Deploy a Network Intrusion Prevention Solution
  • CIS-17.4 Establish and Maintain an Incident Response Process

ASD Strategies to Mitigate Cyber Security Incidents · 3 controls

  • ASD37-22 Network segmentation (Excellent)
  • ASD37-28 Continuous incident detection and response (Excellent)
  • ASD37-30 Endpoint detection and response (Very Good)

AWS Well-Architected Security Pillar · 3 controls

  • SEC04-BP04 Initiate remediation for non-compliant resources
  • SEC10-BP04 Develop and test security incident response playbooks
  • SEC10-BP05 Pre-provision access

Australian Information Security Manual · 3 controls

  • ISM-0133 Handling and containing data spills
  • ISM-0917 Handling malicious code infections
  • ISM-1591 Removing access for detected malicious activity

HIPAA Security Rule · 2 controls

ISO 27002:2022 · 2 controls

  • 5.26 Response to information security incidents
  • 8.12 Data leakage prevention

ISO 27701:2019 · 2 controls

  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements

NIST SP 800-66 Rev 2 · 2 controls

PCI DSS 4.0 · 2 controls

  • 11.6.1 11.6.1 Payment page tamper detection
  • 12.10.1 12.10.1 Incident response plan ready for activation

APRA CPS 234 · 1 control

  • CPS234-P24 Information Security Response Plans

Azure Security Benchmark · 1 control

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

Belgium CyberFundamentals · 1 control

  • BE-CF-19 Incident handling and containment

Bermuda Monetary Authority (BMA) Cyber Risk Management Code of Conduct · 1 control

  • BMA-14 IT Security Incident Management and Response Team

C5 (Germany) · 1 control

CMMC 2.0 · 1 control

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

DORA · 1 control

ISO 27001:2022 · 1 control

  • 5.26 Response to information security incidents

NIS2 Directive · 1 control

NIST Cybersecurity Framework 1.0 · 1 control

  • RS.MI-1 RS.MI-1: Incidents are contained

NIST Cybersecurity Framework 1.1 · 1 control

  • RS.MI-1 RS.MI-1: Incidents are contained

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-61 Rev. 3 · 1 control

  • RS.MI-01 RS.MI-01 Incidents contained, automatically where configured and manually by handlers

SOC 2 · 1 control

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-01 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.

If you hold ISO 27001:202268.9% covered · 33 gapsIf you hold NIST SP 800-53 Rev 567.9% covered · 34 gapsIf you hold C5 (Germany)67% covered · 35 gapsIf you hold FedRAMP Moderate63.2% covered · 39 gapsIf you hold ISO 27002:202258.5% covered · 44 gapsIf you hold CIS Controls v853.8% covered · 49 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll NIST Cybersecurity Framework 2.0 controls