If you work at a bank, an insurer or an investment firm, your digital operational resilience is governed by DORA, not NIS2. EU lawmakers set it up that way on purpose, and national NIS2 laws follow suit. Yet the two regimes still meet: some of your suppliers fall under NIS2, with their own audits and their own reporting deadlines. If the contract does not align the two, you will learn about an incident too late, when you have four hours to report it.
In brief
- For financial entities in scope of DORA, its rules on ICT risk management, incident reporting, resilience testing and third-party risk apply instead of the corresponding NIS2 rules.
- Not every company in a financial group is a DORA entity. DORA has a closed list, and anything outside it needs a separate check against national NIS2 law.
- Your supplier may be a NIS2 entity, for example if it provides managed IT services. Its NIS2 audit is useful evidence, but it is not about the service it provides to you.
- Under DORA, the initial notification is due four hours after an incident is classified as major. The supplier's NIS2 deadline is not built around that, so the contract has to close the gap.
NIS2 vs DORA: which one applies to a financial firm?
The NIS2 Directive (EU 2022/2555) is the general cybersecurity framework for critical sectors. DORA (Regulation EU 2022/2554) deals specifically with digital operational resilience in financial services and has applied since 17 January 2025.
NIS2 settles the relationship itself. Recital 28 states that DORA is a sector-specific act in relation to NIS2: for ICT risk management, incident management and reporting, resilience testing, information sharing and ICT third-party risk, DORA's provisions apply instead. Member States therefore do not apply NIS2's risk management, reporting, supervision and enforcement provisions to financial entities covered by DORA.
National laws follow the same logic. Hungary's Cybersecurity Act (Act LXIX of 2024), for example, excludes DORA entities from its essential and important entity categories but still applies its incident handling rules to them, with specific deviations. A bank or insurer does not need to run two parallel compliance programmes, but its incident data still reaches the national cybersecurity system.
A group is not a single entity
Article 2 of DORA gives a closed list: credit institutions, payment and e-money institutions, investment firms, insurers and reinsurers, insurance intermediaries, fund managers, occupational pension funds and a few other categories. Anything not on the list is outside DORA, even if it belongs to a financial group.
In practice, several regimes can coexist within one group. The bank and the insurer are DORA entities. A standalone, non-bank leasing company is not on DORA's list. The group's own IT services subsidiary counts as an ICT third-party service provider under DORA, and depending on its size and activities it may also fall under national NIS2 law.
So "we are a financial firm, DORA applies to us" is not a complete answer. You need to go through the group entity by entity and record which regime applies, who supervises it, and which service relies on which other entity.
Your supplier may be a NIS2 entity
Annex I of NIS2 lists "ICT service management (business-to-business)" as a sector in its own right, covering managed service providers and managed security service providers. The definition is broad. A managed service provider is anyone providing services related to the installation, management, operation or maintenance of ICT products, networks, infrastructure or applications, on site or remotely.
A supplier that runs, supports or remotely maintains an application for you may therefore fall under NIS2 once it reaches medium-enterprise size. For the supplier, that means registration, recurring audits and its own reporting obligations to a national authority.
Hungary shows what this looks like once it becomes real. The first mandatory NIS2 audit deadline there was 30 June 2026. According to the supervisory authority, SZTFH, 2,194 organisations completed the audit and almost 90 percent passed. Among the frequent weaknesses, it highlighted poor documentation of remote access solutions.
For a financial client, that last finding matters. A supplier's remote access usually leads straight into your systems.
Two audits, two different questions
Under DORA, the financial entity is responsible for assessing and managing its ICT third-party risk. A supplier's NIS2 audit is a useful starting point: it shows whether the company has working risk management, backups, access control and an incident process.
But the audit covers the supplier as a whole, not the service it provides to you. It does not tell you where your data sits, who can access it, how fast your service can be restored, or how you can exit the contract. Those answers come from the contractual provisions required by DORA Article 30 and from your own risk assessment.
In my view, the sensible approach is to ask for the summary of the supplier's NIS2 audit and its remediation plan for any findings, and to build that into your DORA assessment. Your questionnaire can then focus on the gap: what the audit does not cover. The supplier benefits too, because it does not have to prove the same thing three different ways.
The two incident clocks do not tick together
This is where it is easiest to get things wrong. The two regimes measure time differently:
| DORA (financial entity) | NIS2 (supplier) | |
|---|---|---|
| First notice | Within 4 hours of classifying the incident as major, and no later than 24 hours after becoming aware of it | Early warning within 24 hours |
| Intermediate report | Within 72 hours of the initial notification | Incident notification within 72 hours |
| Final report | Within one month of the latest intermediate report | Within one month of the incident notification |
| Reported to | The financial supervisor | The national CSIRT or competent authority |
Sources: Commission Delegated Regulation (EU) 2025/301 supplementing DORA; NIS2 Article 23.
If something happens at your supplier that affects your service, NIS2 does require it to inform affected customers, but only "where appropriate" and "without undue delay": no hour limit and no set content. The hour-based deadlines run towards the authority. Your four-hour clock can only start once you know about the incident and have enough information to classify it.
That is why the contract has to state separately how quickly and with what information the supplier notifies you, who the contact is at night and at weekends, and what data it provides for classification. That deadline has to fit your DORA process, not the supplier's NIS2 obligation.
Both regimes put management on the hook
On one point the two regimes say the same thing: cybersecurity is a management responsibility. Under DORA Article 5, the management body bears ultimate responsibility for managing ICT risk. NIS2 Article 20 requires management bodies to approve cybersecurity risk-management measures and their members to follow training.
That raises a practical question when you choose a supplier: does its management understand what it is signing up to? For many small and mid-sized IT firms, NIS2 is the first regulation that places a personal burden on the managing director. If the supplier's director cannot tell you in a meeting who owns incident handling, that tells you more than any completed questionnaire.
What we do differently at FrontX
- We map entity by entity. Before writing requirements for a system or service, we record which legal entity falls under which regime and who relies on whom.
- We write requirements in business terms. Incident notification, access management and exit planning are part of the specification, not a legal annex added at the end.
- We know both sides. Our team members have worked on the client side at financial institutions, so we know what evidence supervisors expect and what a supplier can realistically provide. That is the basis of our digital transformation consulting service.
For DORA contract content, see our article DORA in practice: what your IT suppliers need to know, and for how pricing models interact with DORA, fixed price vs time and material.
If you are working out which rules apply to which of your suppliers, and how to get that into your contracts, we are happy to walk through it with you: book a free consultation.
Frequently asked questions
Does NIS2 apply to banks and insurers?
For financial entities in scope of DORA, DORA applies instead of the NIS2 rules on risk management and incident reporting. National NIS2 laws generally exclude them from the essential and important entity categories, although some, such as Hungary's, still apply incident handling rules to them with deviations.
What is the difference between NIS2 and DORA?
NIS2 is a directive that sets a general cybersecurity framework for critical sectors and is transposed into national law by each Member State. DORA is a directly applicable regulation for financial services, with more detailed rules on ICT risk management, incident reporting, resilience testing and third-party risk.
Does NIS2 apply to IT suppliers of financial institutions?
It can. NIS2 covers managed service providers and managed security service providers as a sector in their own right, typically from medium-enterprise size upwards. A supplier that operates, supports or remotely maintains systems for a bank may therefore have its own NIS2 obligations alongside its DORA contract obligations.
Does a supplier's NIS2 audit replace the DORA third-party assessment?
No, but it is a good starting point. The audit covers the supplier as a whole, while DORA asks about the risk of the specific service you receive: data location, access, recovery and exit options. Use the audit results in your assessment and narrow your questionnaire to the gaps.
How quickly must a major incident be reported under DORA?
The initial notification is due within four hours of classifying the incident as major, and no later than 24 hours after becoming aware of it. The intermediate report follows within 72 hours and the final report within one month.
László Behán is Managing Director and Co-Founder of FrontX Kft. He was previously CIO of Signal Insurance, Deputy IT Director and Head of Development at Groupama Insurance, and Operations Director and board member at LeasePlan Hungaria. He has 20 years of IT and business leadership experience in financial services. LinkedIn profile


