Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

Article 12Backup policies and procedures, restoration and recovery procedures and methods

1. For the purpose of ensuring the restoration of ICT systems and data with minimum downtime, limited disruption and loss, as part of their ICT risk management framework, financial entities shall develop and document:

(a) backup policies and procedures specifying the scope of the data that is subject to the backup and the minimum frequency of the backup, based on the criticality of information or the confidentiality level of the data;

(b) restoration and recovery procedures and methods.

2. Financial entities shall set up backup systems that can be activated in accordance with the backup policies and procedures, as well as restoration and recovery procedures and methods. The activation of backup systems shall not jeopardise the security of the network and information systems or the availability, authenticity, integrity or confidentiality of data. Testing of the backup procedures and restoration and recovery procedures and methods shall be undertaken periodically.

3. When restoring backup data using own systems, financial entities shall use ICT systems that are physically and logically segregated from the source ICT system. The ICT systems shall be securely protected from any unauthorised access or ICT corruption and allow for the timely restoration of services making use of data and system backups as necessary.

For central counterparties, the recovery plans shall enable the recovery of all transactions at the time of disruption to allow the central counterparty to continue to operate with certainty and to complete settlement on the scheduled date.

Data reporting service providers shall additionally maintain adequate resources and have back-up and restoration facilities in place in order to offer and maintain their services at all times.

4. Financial entities, other than microenterprises, shall maintain redundant ICT capacities equipped with resources, capabilities and functions that are adequate to ensure business needs. Microenterprises shall assess the need to maintain such redundant ICT capacities based on their risk profile.

5. Central securities depositories shall maintain at least one secondary processing site endowed with adequate resources, capabilities, functions and staffing arrangements to ensure business needs.

The secondary processing site shall be:

(a) located at a geographical distance from the primary processing site to ensure that it bears a distinct risk profile and to prevent it from being affected by the event which has affected the primary site;

(b) capable of ensuring the continuity of critical or important functions identically to the primary site, or providing the level of services necessary to ensure that the financial entity performs its critical operations within the recovery objectives;

(c) immediately accessible to the financial entity’s staff to ensure continuity of critical or important functions in the event that the primary processing site has become unavailable.

6. In determining the recovery time and recovery point objectives for each function, financial entities shall take into account whether it is a critical or important function and the potential overall impact on market efficiency. Such time objectives shall ensure that, in extreme scenarios, the agreed service levels are met.

7. When recovering from an ICT-related incident, financial entities shall perform necessary checks, including any multiple checks and reconciliations, in order to ensure that the highest level of data integrity is maintained. These checks shall also be performed when reconstructing data from external stakeholders, in order to ensure that all data is consistent between systems.

DORA, the European Union regulation on digital operational resilience, Article 12

Backup, restoration and recovery. Entities must document backup policies and procedures covering what is backed up and the minimum frequency, based on criticality or confidentiality, plus restoration and recovery procedures and methods. Backup systems must be activated without jeopardising security or data properties, and procedures tested periodically.

When restoring from backups on their own systems, entities must use systems physically and logically segregated from the source system, protected against unauthorised access and corruption, and able to restore in time. When recovering from an incident, they must carry out the necessary checks and reconciliations, including when reconstructing data from external parties, to maintain the highest level of data integrity and keep data consistent between systems.

Recovery time and recovery point objectives are set per function, taking into account whether it is critical or important and the impact on market efficiency, so that agreed service levels hold even in extreme scenarios.

Entities other than microenterprises must keep redundant ICT capacity adequate to business needs. Microenterprises must assess the need for it based on their risk profile.

Some duties are sector-specific. Central counterparties’ recovery plans must allow recovery of all transactions at the time of disruption and completion of settlement on the scheduled date. Data reporting service providers need adequate backup and restoration facilities. Central securities depositories must maintain a secondary processing site at a geographical distance that gives it a distinct risk profile, able to continue critical functions, and immediately accessible to staff.

What is in the packs for this

Each one helps with this requirement.

  • DORA Article-to-Control Mapping LibraryExcel

    in DORA ICT Risk & Resilience Readiness

    Requirement Library rows RQ-19: each gives the provision in plain words, what an entity must be able to show and the documents that help.

  • DORA Readiness Self-AssessmentExcel

    in DORA ICT Risk & Resilience Readiness

    Readiness items RM-06 rate how ready the entity is for the provision, with the evidence behind each rating and the gap.

  • ICT Risk Management Framework Document TemplateWord

    in DORA ICT Risk & Resilience Readiness

    Statement FW-31 on the backup policy and the restoration and recovery procedures.

  • Business Continuity & ICT Resilience PolicyWord

    in Cyber Resilience & Recovery

    Sets backup frequency from each service's recovery point (RR-11) and recovery time and recovery point objectives for each critical service (RR-04).

  • Cyber Recovery Operating ProcedureWord

    in Cyber Resilience & Recovery

    Documents restoration and recovery procedures: R2 to R4 activate backups without risking security or data integrity, R2 restores into segregated systems, R5 checks and reconciles restored data.

  • Critical Service Recovery Objectives Matrix (RTO, RPO, MTD)Excel

    in Cyber Resilience & Recovery

    The Objectives sheet sets a recovery time and a recovery point objective per function, and MX-05 covers the extreme scenario of a destructive attack.

  • Clean-Room Recovery & Rebuild ChecklistExcel

    in Cyber Resilience & Recovery

    CG-01 to CG-05 and CG-12 to CG-14 bring backups into use without risk to the network or data; CG-01 to CG-03 restore in a separate environment; CG-17 and CG-18 reconcile restored data.

  • Backup Operations & Restore Test ProcedureWord

    in Backup & Restore Assurance

    Routines 1 and 3 document backup and restoration, routines 3 and 4 test them, and routine 4 restores into segregated systems and reconciles the data.

  • Backup Coverage & Retention MatrixExcel

    in Backup & Restore Assurance

    The Data Sets sheet sets the scope and minimum frequency of each backup by data criticality and the Copies sheet shows the redundancy the copies give.

  • Restore Test WorkbookExcel

    in Backup & Restore Assurance

    The Tests and Test Plan sheets test backup, restoration and recovery periodically, the Services sheet holds recovery objectives, and the Tests sheet records checks on restored data.

Text: Regulation (EU) 2022/2554, as published in the Official Journal of the European Union, from EUR-Lex. Only the Official Journal text is authentic.