An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesDisaster Recovery and NIS2
Business Continuity / 2026-10-09

Disaster Recovery and NIS2

NIS2 Article 21(2)(c) includes disaster recovery within business continuity and crisis management. A recovery programme should identify which services to restore, what those services depend on and how the organisation will verify that recovered systems can operate safely. Specific technical requirements also apply to the provider categories covered by Implementing Regulation (EU) 2024/2690.

Disaster Recovery Is a Service Restoration Capability

Disaster recovery deals with restoring systems, data and the technical dependencies needed to deliver an interrupted service. Business continuity can also involve nontechnical workarounds, alternate premises or reduced service delivery while restoration proceeds. Neither concept replaces the other.

For example, recovering a customer portal might require restoring its database, identity provider, network rules and access to encryption keys. A working server image alone does not prove the portal is usable. The recovery plan should name the service owner responsible for accepting the result.

Map Dependencies Before Writing Recovery Steps

Begin with the outcomes of the business impact analysis and technical dependency mapping. Identify the services whose disruption would cause the greatest harm and the infrastructure that supports each one. Shared components may deserve earlier restoration than the applications they support.

Include externally hosted systems, network connectivity, privileged accounts, configuration repositories and DNS where relevant. Document assumptions about what will remain available during a cyber incident. If recovery relies on a compromised identity platform, an alternative trusted administrative route may be necessary.

Set Objectives That Can Be Tested

A recovery time objective expresses the target period for restoring a specified service following disruption. A recovery point objective expresses the acceptable period of data loss. These are management choices informed by operational impact, contractual commitments and risk, not universal numbers prescribed for all NIS2 entities.

Translate objectives into a restoration sequence and resource requirements. An objective of four hours is unsupported if necessary hardware, backups or supplier assistance cannot be obtained in that period. Record whose approval is required when realistic capability falls short of an agreed target.

Restore Into a Trusted State

Ransomware and other intrusions complicate recovery because the latest backup or system image may contain malicious changes. Define how restoration candidates are checked for integrity and how clean systems are isolated from affected production environments.

Plan for credentials, keys, patches and configuration baselines required to return services to operation. A recovery may need security validation before users are reconnected. The incident response team should coordinate with recovery personnel so that restoration does not destroy forensic evidence needed for investigation.

Test the Whole Recovery Path

A database restoration test demonstrates one capability, while a service recovery exercise tests dependencies, access, communications and decision-making. Run exercises in conditions that resemble plausible failures, including loss of a primary hosting region or administrative account.

Track elapsed time, data recovered, integrity findings, required manual interventions and deviations from the plan. Record corrective action owners and retest consequential failures. For providers in scope of Regulation 2024/2690, Annex 4.1 expressly addresses testing and reviewing business continuity and disaster recovery plans.

Check Which Rules Apply

Article 21 provides the general NIS2 continuity framework. Annex 4 of Regulation 2024/2690 adds defined business impact analysis, planning, testing and backup measures for its specified types of digital and ICT entities. Its detailed provisions should not be presented as automatically applying to every NIS2 organisation.

The applicable national transposition measures and competent authority guidance remain important. Keep a record of the entity classification, laws consulted, recovery plan version and last meaningful test so that the decision can be reviewed after major changes.

Questions on the text

Does NIS2 specify one disaster recovery time for every company?

No. Article 21 does not prescribe a universal restoration time for all covered entities. Objectives should be justified by risk, service impact and applicable additional legal requirements.

Is restoring data enough to demonstrate disaster recovery?

Not necessarily. Recovery requires restoring usable services and verifying the integrity and security of the restored environment.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.