CMMC 2.0
Incident Response

CMMC 2.0 IR.L2-3.6.2: Incident Reporting

Track, document and report incidents to the designated internal officials and to external authorities where required.

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

What else in your programme already covers this

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

SOC 2 · 7 controls

  • SOC2-CC2.3 CC2.3 Communication with external parties about internal control (COSO principle 15)
  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-P6.3 P6.3 Record of unauthorised disclosures and breaches
  • SOC2-P6.5 P6.5 Vendor commitments to report unauthorised disclosures
  • SOC2-P6.6 P6.6 Notifying breaches and incidents

ISO 27001:2022 · 5 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.5 Contact with authorities
  • 6.8 Information security event reporting

NIST Cybersecurity Framework 2.0 · 5 controls

  • NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
  • NIST-CSF-RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
  • NIST-CSF-RS.AN-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved
  • NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
  • NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders

NIST SP 800-53 Rev 5 · 5 controls

  • NIST800-IR-5 IR-5 Incident Monitoring
  • NIST800-IR-6 IR-6 Incident Reporting
  • NIST800-IR-7 IR-7 Incident Response Assistance
  • NIST800-IR-8 IR-8 Incident Response Plan
  • SP800-53-IR Incident Response Family

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 4 controls

AWS Well-Architected Security Pillar · 3 controls

  • SEC10-BP01 Identify key personnel and external resources
  • SEC10-BP02 Develop incident management plans
  • SEC10-BP08 Establish a framework for learning from incidents

C5 (Germany) · 3 controls

  • C5-OPS-21 Involvement of Cloud Customers in the Event of Incidents
  • C5-SIM-03 Documentation and reporting of security incidents
  • C5-SIM-04 Duty of the users to report security incidents to a central body

CIS Controls v8 · 3 controls

  • CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
  • CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
  • CIS-17.6 Define Mechanisms for Communicating During Incident Response

FedRAMP High · 3 controls

  • IR-5 Incident Monitoring
  • IR-6 Incident Reporting
  • IR-6(1) Automated Reporting

FedRAMP Moderate · 3 controls

  • IR-5 Incident Monitoring
  • IR-6 Incident Reporting
  • IR-6(1) Automated Reporting

APRA CPS 230 Operational Risk Management · 2 controls

  • CPS230-27 Identification and Escalation of Incidents and Near Misses
  • CPS230-P33 APRA Notification of Operational Risk Incidents within 72 Hours

APRA CPS 234 · 2 controls

  • CPS234-35 APRA Notification of Material Incidents within 72 Hours
  • CPS234-P25 Response Plan Content and Escalation Mechanisms

HIPAA Security Rule · 2 controls

ISO 22301:2019 · 2 controls

  • 7.4 Communication
  • 8.4.3 Warning and communication

ISO 27002:2022 · 2 controls

  • 5.5 Contact with authorities
  • 6.8 Information security event reporting

ISO/IEC 42001:2023 · 2 controls

  • A.3.3 Reporting of concerns
  • A.8.4 Communication of incidents

NIS2 Directive · 2 controls

  • Art.21.2.b Incident handling
  • Art.23.1 Notify significant incidents to the CSIRT or competent authority, and warn affected service recipients

ACSC Essential Eight · 1 control

  • E8-APP-ML3 Application Control (ML3)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-40 Define a Security Incident Management Procedure

APPI · 1 control

  • APPI-A26 Report of Leakage to the Commission and Notification to the Person

APRA CPS 220 Risk Management · 1 control

  • CPS220-19 APRA Notification of Framework Breach within 10 Business Days

APRA SPS 220 Risk Management (Superannuation) · 1 control

  • SPS220-44 APRA Notification of Framework Breach within 10 Business Days

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-28 Continuous incident detection and response (Excellent)

Australia Consumer Data Right - Banking (CDR) · 1 control

Azure Security Benchmark · 1 control

  • ASBv3-IR-2 Preparation - setup incident notification

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

DFARS 252.204-7012 - Safeguarding Covered Defense Information · 1 control

  • DFARS-7012-c Cyber incident reporting (72-hour rapid report)

ISO 27701:2019 · 1 control

  • 6.13.1 Management of information security incidents and improvements

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

  • 03.06.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-66 Rev 2 · 1 control

PCI DSS 4.0 · 1 control

  • 12.10.1 12.10.1 Incident response plan ready for activation

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

If you hold FedRAMP Moderate98.2% covered · 2 gapsIf you hold NIST SP 800-171 Rev 394.5% covered · 6 gapsIf you hold NIST SP 800-53 Rev 585.5% covered · 16 gapsIf you hold ISO 27001:202279.1% covered · 23 gapsIf you hold ISO 27002:202267.3% covered · 36 gapsIf you hold CIS Controls v864.5% covered · 39 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. 1 were rejected on the FedRAMP Moderate pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll CMMC 2.0 controls