CIS Controls v8
CIS Control 17: Incident Response Management

CIS Controls v8 CIS-17.6: Define Mechanisms for Communicating During Incident Response

Decide the primary and secondary means of communicating and reporting during a security incident, such as phone calls, emails or letters, bearing in mind that some means, email for instance, may be disrupted by the incident. Review this 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 55 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-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-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
  • 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 · 6 controls

FedRAMP High · 3 controls

  • IR-4 Incident Handling
  • IR-7 Incident Response Assistance
  • IR-8 Incident Response Plan

FedRAMP Moderate · 3 controls

  • IR-4 Incident Handling
  • IR-7 Incident Response Assistance
  • IR-8 Incident Response Plan

ISO 27001:2022 · 3 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.26 Response to information security incidents
  • 5.29 Information security during disruption

PCI DSS 4.0 · 3 controls

  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 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

SOC 2 · 3 controls

  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-P6.6 P6.6 Notifying breaches and incidents

CMMC 2.0 · 2 controls

ISO 22301:2019 · 2 controls

  • 7.4 Communication
  • 8.4.3 Warning and communication

ISO 27002:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation
  • 5.26 Response to information security incidents

ISO 27701:2019 · 2 controls

  • 5.5.4 Communication
  • 6.13.1 Management of information security incidents and improvements

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • 03.06.02 Incident Monitoring, Reporting, and Response Assistance
  • 03.06.05 Incident Response Plan

APRA CPS 234 · 1 control

  • CPS234-P25 Response Plan Content and Escalation Mechanisms
  • ISM-1731 Separate system for remediation planning
  • ASBv3-IR-2 Preparation - setup incident notification

C5 (Germany) · 1 control

  • C5-SIM-03 Documentation and reporting of security incidents
  • CFTC-SS-16 Security Incident Response Plan and Testing

DORA · 1 control

HIPAA Security Rule · 1 control

ISO/IEC 42001:2023 · 1 control

  • A.8.4 Communication of incidents

NIS2 Directive · 1 control

  • Art.21.2.j Multi-factor or continuous authentication, secured communications and secured emergency communications

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

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.

Query this from an agent

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