CIS Controls v8
CIS Control 17: Incident Response Management

CIS Controls v8 CIS-17.5: Assign Key Roles and Responsibilities

Allocate the key incident response roles and responsibilities, drawing as relevant on people from IT, information security, legal, facilities, human resources and public relations, as well as incident responders and analysts. 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 47 controls across 29 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 · 5 controls

SOC 2 · 4 controls

  • SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC7.4 CC7.4 Responding to security incidents

NIST Cybersecurity Framework 2.0 · 3 controls

  • 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-RS.MA-04 Incidents are escalated or elevated as needed

NIST SP 800-181 · 3 controls

PCI DSS 4.0 · 3 controls

  • 1.1.2 1.1.2 Requirement 1 roles and responsibilities assigned
  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 12.10.3 12.10.3 Incident response personnel available 24/7

Azure Security Benchmark · 2 controls

  • ASBv3-IR-1 Preparation - update incident response plan and handling process
  • GS-1 Align organization roles, responsibilities and accountabilities

ISO 22301:2019 · 2 controls

  • 5.3 Roles, responsibilities and authorities
  • 8.4.2 Response structure

ISO 27001:2022 · 2 controls

  • 5.2 Information security roles and responsibilities
  • 5.24 Information security incident management planning and preparation 

ISO 27002:2022 · 2 controls

  • 5.2 Information security roles and responsibilities
  • 5.24 Information security incident management planning and preparation

NIST SP 800-171 Rev 3 · 2 controls

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

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

APRA CPS 230 Operational Risk Management · 1 control

  • CPS230-14 Board Setting of Senior Manager Roles and Responsibilities

APRA CPS 234 · 1 control

  • CPS234-14 Definition of Information Security Roles and Responsibilities

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

C5 (Germany) · 1 control

  • C5-SIM-01 Policy for security incident management

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

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

CMMC 2.0 · 1 control

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

DORA · 1 control

FedRAMP High · 1 control

  • IR-8 Incident Response Plan

FedRAMP Moderate · 1 control

  • IR-8 Incident Response Plan

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 5.3.3 Organizational roles, responsibilities and authorities

ISO/IEC 42001:2023 · 1 control

  • A.3.2 AI roles and responsibilities

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-172 · 1 control

  • 3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-66 Rev 2 · 1 control

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

MCP endpointAll CIS Controls v8 controls