NIS2 Business Continuity Requirements: Backup, DR and Crisis Management

NIS2’s business continuity, backup, disaster recovery and crisis management measures. Reporting of significant incidents and supply chain requirements are explained under separate headings.
Technical summary
Technology
NIS2 (EU) 2022/2555, ISO 22301:2019, ISO/IEC 27001:2022
Topic
Continuity and crisis management obligations under NIS2
Level
Intermediate–advanced
Prerequisites
  • Basic ISMS or continuity management knowledge
  • Knowing the organization’s relationship with the EU (customers, subsidiaries, services)
In this article7 sections

The NIS2 Directive is mostly discussed in terms of firewalls, MFA and vulnerability management. Yet one of the mandatory risk management measures the Directive lists is business continuity itself: backup management, disaster recovery and crisis management. Below we interpret this obligation from a management system perspective, and explain its mapping to ISO 22301 and ISO/IEC 27001, the management body’s responsibility and the ways in which companies in Türkiye that don’t operate in the EU come up against these requirements. The details of technical controls are out of scope.

Continuity within NIS2 risk management measures

The NIS2 Directive (EU) 2022/2555 requires “essential” and “important” entities in scope to take appropriate and proportionate technical, operational and organizational measures to manage risks to their network and information systems (Article 21(1)). Article 21(2) requires these measures to be based on an “all-hazards” approach and to include at least certain topics. The topics directly related to continuity:

Article 21(2) Item Link to continuity
(b) Incident management The trigger for moving from incident to recovery
(c) Business continuity: backup management, disaster recovery and crisis management A direct continuity obligation
(d) Supply chain security Critical supplier outage
(f) Assessing the effectiveness of measures Exercise and test evidence
(j) Multi-factor authentication, secured communications, secured emergency communication systems within the entity Communication during a crisis

Take the phrase “all hazards” seriously. The continuity plan must cover not only cyber attacks but also physical events that can affect network and information systems: a fire in the server room, a UPS failure, a long power outage, water coming through the ceiling. This matches ISO 22301’s impact-focused approach, which is independent of the source of risk. The ransomware scenario isn’t the only scenario.

The Directive largely leaves the details of the measures to member states’ national legislation and the Commission’s implementing acts. For example, Implementing Regulation (EU) 2024/2690 separately details business continuity and crisis management for certain types of digital service such as DNS service providers, cloud, data centers, managed service providers and managed security service providers. Which national legislation an entity in scope is subject to is determined by the member state it operates in.

Expectations for backup, DR and crisis management

Article 21(2)(c) lists three elements together. From a management system perspective, the expected outputs for each can be interpreted as follows:

Backup management

  • A policy defining which data is backed up, how often and for how long it’s kept; the frequency derived from RPO targets,
  • Isolating backups from the main systems and main identity infrastructure; although the Directive doesn’t specify a technical method, keeping at least one copy immutable or offline against ransomware risk is good practice,
  • Regular restore tests and their records.

A weakness you may come across is the backup server being a member of the production domain and the backup repository being accessible with the same admin accounts. When an attacker gets domain admin rights, they delete the backups too. The question asked in an audit isn’t “Are backups taken?”; it’s “How do you prove they can be restored?” For how to prepare the evidence set, see the guide backup and restore audit evidence.

Disaster recovery

  • RTO/RPO targets for critical services based on a business impact analysis,
  • A technical strategy that achieves the targets (restore from backup, replication, secondary site) and the recovery order,
  • Tested recovery procedures and comparison of test results with targets.

The recovery order is missing from most plans. Starting the application server before the domain controller, DNS and DHCP are up wastes hours; so does starting the application layer before the database is ready. The order must be written down.

Crisis management

  • A crisis management team with defined authority, and activation criteria,
  • Internal communication channels that can work independently of the corporate infrastructure,
  • A communication flow with customers, suppliers and authorities.

Crisis management intersects directly with the reporting obligation in Article 23. Under Article 23 of NIS2, entities in scope report significant incidents without undue delay. The general timeline is an early warning within 24 hours at the latest of becoming aware of the incident, an incident notification within 72 hours at the latest and a final report within one month at the latest of the incident notification. For trust service providers, there’s a specific 24-hour period for reporting relevant significant incidents. If the incident is still ongoing at the time of the final report, a progress report is submitted, with the final report given within one month of the incident being handled. The competent authority and national implementation are confirmed for the relevant country. Because of these deadlines, the notification decision is on the agenda of the crisis team’s first meeting. For the crisis team structure and stakeholder communication, see the guide crisis management and crisis communication plan.

Mapping to ISO 22301 and ISO 27001

NIS2 isn’t a management system standard and doesn’t mandate a particular standard; but Article 21(1) expects measures to take relevant European and international standards into account. An organization certified to ISO 22301 and ISO/IEC 27001:2022 can meet most of the continuity topic with its existing structure. The mapping below is a starting point; extend it according to the additional requirements of national legislation.

NIS2 expectation ISO 22301:2019 ISO/IEC 27001:2022 Annex A
Continuity and DR planning 8.2 BIA and risk assessment, 8.3 strategies, 8.4 plans 5.29 Information security during disruption, 5.30 ICT readiness for business continuity
Backup management 8.3 strategies and solutions (resource requirements) 8.13 Information backup
Redundancy 8.3 strategies and solutions 8.14 Redundancy of information processing facilities
Crisis management and communication 8.4.2 Response structure, 8.4.3 Warning and communication 5.24–5.26 Incident management planning and response
Assessing effectiveness 8.5 Exercise program, 9.1–9.2 monitoring and internal audit 5.35 Independent review
Management responsibility 5.1 Leadership, 9.3 Management review Main text 5.1 and 9.3 (outside Annex A)

