NIS2 vs DORA: third-party risk requirements compared
Short answer. DORA is a regulation that applies directly to EU financial entities and prescribes exactly how to manage ICT third-party risk — register of information, mandatory contract provisions, exit strategies, oversight of critical providers. NIS2 is a directive covering 18 sectors that requires the same outcomes without prescribing the mechanics.
Last reviewed: 31 July 2026.
NIS vs DORA in one paragraph
Both regimes want the same thing: organisations that understand and control their dependency on third parties. DORA — Regulation (EU) 2022/2554, applying from 17 January 2025 — tells financial entities precisely how. NIS2 — Directive (EU) 2022/2555 — tells everyone else what outcome to reach and leaves the method to them, subject to proportionality.
If you build for DORA you will satisfy NIS2's supply chain measure comfortably. The reverse is not true.
Which regime applies to you
The overlap rule. NIS2 Article 4 provides that where sector-specific Union legal acts require 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 corresponding NIS2 provisions do not apply. DORA is the archetypal case: banking and financial market infrastructure entities are in Annex I of NIS2, but DORA governs their ICT risk management and incident reporting.
Two caveats. First, "corresponding" is provision-by-provision, not wholesale — NIS2 duties outside DORA's subject matter, such as registration with the national authority, can still apply, and national transposition varies on the detail. Second, a financial group frequently contains entities that are not financial entities under DORA. Map at entity level.
Third party risk compared
The register of information
DORA's register of information is the single most visible difference. Financial entities must maintain — and report to supervisors in a specified format — details of every contractual arrangement for the use of ICT services, including the provider, the function supported, whether it supports a critical or important function, the data involved, locations, and the chain of subcontracting for critical functions.
NIS2 has no equivalent filing. But the underlying data is the same data you need to satisfy Article 21(2)(d), and building the register-of-information dataset is a reasonable target even for a non-financial entity: it forces you to link supplier → service → criticality → data → location, which is exactly what supervisors probe. See How to build a NIS2 vendor register.
Contract requirements compared
DORA Article 30 sets a baseline for all ICT contracts — clear service description, locations of service provision and data processing, data protection and availability commitments, assistance at no additional cost during incidents, cooperation with authorities, termination rights, notice periods.
For services supporting critical or important functions it adds more: full service levels with precise quantitative targets, notice and reporting obligations, incident support, participation in the entity's testing, unrestricted rights of access, inspection and audit, and detailed exit strategies.
For NIS2 you draft the equivalent yourself. The core clause set borrows heavily from DORA's list for that reason — it is the best-tested articulation of what "security-related aspects of the relationship" means in a contract.
Incident reporting compared
Both regimes reward the same operational capability: knowing quickly, deciding significance against written criteria, and filing on time. If you run both, build one incident pipeline with two output templates rather than two processes.
Running one programme for both
For groups spanning financial and non-financial entities:
- Build to DORA, report to both. The DORA dataset is a superset; deriving NIS2 evidence from it is straightforward.
- One supplier register, with flags for which regime and which entity each relationship falls under. Do not maintain two.
- One contract schedule with tiered annexes — the DORA critical-or-important annex, a general security annex, and a light annex for low-risk suppliers.
- One assessment method, with the DORA-specific additions (concentration, exit, criticality determination) as extra fields rather than a separate workflow.
- Map obligations per legal entity, per member state. This is the part organisations consistently underestimate, and it is where the Article 4 equivalence analysis has to be recorded.
- Record the equivalence reasoning. If you are relying on Article 4 to disapply NIS2 provisions, write down why, per provision. That memo is the answer when a national authority asks why you did not report to them.