Backup policy
What is backed up, how often, where the copies are kept, how they are protected and how restoration is tested.
How the register reads it
| Also called | backup and recovery policy, restore procedure |
|---|---|
| Family | Operations and technology |
| Document type | Policy. The regimes ask for the content, not the label; a line pasted as a standard, procedure, plan or schedule is placed here with the label noted. |
| Expected owner | The head of IT operations. |
| Review cadence | Annual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period). |
| On the gap list when | ISO 27001 or DORA or NIS2 is ticked and no line resolves to it (ISO 27701 requires it too, inside a parent document, so it does not list it separately). |
| Template | Backup and recovery policy. |
Which standards require it, and what each expects it to contain
4 requiring clauses, 4 regimesShown on a register for the regimes you tick; with none ticked, ISO 27001 is applied. Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim.
ISO/IEC 27001:2022
ISO 27001 8.13 Information backupMaintain and regularly test backups of information, software and systems per the backup policy.
What the ISO 27002 guidance expects the document to say: 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.
Common gap: infrequent restore testing
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO/IEC 27701:2025
ISO 27701 A.3.24 Information backupThe organization shall have a policy addressing the backup, recovery and restoration of PII and any further contractual or legal requirements for the erasure of PII held in backups; shall inform customers of the limits of the service regarding backup and, where it explicitly provides backup and restore services, give them clear information about its backup and restoration capabilities for PII; shall demonstrate compliance with any jurisdiction-specific requirements on backup frequency, testing and recovery procedures; shall ensure that restored PII is brought to a state where its integrity can be assured or where inaccuracy or incompleteness is identified and resolved, which can involve the PII principal; and shall keep a procedure for and a log of PII restoration efforts recording at least the person responsible and a description of the PII restored, meeting any jurisdiction-prescribed log content. Subcontracted storage of backup copies falls under the supplier controls.
Common gap: PII erased from live systems and retained indefinitely in backups
Source: ISO/IEC 27701:2025
DORA (Regulation (EU) 2022/2554)
DORA Art. 12 Backup policies and procedures, restoration and recoveryFinancial entities document backup policies (scope of data and minimum backup frequency set by criticality or confidentiality) and restoration and recovery procedures, set up backup systems whose activation does not weaken security, and test backup and restoration periodically. When restoring with their own systems they restore onto ICT systems kept separate, both physically and logically, from the source system. Recovery time and recovery point objectives are set per function, and integrity checks and reconciliations follow any recovery. Entities other than microenterprises keep redundant ICT capacity; microenterprises decide on redundancy from their risk profile (Art. 12(4)). Further duties apply only to specific entity types: central counterparties must be able to recover every transaction in progress when the disruption hit, data reporting service providers keep backup and restoration facilities, and central securities depositories keep a geographically distant secondary processing site (Art. 12(3) and (5)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
Common gap: Backups never restored in a test
Source: DORA (Regulation (EU) 2022/2554)
The NIS2 Directive
NIS2 Art. 21(2)(c) Business continuity, backup management, disaster recovery and crisis managementThis 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.
Common gap: Backups verified as completed but never restored end to end
Source: NIS2 Directive
Customizable template
10 sections, 4 cited to requiring clausesWith every regime ticked. Each clause section carries our statement of the clause, guidance beside it and starter wording to adapt; enter your organisation once, edit any section, export to Word, print or text. Every template is a draft to adapt and approve.
- Purpose
- Scope
- Roles and responsibilities
- Information backup ISO 27001 A.8.13
- Information backup ISO 27701 A.3.24
- Backup policies and procedures, restoration and recovery DORA Art. 12
- Business continuity, backup management, disaster recovery and crisis management NIS2 Art. 21(2)(c)
- Exceptions
- Related documents
- Review and approval
Customise this template The template document on the compliance platform
Do this for every document on your list
Paste the list and get this reading for every document at once, with the owner and cadence against each, the clauses quoted, and the documents the regimes expect that the list does not carry. Eight documents free, no account.
Build a register