CIS Controls v8
CIS Control 17: Incident Response Management

CIS Controls v8 CIS-17.3: Establish and Maintain an Enterprise Process for Reporting Incidents

Set up and keep an enterprise process through which the workforce reports security incidents. It covers the time allowed for reporting, who reports go to, how to report, and the minimum details a report must contain. Make the process openly available to the whole workforce. Review it each year, or sooner when a major change in the enterprise could affect this Safeguard.

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

What else in your programme already covers this

This control maps to 81 controls across 30 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 Cybersecurity Framework 2.0 · 9 controls

  • NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
  • NIST-CSF-GV.RM-05 Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind
  • 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-CSF-RS.MA-02 Incident reports are triaged and validated
  • NIST-CSF-RS.MA-03 Incidents are categorized and prioritized

FedRAMP High · 6 controls

  • IR-5 Incident Monitoring
  • IR-6 Incident Reporting
  • IR-6(1) Automated Reporting
  • IR-6(3) Incident Reporting | Supply Chain Coordination (IR-6(3))
  • IR-7 Incident Response Assistance
  • IR-8 Incident Response Plan

FedRAMP Moderate · 6 controls

  • IR-5 Incident Monitoring
  • IR-6 Incident Reporting
  • IR-6(1) Automated Reporting
  • IR-6(3) Incident Reporting | Supply Chain Coordination (IR-6(3))
  • IR-7 Incident Response Assistance
  • IR-8 Incident Response Plan

SOC 2 · 6 controls

  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • 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.6 P6.6 Notifying breaches and incidents

ISO 27001:2022 · 5 controls

  • 5.2 Information security roles and responsibilities
  • 5.24 Information security incident management planning and preparation 
  • 5.26 Response to information security incidents
  • 6.3 Information security awareness, education and training
  • 6.8 Information security event reporting

PCI DSS 4.0 · 5 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.3 12.10.3 Incident response personnel available 24/7
  • 12.10.5 12.10.5 Plan covers alerts from security monitoring systems
  • 12.10.7 12.10.7 Response procedures for PAN found in unexpected locations

APRA CPS 234 · 4 controls

  • CPS234-30 Detection and Response Mechanisms
  • CPS234-35 APRA Notification of Material Incidents within 72 Hours
  • CPS234-P19 Policy Direction to All Responsible Parties
  • CPS234-P25 Response Plan Content and Escalation Mechanisms

ISO 27002:2022 · 4 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
  • 6.8 Information security event reporting

NIST SP 800-53 Rev 5 · 4 controls

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

DORA · 3 controls

ISO 27701:2019 · 3 controls

  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements
  • 8.3 Obligations to PII principals

C5 (Germany) · 2 controls

  • C5-SIM-03 Documentation and reporting of security incidents
  • C5-SIM-04 Duty of the users to report security incidents to a central body

CMMC 2.0 · 2 controls

HIPAA Security Rule · 2 controls

ISO 22301:2019 · 2 controls

  • 7.4 Communication
  • 8.4.3 Warning and communication

NIST SP 800-66 Rev 2 · 2 controls

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 230 Operational Risk Management · 1 control

  • CPS230-27 Identification and Escalation of Incidents and Near Misses

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

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

Australia My Health Records Act 2012 · 1 control

Australian Information Security Manual · 1 control

  • ISM-0123 Reporting incidents to the CISO

Azure Security Benchmark · 1 control

  • ASBv3-IR-2 Preparation - setup incident notification

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

  • CFTC-SS-16 Security Incident Response Plan and Testing

NIS2 Directive · 1 control

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

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

UK Cyber Essentials · 1 control

  • CE-SC.8 Process for Compromised Passwords

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 CIS Control 17: Incident Response Management

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-17.3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

If you hold ISO 27001:202266.7% covered · 51 gapsIf you hold FedRAMP Moderate62.7% covered · 57 gapsIf you hold NIST SP 800-53 Rev 557.5% covered · 65 gapsIf you hold NIST Cybersecurity Framework 2.050.3% covered · 76 gapsIf you hold ISO 27002:202249.7% covered · 77 gapsIf you hold Azure Security Benchmark49% covered · 78 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. 240 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 81 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll CIS Controls v8 controls