The trap in the mapping is scope. ISO 22301 scope is often limited to certain products and services; NIS2 targets all the network and information systems the entity uses to provide in-scope services. If the certificate’s scope doesn’t include the service within NIS2 scope, the mapping is misleading. The certificate hangs on the wall; the scope is in its annex. For the standard’s clause structure and what it shares with ISO 27001, see the article ISO 22301 requirements.

The management body’s responsibility

NIS2’s most notable innovation from a management system perspective is Article 20. The entity’s management body approves the risk management measures in Article 21, oversees their implementation and can be held liable for infringements. Members of the management body are also expected to receive training. On the continuity side, in practice this means:

  • Formal approval by the management body of RTO/RPO targets and accepted residual risks,
  • Regular presentation of exercise results and open actions in management review,
  • Training and exercise participation for management body members suited to their roles in the crisis team,
  • Recording budget and resource decisions against the gaps between targets and current capacity.

The last item is the most useful in practice. If a four-hour RTO was approved and the budget for a secondary site was rejected, that decision must be in writing. Otherwise, after an outage, the question comes back to the IT team.

The Directive (Article 34) also regulates how the maximum administrative fines are set: the maximum is at least €10 million for essential entities and at least €7 million for important entities, or 2% of total worldwide annual turnover for essential entities and 1.4% for important entities, whichever is higher. From a management perspective, the real change is that responsibility is explicitly moved from the technical team to the management body.

Being affected through the supply chain

Whether a company established in Türkiye falls directly within scope is examined based on the type of entity, activity in the EU, size, exemptions and the relevant member state’s implementing legislation. Companies in Türkiye can come up against these requirements in three ways:

  1. EU customers: Articles 21(2)(d) and 21(3) require entities in scope to take into account the security practices and vulnerabilities of their direct suppliers. That’s why EU customers pass requirements such as a continuity plan, recovery targets, incident reporting and test evidence on to their suppliers through contracts and questionnaires.
  2. Digital service providers serving the EU: For entities that provide certain types of digital service in the EU, such as cloud, data center and managed services, but aren’t established in the EU, the Directive requires a representative to be designated in a member state (Article 26).
  3. Groups with an EU subsidiary: If the EU subsidiary is in scope, intra-group IT services and shared infrastructure effectively have to be managed according to NIS2 requirements.

The first route is the most common, and its effect depends on the contract. The customer asks the supplier for a service continuity assurance consistent with its own RTO; the questionnaire usually arrives with questions like “What’s your RTO, when was your last DR test, can you share the evidence?” For how to prepare for these requests, the article business continuity at critical suppliers details the questions the customer side will ask and the contract clauses. Mapping technical measures to controls is covered in the guide NIS2 technical measures.

Preparation roadmap

Whether you’re directly in scope or facing a customer request, preparation on the continuity side within information security compliance can proceed in this order:

  1. Determine the scope and how you’re affected: Direct scope, a representative obligation or a customer contract; which applies?
  2. Do a BIA for in-scope services: Identify the network and information systems supporting the services, their dependencies and the impact of disruption.
  3. Have the management body approve the targets: RTO/RPO and accepted residual risks should be written decisions.
  4. Do a gap analysis: Compare your existing backup, DR and crisis management arrangements with the mapping table above.
  5. Integrate crisis management with notification deadlines: Add the 24-hour and 72-hour thresholds to the crisis team’s task list.
  6. Test and prove it: Measure effectiveness with restore tests, a DR test and a tabletop crisis exercise; take the results to management review.

You can address scoping and gap analysis through NIS2 scope and requirements preparation work, and the continuity management system through the ISO 22301 business continuity management approach.

Frequently asked questions

Does NIS2 apply to companies in Türkiye?

Direct scope is determined by the type of entity, activity in the EU, size, exemptions and the relevant member state’s implementing legislation. EU customers may also require continuity and incident reporting conditions from their suppliers by contract. Organizations offering certain digital services in the EU may have to appoint a representative; groups whose EU subsidiary is in scope are also affected indirectly.

Does an ISO 22301 certificate meet the NIS2 continuity requirement?

It supports it to a large extent but doesn’t provide automatic compliance. The certificate’s scope must include the services within NIS2 scope and the network and information systems supporting them, backup and crisis management must be integrated with incident reporting deadlines, and the additional requirements of national legislation must be checked.

What are the incident reporting deadlines in NIS2?

Under Article 23 of NIS2, entities in scope report significant incidents without undue delay. The general timeline is an early warning within 24 hours at the latest of becoming aware of the incident, an incident notification within 72 hours at the latest and a final report within one month at the latest of the incident notification. For trust service providers, there’s a specific 24-hour period for reporting relevant significant incidents. If the incident is still ongoing at the time of the final report, a progress report is submitted, with the final report given within one month of the incident being handled. The competent authority and national implementation are confirmed for the relevant country.

What is the board’s responsibility under NIS2?

Under Article 20, the management body approves risk management measures, oversees their implementation and can be held liable for infringements; members are also expected to receive training. From a continuity perspective, this means targets, residual risks and exercise results are approved and monitored by the management body.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles