CIS Controls v8
CIS Control 17: Incident Response Management

CIS Controls v8 CIS-17.7: Conduct Routine Incident Response Exercises

Plan and run regular incident response exercises and scenarios for the key people in the incident response process so they are ready for real incidents. The exercises have to put communication channels, workflows and decision making to the test. Run them at least once a year.

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 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 SP 800-53 Rev 5 · 9 controls

FedRAMP High · 6 controls

  • CP-4(1) Coordinate with Related Plans
  • IR-2 Incident Response Training
  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-4 Incident Handling
  • IR-8 Incident Response Plan

FedRAMP Moderate · 6 controls

  • CP-4(1) Coordinate with Related Plans
  • IR-2 Incident Response Training
  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-4 Incident Handling
  • IR-8 Incident Response Plan
  • NIST-CSF-GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities
  • NIST-CSF-ID.IM-01 Improvements are identified from evaluations
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process

PCI DSS 4.0 · 3 controls

  • 12.10.2 12.10.2 Annual review and testing of the incident response plan
  • 12.10.4 12.10.4 Periodic training for incident response personnel
  • 12.10.4.1 12.10.4.1 Responder training frequency set by targeted risk analysis

DORA · 2 controls

  • DORA-Art.11 Response and recovery
  • DORA-Art.24 General requirements for the performance of digital operational resilience testing

ISO 22301:2019 · 2 controls

  • 8.5 Exercise programme
  • 8.6 Evaluation of business continuity documentation and capabilities

ISO 27001:2022 · 2 controls

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

ISO 27002:2022 · 2 controls

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

SOC 2 · 2 controls

  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC7.4 CC7.4 Responding to security incidents

APRA CPS 234 · 1 control

  • CPS234-32 Annual Review and Testing of Response Plans
  • ISM-1784 Annual exercising of incident response plan

C5 (Germany) · 1 control

  • C5-BCM-04 Verification, updating and testing of the business continuity
  • CFTC-SS-16 Security Incident Response Plan and Testing

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.13.1 Management of information security incidents and improvements

NIS2 Directive · 1 control

NIST SP 800-172 · 1 control

  • 3.2.2e Practical Exercises in Awareness Training

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