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.
HomeArticlesDeveloping a NIS2 Business Continuity Plan
Business Continuity / 2026-10-09

Developing a NIS2 Business Continuity Plan

A NIS2-aligned business continuity plan should connect critical services to their dependencies, identify disruption scenarios, assign decision-makers, establish recovery arrangements and produce evidence from realistic testing. Article 21(2)(c) supplies the EU framework; applicable national law and, for specified digital and ICT providers, Regulation 2024/2690 determine further details.

Establish Scope and Ownership

Identify the legal entity, covered services and accountable owner of the plan. A plan intended for a whole corporate group can be useful operationally, but it must not obscure the responsibilities of individual entities. Define which services, locations, systems and third parties are within scope.

Keep an approval record and version history. The plan needs an owner who can coordinate updates after operational changes, not only someone who stores the document.

Perform a Business Impact Analysis

For each service, identify the consequences of interruption over time. Consider service users, contractual delivery, financial effects, safety where relevant and dependencies on other organisations. The analysis should help rank recovery priorities rather than merely produce a catalogue of systems.

Describe important assumptions explicitly. If a business function depends on a shared authentication platform or external telecoms link, the plan must reflect that link. For entities within Regulation 2024/2690, Annex 4.1.3 explicitly requires business impact analysis and continuity requirements derived from it.

Choose Continuity and Recovery Arrangements

Define how services continue in a degraded state and how the organisation will return to normal operations. Possible measures include alternate processing, reduced manual workflows, secondary facilities and tested backups. Match each proposed measure to the disruption it is intended to address.

Set service-specific recovery time and recovery point objectives when relevant, and confirm that infrastructure, personnel and supplier agreements can meet them. Document exceptions rather than presenting unsupported targets as proven capabilities.

Write Usable Activation and Escalation Instructions

State who can activate the plan, how the decision is recorded and how teams will communicate if primary systems are unavailable. Specify recovery order, responsibilities, required resources and the conditions for ending contingency operations.

Short checklists can assist responders under pressure, but they should be based on accurate technical procedures and contacts. Protect sensitive recovery details from inappropriate access while ensuring authorised responders can reach them in an outage.

Test and Maintain the Plan

Combine discussion-based exercises with practical restoration and service continuity tests. Choose scenarios that challenge assumptions, such as simultaneous loss of a supplier and its usual communications route. Observe actual recovery capability and document deviations.

Review plans after meaningful service changes, exercises and incidents. Track corrective actions to closure. The frequency should be justified by risk and applicable rules, including the specific testing requirements of Regulation 2024/2690 where it applies.

Create a Compact Evidence Record

Retain the approved plan, impact analysis, service-to-system dependencies, contact arrangements, supplier commitments, exercise outcomes and management review. An evidence record should establish what was tested and what failed, rather than merely state that testing occurred.

As the site covers an EU Directive, note the relevant Member State implementing law and any applicable sector or competent authority guidance. Review these sources when updating the plan. Link the continuity plan to incident handling, backups and crisis management while preserving their distinct purposes.

Questions on the text

Does a business continuity template alone establish NIS2 compliance?

No. A template must be adapted to actual services, risk, dependencies and applicable law, and the resulting arrangements should be tested.

What should management review?

Management should understand critical service priorities, approved recovery objectives, unresolved gaps, exercise findings and whether resources support the agreed arrangements.

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.