Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Cloud and platforms

DORA and NIS2: what are the differences, and which text applies to a financial entity?

In brief

The differences between DORA and NIS2 start with their nature: DORA, Regulation (EU) 2022/2554, applies directly to financial entities, whereas NIS2, Directive (EU) 2022/2555, covers essential and important entities in the sectors of its annexes and operates through national law. Management Square compares the two texts here, article by article, and describes how they fit together for a financial entity.

Page contents

Regulation (EU) 2022/2554, known as DORA, “shall be considered to be a sector-specific Union legal act for the purposes of Article 4” of Directive (EU) 2022/2555, known as NIS2. Its Article 1, paragraph 2, provides for this for financial entities that national law identifies as essential or important. The differences between DORA and NIS2, adopted on the same day, 14 December 2022, begin with their nature.

DORA is a regulation: it has applied directly, since 17 January 2025 (Article 64), to financial entities, and reaches their IT providers through contracts and an oversight framework. NIS2 is a directive: it covers essential and important entities in the sectors of its annexes, in the terms of a national law. Our entries on the DORA regulation and the NIS2 directive define each text.

A sector-specific regulation, a cross-sector directive

DORA ends with the wording specific to regulations: it is “binding in its entirety and directly applicable in all Member States”. NIS2 required Member States, in its Article 41, to adopt their provisions by 17 October 2024 at the latest and to apply them from 18 October 2024. An organisation therefore reads its obligations in the national text.

Article 2, paragraph 1, of DORA lists twenty categories of financial entities (points (a) to (t)) and adds ICT third-party service providers (point (u)). Size does not serve as a general entry threshold: it adjusts the requirements, through the proportionality of Article 4 and the simplified framework of Article 16. NIS2 reasons by sector, then by size: its Article 2 covers entities of a type listed in Annex I or II that at least reach the size of a medium-sized enterprise, except for cases covered regardless of size.

The two scopes overlap: Annex I of NIS2 includes credit institutions, trading venues and central counterparties, as well as providers that DORA reaches by other means, such as cloud computing service providers.

Risks, incidents, third parties: obligations of unequal precision

On risk management, NIS2 requires “appropriate and proportionate” measures and sets a baseline of ten points (Article 21, paragraphs 1 and 2). DORA prescribes more. The management body shall “define, approve, oversee and be responsible for the implementation” of the ICT risk management framework (Article 5, paragraph 2). Chapter IV adds testing: at least annually, except for microenterprises, for systems that support critical or important functions (Article 24, paragraph 6) and, for entities identified by their authority, threat-led penetration testing at least every three years (Article 26, as corrected).

On incidents, the vocabulary already differs: “significant incident” for NIS2 (Article 23, paragraph 3), “major ICT-related incident” for DORA (Article 3, point 10). Article 23 of NIS2 provides for an early warning within 24 hours of becoming aware, a notification within 72 hours, then a final report no later than one month after that notification, sent to the national computer security incident response team (CSIRT) or the competent authority.

For DORA, Article 5 of Delegated Regulation (EU) 2025/301 sets the initial notification at no more than four hours after the incident is classified as major, and no more than 24 hours after the entity became aware of it. An intermediate report follows within 72 hours of that notification, then a final report no more than one month after that report or its last update, submitted to the financial supervisory authority. Our article on cyber crisis management places these notifications in the course of a crisis.

On third parties, NIS2 places supply chain security among its ten measures (Article 21, paragraph 2, point (d)). DORA devotes its Chapter V to the subject. Financial entities “shall at all times remain fully responsible” for their obligations (Article 28, paragraph 1). They keep a register of their contractual arrangements, include the clauses of Article 30 in these contracts and prepare exit strategies for services that support critical or important functions.

Who supervises, and under what threat of penalty

DORA entrusts supervision to the authorities that already supervise each category of entity: its Article 46 designates them by reference to the sectoral texts, with the European Central Bank for credit institutions classified as significant. NIS2 requires each Member State to designate competent authorities (Article 8) and CSIRTs (Article 10). Supervision there depends on the category: on-site inspections and regular security audits for essential entities (Article 32), ex post supervision for important entities (Article 33).

NIS2 itself sets a floor for maximum fines. For an infringement of Article 21 or 23, the maximum amount is at least EUR 10,000,000 or at least 2% of total worldwide annual turnover for an essential entity, and at least EUR 7,000,000 or at least 1.4% for an important entity, whichever is higher (Article 34, paragraphs 4 and 5). DORA puts no figure on any fine for financial entities: its Article 50 tasks Member States with laying down administrative penalties and remedial measures. Its only penalty amount concerns critical providers: a daily periodic penalty payment of up to 1% of average daily worldwide turnover, for up to six months (Article 35).

The differences between DORA and NIS2 in a table

