Frameworks

What is the difference between NIS2 and DORA?

Direct answer

NIS2 and DORA are two EU frameworks for cybersecurity and operational resilience that came into force around the same time and overlap heavily, but they are not interchangeable. NIS2 (Directive (EU) 2022/2555) is a cross-sector cybersecurity directive covering many industries; DORA (Regulation (EU) 2022/2554) is a finance-specific regulation for digital operational resilience.

Where both could apply to the same organisation, DORA generally takes precedence for ICT risk in financial services as the more specific law, the lex specialis principle. A financial entity can therefore be in scope for both, with DORA governing its ICT risk and NIS2 relevant to the extent DORA does not cover. The two differ on instrument, scope, and specificity. NIS2 is a directive, so it is transposed into each member state's national law and its details can vary by country. DORA is a regulation, so it applies directly and uniformly across the EU without transposition. NIS2 spans many sectors; DORA is confined to financial entities and their ICT providers. DORA is also more prescriptive on ICT specifics, such as the register of information and threat-led penetration testing, than NIS2's more general risk-management measures. Where a financial entity would fall under both, DORA is treated as the more specific regime for its ICT risk, and it prevails on the matters it covers. NIS2 recognises this relationship, so the two are designed to fit together rather than duplicate. In practice, a bank manages its ICT risk under DORA and does not also apply NIS2's general measures to the same ground. For a financial entity in scope for both: determine your DORA obligations for ICT risk first, since they are the more specific and prescriptive. Then confirm what, if anything, NIS2 adds beyond DORA's coverage for your organisation, which depends partly on your member state's transposition. The efficient path is to map the shared requirements once, as most of the risk-management and supply-chain substance is common, and only maintain the genuinely distinct pieces separately.

How do the two texts settle the overlap?

The rule is written into both texts. Article 1(2) of DORA states that, for financial entities identified as essential or important entities under the national rules transposing Article 3 of NIS2, DORA is a sector-specific Union legal act for the purposes of Article 4 of NIS2.

Article 4(1) of NIS2 then sets the consequence: where a sector-specific Union legal act requires essential or important entities to adopt cybersecurity risk-management measures or to notify significant incidents, and those requirements are at least equivalent in effect, the relevant NIS2 provisions do not apply to those entities, including supervision and enforcement under Chapter VII. Recital 28 of NIS2 is explicit about DORA: its provisions on ICT risk management, ICT-related incident management and reporting, digital operational resilience testing, information-sharing arrangements and ICT third-party risk apply instead of those of NIS2.

The carve-out has limits. Article 4(1) adds that NIS2 keeps applying to entities in a sector that the sector-specific act does not cover. And under Article 2(10) of NIS2, entities that a member state exempted from DORA under its Article 2(4) fall outside NIS2 as well.

NIS2 lists only a part of the financial sector. Its Annex I covers banking (credit institutions as defined in Article 4(1) of Regulation (EU) No 575/2013) and financial market infrastructures (operators of trading venues and central counterparties). Insurers, investment firms, payment institutions and most of the other financial entities in DORA’s Article 2(1) are not listed in NIS2 annexes, so for them DORA is the only one of the two regimes in play. See who DORA applies to.

For the banks and market infrastructures that sit in both, the link to NIS2 does not disappear. Recital 28 asks member states to keep the financial sector in their cybersecurity strategies and lets national CSIRTs cover it. Under DORA Article 19(6), the competent authority passes details of major ICT-related incidents to the competent authorities, single points of contact or CSIRTs under NIS2, and Article 19(1) lets member states require entities to send their reports to them directly as well. Article 47 organises cooperation between DORA authorities and the NIS2 Cooperation Group.

How do incident reporting and penalties compare?

Both regimes report in three stages, but on different clocks and thresholds. Under NIS2 Article 23(4), a significant incident gets an early warning within 24 hours of becoming aware of it, an incident notification within 72 hours and a final report within one month (see NIS2 incident reporting). Under DORA, the incident is first classified as major using the criteria of Article 18. Article 5 of Delegated Regulation (EU) 2025/301 then requires the initial notification within four hours of that classification and no later than 24 hours from becoming aware of the incident, an intermediate report within 72 hours of the initial notification, and a final report no later than one month after the latest intermediate report (see DORA incident reporting).

Penalties are built differently too. NIS2 Article 34 sets minimum ceilings for fines: at least EUR 10 million or 2% of total worldwide annual turnover for essential entities, and EUR 7 million or 1.4% for important entities. DORA Article 50 leaves the administrative penalties and remedial measures to member states, sets the minimum powers competent authorities must have, and lets national law extend them to members of the management body and other individuals responsible for the breach.

What about ICT providers that serve financial entities?

Here the two regimes stack rather than replace each other. A cloud computing service provider, data centre service provider, managed service provider or managed security service provider can be an essential or important entity under NIS2 in its own right (Annex I, digital infrastructure and ICT service management). It is not a financial entity, so DORA does not carve it out of NIS2.

At the same time, DORA reaches the same provider through its financial clients: the contract terms of Article 30, the register of information and, for providers designated as critical under Article 31, direct oversight by the European Supervisory Authorities. Article 47 foresees coordination between DORA and NIS2 authorities for essential or important entities that are also designated as critical ICT third-party service providers.

How Acuna GRC handles it

Sources

  1. Directive (EU) 2022/2555 (NIS2), recital 28, Articles 2, 4, 23 and 34, Annex I
  2. Regulation (EU) 2022/2554 (DORA), Articles 1, 18, 19, 30, 31, 47 and 50
  3. Commission Delegated Regulation (EU) 2025/301, Article 5 (time limits for major ICT-related incident reports)

This page explains the rules in general terms and is not legal advice.

Frequently asked

Does NIS2 apply to insurers?

Not as financial entities. NIS2 lists banking and financial market infrastructures in Annex I and no insurance sector, so insurers and reinsurers are covered by DORA. An insurer could still fall under NIS2 through another activity listed in the annexes.

Is a bank that complies with DORA also compliant with NIS2?

For the matters DORA covers, NIS2 Article 4 means its risk-management, incident notification, supervision and enforcement provisions do not apply to the bank, so DORA compliance is what counts. National CSIRTs and NIS2 authorities can still receive information on its major incidents through DORA Article 19.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US