Incident response exercise or drill
The shortest fixed clock in these texts is 8,760 hours (yearly), set by PCI DSS 12.10.2. Paste one job that feeds this consumer, for example ir_tabletop_exercise, weekly, and the register reads its period against the clocks below, names the gap in hours, and carries the question for its owner.
Matched on the job name or the consumer column by these words: drill, tabletop, ir test, incident exercise, response exercise, exercise, ir exercise, response test, crisis exercise, tabletop exercise.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| PCI DSS | 8,760h | PCI DSS 12.10.2 Annual review and testing of the incident response planreviewed at least once every 12 months and tested annually |
| CPS 234 | 8,760h | CPS 234 para 26 Annual review and testing of response plansreviewed and tested every year |
| SP 800-53 | no clock | SP 800-53 IR-3 Incident response testinga defined frequency |
| ISO 22301 | no clock | ISO 22301 8.5 Exercise programmeplanned intervals |
| DORA | 8,760h | DORA Art. 11 Response and recoveryresponse and continuity plans tested at least once a year |
| HIPAA | no clock | HIPAA 164.308(a)(7)(ii)(D) Testing and Revision Procedures (Addressable)periodic |
Questions this page answers
How often does PCI DSS v4.0 require incident response exercise or drill?
Yearly (8,760 hours): PCI DSS 12.10.2, Annual review and testing of the incident response plan. On a cycle of no more than 12 months, the entity must review its security incident response plan, updating the content where needed, and must test it, with the test covering every element listed in Requirement 12.10.1. The guidance explains that tests can take the form of simulated incidents or table-top exercises involving relevant personnel, and that reviewing how well the simulated response went helps confirm nothing required is missing from the plan. Customized approach objective: the plan stays current and undergoes periodic testing.
How often does APRA CPS 234 require incident response exercise or drill?
Yearly (8,760 hours): CPS 234 para 26, Annual review and testing of response plans. Every year the entity reviews and tests its response plans so they stay effective and fit for purpose.
How often does NIST SP 800-53 Rev 5 require incident response exercise or drill?
The text of SP 800-53 IR-3 (Incident response testing) sets no fixed period: a defined frequency. Requires the incident response capability serving the system to be tested for effectiveness at an organization-defined frequency using the test types the organization has defined, so readiness is demonstrated rather than assumed.
How often does ISO 22301:2019 require incident response exercise or drill?
The text of ISO 22301 8.5 (Exercise programme) sets no fixed period: planned intervals. Implement and maintain a programme of exercising and testing that validates the effectiveness of the continuity strategies and solutions over time, running exercises and tests consistent with the continuity objectives, based on well planned scenarios with clearly defined aims, that build teamwork, competence, confidence and knowledge in those with response roles, that taken together over time validate the strategies and solutions, that produce formal post exercise reports with outcomes, recommendations and improvement actions, that are reviewed in the context of continual improvement, and that are held at planned intervals and when significant change occurs; act on the results to implement changes and improvements.
How often does DORA (Regulation (EU) 2022/2554) require incident response exercise or drill?
Yearly (8,760 hours): DORA Art. 11, Response and recovery. Financial entities adopt an ICT business continuity policy within their overall continuity policy and implement it through documented arrangements that keep critical or important functions running, contain and resolve incidents, estimate preliminary impacts, and drive crisis communication and reporting under Articles 14 and 19; they run a business impact analysis, keep ICT response and recovery plans, test, at least once a year and after substantive changes, the continuity and response plans for the systems behind every function, test crisis communication plans, and keep records of activity during disruptions. Entities other than microenterprises additionally have the response and recovery plans reviewed by independent internal audit (Art. 11(3)), include cyber-attack and switchover scenarios in testing (Art. 11(6)), run a crisis management function (Art. 11(7)), and estimate aggregated annual costs and losses of major incidents when the authority asks (Art. 11(10)). Central securities depositories also send continuity test results to the authority (Art. 11(9)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
How often does HIPAA Security Rule require incident response exercise or drill?
The text of HIPAA 164.308(a)(7)(ii)(D) (Testing and Revision Procedures (Addressable)) sets no fixed period: periodic. Implement procedures for periodic testing and revision of contingency plans. NIST recommends annual tabletop, biennial functional, and post-incident lessons-learned updates.
What does the register ask the owner of a incident response exercise or drill job?
Which on-demand packs does this exercise prove, and is the post-exercise report filed with the plan?
The clauses in full
On a cycle of no more than 12 months, the entity must review its security incident response plan, updating the content where needed, and must test it, with the test covering every element listed in Requirement 12.10.1. The guidance explains that tests can take the form of simulated incidents or table-top exercises involving relevant personnel, and that reviewing how well the simulated response went helps confirm nothing required is missing from the plan. Customized approach objective: the plan stays current and undergoes periodic testing.
What an assessor asks to see: Annual plan review record and change log; Table-top or simulation exercise report; Exercise participant list; Test coverage map against the 12.10.1 elements. Where it usually falls short: Exercise tested only technical containment and skipped brand notification or legal analysis
Every year the entity reviews and tests its response plans so they stay effective and fit for purpose.
What an assessor asks to see: Annual exercise schedule and completed tabletop or simulation reports; Exercise participant lists including executives and, where relevant, the Board; After-action reports with improvements logged and tracked; Records of the annual plan review and resulting changes. Where it usually falls short: Plan reviewed on paper but never exercised
Requires the incident response capability serving the system to be tested for effectiveness at an organization-defined frequency using the test types the organization has defined, so readiness is demonstrated rather than assumed.
What an assessor asks to see: Defined test types and frequency for incident response testing; Exercise scenario documents and participant lists; Test reports with observations and identified weaknesses; Corrective actions tracked to closure after each test. Where it usually falls short: Only tabletop exercises run, so technical containment steps are never proven
Implement and maintain a programme of exercising and testing that validates the effectiveness of the continuity strategies and solutions over time, running exercises and tests consistent with the continuity objectives, based on well planned scenarios with clearly defined aims, that build teamwork, competence, confidence and knowledge in those with response roles, that taken together over time validate the strategies and solutions, that produce formal post exercise reports with outcomes, recommendations and improvement actions, that are reviewed in the context of continual improvement, and that are held at planned intervals and when significant change occurs; act on the results to implement changes and improvements.
What an assessor asks to see: Exercise programme showing scope, scenario and interval coverage over time; Exercise aims and objectives defined before each exercise; Formal post exercise reports with outcomes, recommendations and actions; Action tracking to closure with evidence of the resulting change. Where it usually falls short: The same comfortable scenario rehearsed annually, so rare failure modes are never stressed
Financial entities adopt an ICT business continuity policy within their overall continuity policy and implement it through documented arrangements that keep critical or important functions running, contain and resolve incidents, estimate preliminary impacts, and drive crisis communication and reporting under Articles 14 and 19; they run a business impact analysis, keep ICT response and recovery plans, test, at least once a year and after substantive changes, the continuity and response plans for the systems behind every function, test crisis communication plans, and keep records of activity during disruptions. Entities other than microenterprises additionally have the response and recovery plans reviewed by independent internal audit (Art. 11(3)), include cyber-attack and switchover scenarios in testing (Art. 11(6)), run a crisis management function (Art. 11(7)), and estimate aggregated annual costs and losses of major incidents when the authority asks (Art. 11(10)). Central securities depositories also send continuity test results to the authority (Art. 11(9)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
What an assessor asks to see: ICT business continuity policy and the business impact analysis it rests on; ICT response and recovery plans with yearly test reports and tests after substantive changes; Crisis communication plan test record and records kept during actual disruptions; Internal audit review of the response and recovery plans, crisis management function terms of reference and cyber-attack and switchover test scenarios (entities other than microenterprises). Where it usually falls short: Plans tested only for critical systems, not for systems supporting all functions
Implement procedures for periodic testing and revision of contingency plans. NIST recommends annual tabletop, biennial functional, and post-incident lessons-learned updates.
What an assessor asks to see: Test schedule; Test reports; After-action reports; Plan revision history. Where it usually falls short: Plans untested for years
Requirement text is our own statement of each clause, from the standards published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard: our statement of each clause, not the instrument verbatim. Run this job through the register