CIS Controls v8
CIS Control 17: Incident Response Management

CIS Controls v8 CIS-17.1: Designate Personnel to Manage Incident Handling

Name one key person, plus at least one deputy, to run the enterprise incident handling process. These managers coordinate and document incident response and recovery, and may be enterprise employees, third-party vendors, or a mix of both. Where a third-party vendor is used, name at least one person inside the enterprise to oversee the vendor's work. 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 57 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 SP 800-53 Rev 5 · 6 controls

FedRAMP High · 4 controls

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

FedRAMP Moderate · 4 controls

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

SOC 2 · 4 controls

  • SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
  • 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

ISO 27002:2022 · 3 controls

  • 5.2 Information security roles and responsibilities
  • 5.24 Information security incident management planning and preparation
  • 5.25 Assessment and decision on information security events

C5 (Germany) · 2 controls

  • C5-SIM-01 Policy for security incident management
  • C5-SIM-02 Processing of security incidents

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

HIPAA Security Rule · 2 controls

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 27701:2019 · 2 controls

  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements

NIST Cybersecurity Framework 2.0 · 2 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 SP 800-181 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

PCI DSS 4.0 · 2 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

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

  • ANSSI-HYG-39 Designate an Information System Security Officer and Make the Role Known

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 Consumer Data Right - Banking (CDR) · 1 control

Australia My Health Records Act 2012 · 1 control

Australian Information Security Manual · 1 control

  • ISM-1618 CISO oversight of incident response

Azure Security Benchmark · 1 control

  • ASBv3-IR-1 Preparation - update incident response plan and handling process

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

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

CIS Controls v8.1 · 1 control

  • 17.1 Designate Personnel to Manage Incident Handling

CMMC 2.0 · 1 control

ISO/IEC 42001:2023 · 1 control

  • 5.3 Roles, responsibilities and authorities

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.6.2e Establish and Maintain a Cyber Incident Response Team

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

MCP endpointAll CIS Controls v8 controls