My customer is a bank. Does DORA apply to my IT company?
Not directly, but it reaches you through the contract. DORA keeps the bank fully responsible and prescribes what every ICT contract must say, from audit rights to exit plans. Separately, a medium-sized or larger managed service, cloud or data centre provider falls under the Dutch Cyberbeveiligingswet in its own right.
My customer is a bank. Does DORA apply to my IT company?
Not as a law you must comply with yourself, unless the European supervisors designate you as a critical provider. DORA puts the duties on the bank, the insurer or the investment firm. It then tells them exactly what their contract with you must contain, so the rules arrive on your desk as contract clauses instead of as a statute.
A second law may apply to you directly. If you run managed IT or security services, a cloud platform or a data centre and you are at least medium-sized, the Dutch Cyberbeveiligingswet has applied to your own company since 15 August 2026. Your bank customer being outside that law does not take you out of it.
Why DORA reaches you anyway
DORA lists ICT third-party service providers in its scope (Article 2(1)(u)), but the duties to manage ICT risk sit with the 20 kinds of financial entity in points (a) to (t). Article 28(1)(a) then closes the door on outsourcing the problem: the financial entity "shall, at all times, remain fully responsible" for complying with DORA.
A bank cannot meet that standard with a contract that leaves you free to change data centres without notice or to refuse an audit. So Article 30 lists the clauses every ICT contract must contain, and a longer list for contracts that support a critical or important function. The whole contract, service levels included, must sit in one written document.
What the contract will have to say
| Clause | Article | Which contracts |
|---|---|---|
Description of all services, and whether and on what terms critical functions may be subcontracted | 30(2)(a) | All ICT contracts |
Where services are provided and data is stored, with advance notice of a change | 30(2)(b) | All ICT contracts |
Access, recovery and return of data, including on insolvency or termination | 30(2)(d) | All ICT contracts |
Help with an ICT incident at no extra cost, or at a cost agreed in advance | 30(2)(f) | All ICT contracts |
Full cooperation with the bank's supervisors and resolution authorities | 30(2)(g) | All ICT contracts |
Termination rights and minimum notice periods | 30(2)(h) | All ICT contracts |
Taking part in the bank's security awareness and resilience training | 30(2)(i) | All ICT contracts |
Service levels with precise quantitative and qualitative targets | 30(3)(a) | Critical or important functions |
Business contingency plans that are implemented and tested | 30(3)(c) | Critical or important functions |
Taking part in the bank's threat-led penetration testing | 30(3)(d) | Critical or important functions |
Unrestricted rights of access, inspection and audit for the bank and its supervisors | 30(3)(e) | Critical or important functions |
An exit strategy with a mandatory transition period | 30(3)(f) | Critical or important functions |
What the bank will ask you for
Expect a request for your LEI. Every financial entity keeps a register of all its ICT contracts (Article 28(3)) and files it with DNB or the AFM once a year. Implementing Regulation (EU) 2024/2956 requires a valid and active Legal Entity Identifier or a European Unique Identifier (EUID) for every provider that is a legal person. A provider established outside the EU can only use an LEI. The same regulation asks for identifiers of your subcontractors that support the bank's critical or important functions, collected through you (Article 3(6)). If you do not know your own supply chain to that depth, the bank will find out when it fills in the register.
Your subcontractors are part of the deal
Delegated Regulation (EU) 2025/532 has applied to subcontracting since 22 July 2025. It requires you to monitor every subcontracted service that supports a critical or important function, and to pass the bank's audit and access rights down to your subcontractors. The bank must get a reasonable notice period to object to material changes. Subcontracting something the contract does not explicitly permit gives the bank a right to terminate (Article 6(c)).
Can DORA apply to you directly?
Only if you are designated.
On 18 November 2025 the European supervisors published the first list of 19 critical ICT third-party service providers, drawn from the registers banks filed. Those providers are overseen directly by the EBA, ESMA or EIOPA (Article 31). A provider not on the list may ask to be designated (Article 31(11)). Intra-group providers, and providers serving only financial entities in their own Member State, are exempt from designation (Article 31(8)).
The Cyberbeveiligingswet is a separate question
The Dutch implementation of NIS2 applies by sector and size, not by who your customers are. Managed service providers and managed security service providers form a sector of their own, and cloud and data centre services sit under digital infrastructure. At medium size or above you are at least a belangrijke entiteit.
Banks escape most of the Act because DORA covers the same ground.
Articles 22 and 31 of the Cyberbeveiligingswet switch off the duty of care and the incident reporting duty "op die entiteit": on the bank, not on you. A medium-sized managed service provider with only bank customers registers with the NCSC through mijn.ncsc.nl (Article 44) and reports significant incidents to the NCSC within 24 and 72 hours (Articles 26 and 27). Its supervisor is the RDI.
Questions and answers
We are a ten-person software company. Does any of this apply to us?
DORA's contract clauses do, because your bank customer has to include them. The Cyberbeveiligingswet does not reach managed service, cloud or data centre providers below medium size, which under the EU definition means fewer than 50 staff and turnover or balance sheet of at most EUR 10 million.
Can we refuse an audit clause?
Not in a contract that supports a critical or important function. Article 30(3)(e) requires unrestricted access, inspection and audit rights for the bank, a third party it appoints and its supervisors. The bank can agree on how audits are run, not on whether they happen.
Do we need an LEI?
If you are a legal person established in the EU, the bank needs your LEI or your EUID for its register. Outside the EU only an LEI works.
Are we a critical ICT third-party service provider?
Only if the European supervisors designate you. The first list of 18 November 2025 names 19 providers, and it is updated yearly (Article 31(9)).
Sources
- Regulation (EU) 2022/2554 (DORA), Articles 2, 28, 30 and 31EUR-Lex · 14 December 2022
- Commission Implementing Regulation (EU) 2024/2956: register of information templatesEUR-Lex · 29 November 2024
- Commission Delegated Regulation (EU) 2025/532: subcontracting of ICT services supporting critical or important functionsEUR-Lex · 24 March 2025
- Commission Delegated Regulation (EU) 2024/1773: policy on ICT services supporting critical or important functionsEUR-Lex · 13 March 2024
- European Supervisory Authorities designate critical ICT third-party providers under DORAESAs · 18 November 2025
- Directive (EU) 2022/2555 (NIS2), Annex I and Article 6(39)EUR-Lex · 14 December 2022
- Cyberbeveiligingswet, Stb. 2026, 187Staatsblad · 8 July 2026
- Cyberbeveiligingsbesluit, Stb. 2026, 189Staatsblad · 8 July 2026
- Infosheet registratieplicht CyberbeveiligingswetNCSC
Regulations
Cyberbeveiligingswet (Dutch NIS2)
The Cyberbeveiligingswet is the Dutch implementation of NIS2, Directive (EU) 2022/2555. It entered into force on 15 August 2026 and covers more than 8,000 organisations. Registration, the duty of care and the 24-hour and 72-hour reporting duties applied from day one. Banks are largely displaced to DORA by Articles 22 and 31, but their IT suppliers are not.
NextCommission review of sectors, size criteria and entity types; every 36 months thereafterChecked
Digital Operational Resilience Act (DORA)
DORA is Regulation (EU) 2022/2554. It has applied since 17 January 2025 to 20 categories of licensed financial entity, from banks to crypto-asset service providers. It requires an ICT risk management framework, major incident reporting within 4 hours of classification, an annual register of ICT contracts, and threat-led penetration testing every three years.
NextCommission review of DORA and report to Parliament and Council (Art. 58(1))Checked