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.
HomeArticlesNIS2 Business Continuity and Cyber Crisis Management
Business Continuity / 2026-10-09

NIS2 Business Continuity and Cyber Crisis Management

Article 21(2)(c) of the NIS2 Directive includes business continuity, backup management, disaster recovery and crisis management among the minimum cybersecurity risk-management measures. Organisations within scope need continuity arrangements that reflect their actual services and risks, alongside the applicable national implementing law.

What Article 21 Requires

Article 21(2)(c) names business continuity, including backup management and disaster recovery, and crisis management. The Directive also requires measures to be appropriate and proportionate to the risks faced by the entity. It does not prescribe one universal recovery time, backup frequency or testing interval for every sector. Decisions should follow the significance of each service and the consequences of disruption.

A hospital's clinical systems, an energy operator's control environment and a managed service provider's customer platform may all require different recovery priorities. The common principle is to identify what must continue, how an outage would affect the service, and what resources are needed to restore an acceptable operation.

Identify Critical Services and Dependencies

Start with a business impact analysis. List the services the organisation must sustain, the systems and data they depend on, and the staff, facilities, external providers and connectivity required to deliver them. Distinguish the impact of losing a single application from losing a shared identity service, network connection or site.

Record service owners and recovery priorities. Dependencies can determine recovery order: restoring an application before its identity platform or database is available may not return the service to users. Consider both cyber incidents and other interruptions within the all-hazards approach.

Plan for Recovery and Crisis Decisions

A continuity plan should explain how a disruption is detected, who decides to activate contingency arrangements, which alternate operating procedures are available and when recovery is considered complete. Disaster recovery instructions should describe the technical restoration sequence. A crisis management process addresses leadership decisions, coordination and communication when ordinary operational authority is insufficient.

Define responsibilities and alternatives for unavailable decision-makers. Establish escalation criteria tied to service disruption rather than vague labels. Plans should account for dependencies outside the organisation, including contracted hosting and telecoms services.

Backups Are Necessary but Not Sufficient

A successful backup job does not prove that an operational service can be restored. Organisations should assess which data, system images, configurations and credentials are needed for recovery. Protect backup copies against the same compromise that affects production systems, and test restoration into a controlled environment.

Recovery time objectives describe the intended maximum restoration time; recovery point objectives describe the acceptable amount of data loss expressed as time. Both should be supported by tested capability, not merely written into a policy.

Test, Review and Keep Evidence

Exercises can expose missing authority, outdated contact details and restoration steps that depend on unavailable systems. Test meaningful scenarios and record the conditions, actual elapsed recovery times, issues found and assigned corrective actions. Follow through until critical gaps are resolved.

Maintain current versions of the business impact analysis, continuity plans, backup procedures, restoration results, exercise records and management decisions. For certain digital and ICT providers, Implementing Regulation (EU) 2024/2690 contains more specific technical and methodological requirements; ENISA guidance helps explain these, but does not extend that implementing regulation to every NIS2 entity.

National Implementation and Next Review

NIS2 is a Directive. A covered organisation should check the law and competent authority guidance of the Member State with jurisdiction, including any sector-specific requirements. Align continuity governance with incident reporting, supplier risk and management oversight, while keeping their distinct legal requirements clear.

Review plans after substantial architecture changes, new critical suppliers, incidents or test failures. A dated scope and legal review helps explain why particular continuity controls were selected.

Questions on the text

Does NIS2 require a business continuity plan?

Article 21(2)(c) requires appropriate business continuity measures. The exact documentation and operating requirements depend on applicable national law and, for certain entities, more specific EU implementing rules.

Does NIS2 prescribe a universal recovery time?

No single recovery time applies to all covered entities under Article 21. Set and test objectives based on service needs, risks and any applicable additional requirements.

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.