CMMC 2.0
Incident Response

CMMC 2.0 IR.L2-3.6.3: Incident Response Testing

Test the organizational incident response capability to confirm it works.

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

What else in your programme already covers this

This control maps to 44 controls across 27 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 · 4 controls

  • NIST800-IR-3 IR-3 Incident Response Testing
  • NIST800-PM-14 PM-14 Testing, Training, and Monitoring
  • SP800-53-CP Contingency Planning Family
  • SP800-53-IR Incident Response Family

SOC 2 · 4 controls

  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents

PCI DSS 4.0 · 3 controls

  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 12.10.2 12.10.2 Annual review and testing of the incident response plan
  • 12.10.6 12.10.6 Plan evolved from lessons learned and industry developments

C5 (Germany) · 2 controls

  • C5-BCM-04 Verification, updating and testing of the business continuity
  • C5-SIM-05 Evaluation and learning process

FedRAMP High · 2 controls

  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))

FedRAMP Moderate · 2 controls

  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))

ISO 22301:2019 · 2 controls

  • 8.5 Exercise programme
  • 8.6 Evaluation of business continuity documentation and capabilities

ISO 27001:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.27 Learning from information security incidents

ISO 27002:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation
  • 5.27 Learning from information security incidents

ISO 27701:2019 · 2 controls

  • 6.13.1 Management of information security incidents and improvements
  • 6.14.1 Information security continuity
  • ANSSI-HYG-40 Define a Security Incident Management Procedure
  • CPS230-33 Systematic BCP Testing Program

APRA CPS 234 · 1 control

  • CPS234-32 Annual Review and Testing of Response Plans
  • ASD37-35 Business continuity and disaster recovery plans (Very Good)
  • CFTC-SS-16 Security Incident Response Plan and Testing

CIS Controls v8 · 1 control

  • CIS-17.7 Conduct Routine Incident Response Exercises

HIPAA Security Rule · 1 control

NIS2 Directive · 1 control

NIST SP 800-172 · 1 control

  • 3.2.2e Practical Exercises in Awareness Training

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 Incident Response

You are reading one control. How much of CMMC 2.0 have you already done?

CMMC 2.0 IR.L2-3.6.3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 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. 1 were rejected on the FedRAMP Moderate pair alone.

Query this from an agent

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