CIS Controls v8
CIS Control 17: Incident Response Management

CIS Controls v8 CIS-17.2: Establish and Maintain Contact Information for Reporting Security Incidents

Set up and keep contact details for everyone who must be told about security incidents. These may include the enterprise's own staff, outside vendors, police and other law enforcement, cyber insurers, relevant government bodies, partners in an ISAC (Information Sharing and Analysis Center) and other stakeholders. Check the contacts each year so the details stay current.

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

What else in your programme already covers this

This control maps to 45 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.

ISO 27002:2022 · 4 controls

  • 5.24 Information security incident management planning and preparation
  • 5.5 Contact with authorities
  • 5.6 Contact with special interest groups
  • 6.8 Information security event reporting

NIST Cybersecurity Framework 2.0 · 4 controls

  • NIST-CSF-GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

SOC 2 · 4 controls

  • SOC2-CC2.3 CC2.3 Communication with external parties about internal control (COSO principle 15)
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-P6.6 P6.6 Notifying breaches and incidents

DORA · 3 controls

  • DORA-Art.14 Communication
  • DORA-Art.19 Reporting of major ICT-related incidents
  • DORA-Art.45 Information-sharing arrangements on cyber threat information and intelligence

ISO 27001:2022 · 3 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.5 Contact with authorities
  • 6.8 Information security event reporting

APRA CPS 234 · 2 controls

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

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

FedRAMP High · 2 controls

  • IR-6 Incident Reporting
  • IR-7 Incident Response Assistance

FedRAMP Moderate · 2 controls

  • IR-6 Incident Reporting
  • IR-7 Incident Response Assistance

ISO 22301:2019 · 2 controls

  • 7.4 Communication
  • 8.4.3 Warning and communication

ISO 27701:2019 · 2 controls

  • 5.2.2 Understanding the needs and expectations of interested parties
  • 6.13.1 Management of information security incidents and improvements

AWS Well-Architected Security Pillar · 1 control

  • SEC10-BP01 Identify key personnel and external resources

Australia My Health Records Act 2012 · 1 control

Australian Information Security Manual · 1 control

  • ISM-0043 Cyber security incident response plan contents

Azure Security Benchmark · 1 control

  • ASBv3-IR-2 Preparation - setup incident notification

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

CIS Controls v8.1 · 1 control

  • 17.2 Establish and Maintain Contact Information for Reporting Security Incidents

CMMC 2.0 · 1 control

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

HIPAA Security Rule · 1 control

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

NIST SP 800-53 Rev 5 · 1 control

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 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.2 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 45 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll CIS Controls v8 controls