DORA NIS2
Legal nature Regulation, directly applicable Directive, transposed by each Member State
Scope Financial entities (Art. 2) and their ICT service providers Essential and important entities in Annexes I and II
Authorities Financial supervisors (Art. 46) National competent authorities and CSIRTs
Risk management Detailed framework (Chapter II), testing (Chapter IV) Proportionate measures, baseline of Art. 21
Incident notification Major incident: 4 hours after classification, no more than 24 hours after awareness Significant incident: 24 hours, 72 hours, one month
Third parties Chapter V: register, contractual clauses, exit strategies Supply chain (Art. 21)
Penalties Laid down by Member States (Art. 50) Floors for maximum fines (Art. 34)

For a financial entity, which text applies

Article 4, paragraph 1, of NIS2 gives the rule. Where a sector-specific Union act imposes risk management measures or incident notifications at least equivalent in effect, the corresponding provisions of the directive, “including the provisions on supervision and enforcement laid down in Chapter VII”, do not apply to the entities concerned. The Commission’s guidelines on this Article 4 (communication 2023/C 328/02) list DORA among these sector-specific acts.

According to recital 28 of NIS2, which these guidelines take up, the provisions of DORA “should apply instead of” those of the directive, and Member States should not apply to financial entities those concerning risk management, reporting obligations, supervision and enforcement. A credit institution, a trading venue or a central counterparty, which the guidelines cite as present in both scopes, follows DORA on this basis for its measures, its notifications and its supervision. This reading, written in the conditional in the recital as in the guidelines, is confirmed in the national transposition law. Some checks remain to be carried out with your legal department:

  • Article 19, paragraph 1, of DORA allows Member States to decide that financial entities also send their notifications to the authorities or CSIRTs designated under NIS2;
  • within a group, each entity is qualified separately: one that does not appear in Article 2 of DORA, but falls within the scope of NIS2, follows the national transposition law.

A cloud computing service provider may combine both regimes: NIS2 in its own right, DORA through the clauses of its financial clients and, if it is designated as critical, through an oversight framework that applies “without prejudice to the application of Directive (EU) 2022/2555” (Article 32, paragraph 8).

What DORA requires of a banking project is covered in our article DORA for banks. For a group or a provider placed between the two texts, the first useful document is a table: each entity, the text it falls under, the authority to which it reports, the deadlines that apply. This table opens the alignment with DORA and NIS2 described in our page on cyber resilience.

FAQ

Frequently asked questions

Another question? Ask us

What is the difference between DORA and NIS2?

DORA is Regulation (EU) 2022/2554: it has applied directly, since 17 January 2025, to the financial entities listed in its Article 2 and governs their IT service providers. NIS2 is Directive (EU) 2022/2555: it covers essential and important entities in the sectors listed in its Annexes I and II, and its obligations apply through the national law that transposes it. Supervisory authorities, incident notification deadlines, the treatment of third parties and penalties differ as a result.

Must a financial entity subject to DORA also apply NIS2?

Article 1, paragraph 2, of DORA makes the regulation a sector-specific Union legal act for the purposes of Article 4 of NIS2. Under that Article 4, where the sector-specific act imposes requirements at least equivalent in effect, the corresponding provisions of the directive, supervision and enforcement included, do not apply to the entities concerned. A Member State may however decide, under Article 19 of DORA, that financial entities also send their notifications to the authorities or CSIRTs designated under NIS2: this point is checked in national law.

Are incident notification deadlines the same in DORA and NIS2?

No. Article 23 of NIS2 provides for an early warning within 24 hours of becoming aware of a significant incident, a notification within 72 hours, then a final report no later than one month after that notification. For DORA, Article 5 of Delegated Regulation (EU) 2025/301 sets the initial notification at no more than four hours after the incident is classified as major, and no more than 24 hours after the entity became aware of it. The intermediate report follows within 72 hours of that notification, and the final report no more than one month after the last intermediate report.

Does a bank's IT provider fall under DORA or NIS2?

It may fall under both, in different capacities. NIS2 covers it in its own right if it belongs to a type of entity in its annexes, for example providers of cloud computing services, data centre services or managed services, and if it meets the size conditions. DORA reaches it through the clauses its financial clients must include in their contracts and, if it is designated as a critical provider, through a European oversight framework that applies without prejudice to the directive.

What penalties do DORA and NIS2 provide for?

Article 34 of NIS2 requires Member States to set maximum fines of at least EUR 10,000,000 or at least 2% of total worldwide annual turnover for essential entities, and of at least EUR 7,000,000 or at least 1.4% for important entities, whichever is higher. DORA does not put a figure on penalties for financial entities: its Article 50 tasks Member States with laying them down. The only penalty amount in the regulation is the periodic penalty payment applicable to critical third-party providers, capped by Article 35 at 1% per day of average daily worldwide turnover.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.