Batch Register

Backup restore test

The shortest fixed clock in these texts is 8,760 hours (yearly), set by DORA Art. 24. Paste one job that feeds this consumer, for example backup_restore_test, 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: restore test, recovery test, restore drill, backup test, dr test, recovery drill, restore verif, restoration test, restore test, DR test.

The clock each rule sets

RegimeClockClause
ISO 27001no clockISO 27001 8.13 Information backupregularly test
SP 800-53no clockSP 800-53 CP-4 Contingency plan testinga defined frequency
HIPAAno clockHIPAA 164.308(a)(7)(ii)(D) Testing and Revision Procedures (Addressable)periodic
DORA8,760hDORA Art. 24 General requirements for the performance of digital operational resilience testingsystems behind critical or important functions tested at least yearly, entities other than microenterprises
8,760hDORA Art. 11 Response and recoverycontinuity and response plans tested at least once a year
ISO 22301no clockISO 22301 8.5 Exercise programmeplanned intervals
NIS2no clockNIS2 Art.21.2.c Business continuity, backup management, disaster recovery and crisis management

Questions this page answers

How often does ISO/IEC 27001:2022 require backup restore test?

The text of ISO 27001 8.13 (Information backup) sets no fixed period: regularly test. Maintain and regularly test backups of information, software and systems per the backup policy.

How often does NIST SP 800-53 Rev 5 require backup restore test?

The text of SP 800-53 CP-4 (Contingency plan testing) sets no fixed period: a defined frequency. Requires the contingency plan to be tested at a defined frequency using defined test types to establish that the plan works and that people are ready to execute it, the test results to be reviewed, and corrective action to be initiated where the test shows it is needed.

How often does HIPAA Security Rule require backup restore test?

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.

How often does DORA (Regulation (EU) 2022/2554) require backup restore test?

Yearly (8,760 hours): DORA Art. 24, General requirements for the performance of digital operational resilience testing. Yearly (8,760 hours): DORA Art. 11, Response and recovery. Financial entities other than microenterprises set up, keep and periodically review a robust, comprehensive programme of digital operational resilience testing within the ICT risk management framework, applied proportionately under Article 4(2), to assess incident preparedness, find weaknesses and fix them promptly. For those entities the programme follows a risk-based approach reflecting the evolving ICT risk landscape, specific risks and the criticality of assets and services; tests are run by independent internal or external parties (internal testers need sufficient resources and no conflicts of interest); issues found are prioritised, classified and remedied with internal validation that they are closed; and appropriate tests are run at least yearly on every ICT system and application that supports a critical or important function (Art. 24(3) to (6)). Microenterprises are outside these paragraphs and test under Article 25(3), balancing testing resources and time against urgency, risk type and criticality. Entities identified by their competent authority must add TLPT under Article 26. 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 ISO 22301:2019 require backup restore test?

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 NIS2 Directive require backup restore test?

The text of NIS2 Art.21.2.c (Business continuity, backup management, disaster recovery and crisis management) sets no fixed period: no period set by the text. This category asks the entity to be able to keep providing its services, or to restore them, when systems fail or are attacked. Backup management means backups that are taken, protected against the same event that takes out production, and demonstrably restorable, which is why restore testing rather than backup success rate is the evidence that counts. Disaster recovery means recovery objectives that were derived from what the service can actually tolerate, and infrastructure and procedure capable of meeting them. Crisis management is the decision-making layer above both: who declares a crisis, who can commit the organisation, how the entity communicates while under pressure. Because NIS2 is concerned with continuity of service to recipients, recovery objectives set purely from internal convenience are the usual weak point.

What does the register ask the owner of a backup restore test job?

When did the last restore read back the whole set, and was the time to restore recorded?

The clauses in full

ISO 27001 8.13 Information backupthe standard's page

Maintain and regularly test backups of information, software and systems per the backup policy.

Guidance beside it, ISO 27002 8.13: Requires backup copies of information, software and systems to be maintained and regularly tested, in line with the agreed topic specific policy on backup. Supporting SME guidance treats regular creation of backups together with tested recovery as the substance of the control, not the copy on its own.

What an assessor asks to see: backup_policy; backup_schedule; backup_test_reports; retention_records. Where it usually falls short: infrequent restore testing

SP 800-53 CP-4 Contingency plan testingthe standard's page

Requires the contingency plan to be tested at a defined frequency using defined test types to establish that the plan works and that people are ready to execute it, the test results to be reviewed, and corrective action to be initiated where the test shows it is needed.

What an assessor asks to see: Test plan and scenario documentation for each exercise; Test report with results, observations and participants; Defined test types and frequency, and evidence they were met; Corrective actions raised, tracked and closed following the test. Where it usually falls short: Tabletop exercise substituted for the technical failover test the plan requires

HIPAA 164.308(a)(7)(ii)(D) Testing and Revision Procedures (Addressable)the standard's page

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

DORA Art. 24 General requirements for the performance of digital operational resilience testingthe standard's page

Financial entities other than microenterprises set up, keep and periodically review a robust, comprehensive programme of digital operational resilience testing within the ICT risk management framework, applied proportionately under Article 4(2), to assess incident preparedness, find weaknesses and fix them promptly. For those entities the programme follows a risk-based approach reflecting the evolving ICT risk landscape, specific risks and the criticality of assets and services; tests are run by independent internal or external parties (internal testers need sufficient resources and no conflicts of interest); issues found are prioritised, classified and remedied with internal validation that they are closed; and appropriate tests are run at least yearly on every ICT system and application that supports a critical or important function (Art. 24(3) to (6)). Microenterprises are outside these paragraphs and test under Article 25(3), balancing testing resources and time against urgency, risk type and criticality. Entities identified by their competent authority must add TLPT under Article 26.

What an assessor asks to see: Approved digital operational resilience testing programme with its risk-based rationale (entities other than microenterprises); Tester independence records, including conflict-of-interest checks for internal testers; Issue log from tests with priority, classification, remediation owner and validation of closure; Yearly test schedule and results covering every ICT system and application that supports a critical or important function. Where it usually falls short: Testing done by the team that built or runs the system

DORA Art. 11 Response and recoverythe standard's page

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

ISO 22301 8.5 Exercise programmethe standard's page

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

NIS2 Art.21.2.c Business continuity, backup management, disaster recovery and crisis managementthe standard's page

This category asks the entity to be able to keep providing its services, or to restore them, when systems fail or are attacked. Backup management means backups that are taken, protected against the same event that takes out production, and demonstrably restorable, which is why restore testing rather than backup success rate is the evidence that counts. Disaster recovery means recovery objectives that were derived from what the service can actually tolerate, and infrastructure and procedure capable of meeting them. Crisis management is the decision-making layer above both: who declares a crisis, who can commit the organisation, how the entity communicates while under pressure. Because NIS2 is concerned with continuity of service to recipients, recovery objectives set purely from internal convenience are the usual weak point.

What an assessor asks to see: Business impact analysis deriving recovery time and recovery point objectives from service tolerance; Backup configuration showing isolation or immutability against destructive attack; Restore test results, dated, covering the systems that carry the essential service; The crisis management plan naming decision authority, activation criteria and communications routes. Where it usually falls short: Backups verified as completed but never restored end to end

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