For ICT service providers working for banks, the Digital Operational Resilience Act (DORA) mostly works through contracts. DORA (Regulation (EU) 2022/2554), applicable since 17 January 2025 (Article 64), places its obligations on banks and other financial entities, not directly on most ICT providers. Those obligations reach you through your contracts: Article 30 lists the clauses every ICT contract must contain, with stricter terms when your service supports a critical or important function (CIF). Only providers designated as critical by the European Supervisory Authorities (ESAs) fall under direct EU oversight (Articles 31 to 44). If your firm is one of the 19 providers the ESAs designated as critical, see our list of the 19 critical ICT providers; every other ICT provider is reached through the contract clauses below.

In DORA’s terms, an ICT third-party service provider is an undertaking providing ICT services (Article 3(19)), and ICT services are digital and data services provided through ICT systems to one or more internal or external users on an ongoing basis (Article 3(21)). If you host, build, run or support systems for a bank, you are very likely one. This article looks at DORA from the supplier’s side of the table. For the same rules seen from the bank’s side, read our page on DORA for banks and our ICT third-party risk guide.

What is an ICT third-party service provider under DORA?

Article 3(19) of DORA defines an ICT third-party service provider as “an undertaking providing ICT services”. Article 3(21) defines ICT services broadly: “digital and data services provided through ICT systems to one or more internal or external users on an ongoing basis”, including hardware as a service, and excluding traditional analogue telephone services. In practice, most software, cloud and managed IT services sold to banks fall within this definition.

Do not confuse two labels. Whether your service supports a critical or important function is decided by the bank, and if it does, your contract must include the stricter Article 30(3) terms. A critical ICT third-party service provider (CTPP) is designated by the ESAs under Article 31 and placed under direct EU oversight.

Does DORA apply directly to ICT providers?

In most cases, no. DORA’s obligations are addressed to financial entities: credit institutions, insurers, investment firms, payment institutions and the other categories listed in Article 2. Chapter V (Articles 28 to 30) tells those entities how to manage ICT third-party risk, and much of that management takes the form of requirements they must write into their contracts with you.

Three points are often misread:

  • Intra-group providers are covered. An IT company inside the bank’s own group is an ICT intra-group service provider (Article 3(20)). Delegated Regulation (EU) 2024/1773 treats it like any other ICT third-party service provider: the risks may differ, the requirements are the same (recital 5).
  • There is no exemption for small providers. The proportionality principle of Article 4 governs how the financial entity implements DORA. It does not lighten the clauses a small supplier is asked to sign.
  • The exception is designation. A limited group of large providers designated as critical by the ESAs (EBA, EIOPA and ESMA) is overseen directly at EU level. This is covered further down.

For a typical software house, managed service provider or hosting company, no authority will ask you directly to comply with DORA. Your banking clients will, because their contract with you is part of their own compliance.

Why banking clients ask for new clauses

Under Article 28(1)(a), a financial entity that uses ICT services remains fully responsible, at all times, for compliance with its obligations under DORA and financial services law. Four requirements in Article 28 explain most of the requests you receive:

  • Register of Information (Article 28(3)). The bank keeps a register of all its contractual arrangements on the use of ICT services, at entity level and at group level, in the templates of Implementing Regulation (EU) 2024/2956. This is why you are asked for legal identifiers such as your LEI, service descriptions, data locations and the names of your subcontractors. The ESAs used the Registers of Information collected by competent authorities as the main input for the first CTPP designations (see our list of designated CTPPs). More on the register itself: DORA Register of Information.
  • Assessment before contracting (Article 28(4)). Before signing, the bank must assess whether the arrangement covers a critical or important function, identify and assess the relevant risks, carry out due diligence on you and assess conflicts of interest. This is the source of the security questionnaires.
  • Contractual policy (Article 28(2) and (10)). The bank adopts a strategy and a policy on ICT services supporting critical or important functions. Its content is specified by Delegated Regulation (EU) 2024/1773, which is why procurement teams now arrive with standard DORA schedules.
  • Exit strategies (Article 28(8)). For ICT services supporting critical or important functions, the bank needs an exit strategy. This is why it asks about reversibility, data return and transition support.

Clauses every ICT contract must contain

Article 30(1) requires the rights and obligations of the financial entity and of the provider to be clearly allocated and set out in writing. Article 30(2) lists nine elements, points (a) to (i), that apply to every contract on the use of ICT services, whatever the service. Article 30(3) adds six, points (a) to (f), when the service supports a critical or important function.

Contractual requirement (Article 30 DORA)All ICT contracts (Art. 30(2))Critical or important functions (Art. 30(3))
Clear and complete description of all functions and ICT services, stating whether subcontracting of a CIF service is permitted and on what conditionsYes (a)Yes, with the subcontracting conditions of Delegated Regulation (EU) 2025/532
Regions or countries where services are provided and data is processed and stored, with advance notice of any envisaged changeYes (b)Yes
Availability, authenticity, integrity and confidentiality of data, including personal dataYes (c)Yes
Access, recovery and return of data, including on insolvency, resolution, discontinuation of business or terminationYes (d)Yes
Service levelsService level descriptions, including updates and revisions (e)Full service level descriptions with precise quantitative and qualitative performance targets (a)
Assistance when an ICT incident related to the service occurs, at no additional cost or at a cost determined ex anteYes (f)Yes, plus notice periods and reporting obligations to the bank (b)
Full cooperation with competent authorities and resolution authoritiesYes (g)Yes
Termination rights and related minimum notice periodsYes (h)Yes
Participation in the bank’s ICT security awareness programmes and digital operational resilience trainingYes (i)Yes
Implementation and testing of business contingency plans; ICT security measures, tools and policiesNoYes (c)
Participation and full cooperation in the bank’s threat-led penetration testing (Articles 26 and 27)NoYes (d)
Unrestricted rights of access, inspection and audit for the bank, a third party it appoints and the competent authorityNoYes (e)
Exit strategies, including a mandatory adequate transition periodNoYes (f)

The letters in brackets refer to the points of each paragraph. Two details are worth noting. The duty to notify a change of location in advance applies to every contract, not only to critical or important functions. And DORA itself sets no minimum number of days for that notice, nor a right to refuse the change: those are negotiated. The clause-by-clause reference, with what each point requires in practice, is in our guide to Article 30 and the third-party RTS.

If you support a critical or important function

A critical or important function is a function whose disruption would materially impair the financial performance of a financial entity, or the soundness or continuity of its services and activities, or whose failed performance would materially impair its continuing compliance with the conditions of its authorisation or its other obligations under financial services law (Article 3(22)).

The bank classifies its functions, not you. The same product can support a critical or important function at one bank and an ordinary function at another. Ask each client how it has classified the function your service supports, because the answer decides whether the Article 30(3) clauses apply. Our guide to critical or important functions explains how banks run that assessment.

When Article 30(3) applies, expect three practical changes:

  • Audit. The rights of access, inspection and audit must be unrestricted (Article 30(3)(e)). Standard terms that only offer a pooled report or a questionnaire may need renegotiating. Where the bank is a microenterprise, the parties may agree that these rights are delegated to an independent third party appointed by the provider (Article 30(3), last subparagraph).
  • Resilience evidence. You implement and test business contingency plans (Article 30(3)(c)), and you may be asked to take part in the bank’s threat-led penetration testing (TLPT) where your systems fall within its scope (Article 30(3)(d)). TLPT itself applies only to the financial entities identified by their competent authority (Article 26(8)); see our TLPT requirements guide.
  • Exit. The contract provides a transition period during which you keep delivering the service while the bank migrates to another provider or brings it in-house (Article 30(3)(f)).

Can you still use subcontractors?

Yes, with more transparency. Under Article 30(2)(a), every contract must state whether subcontracting of an ICT service supporting a critical or important function, or of material parts of it, is permitted and on what conditions. Article 30(5) mandated technical standards on this point. They were adopted as Commission Delegated Regulation (EU) 2025/532 on 24 March 2025 and published on 2 July 2025.

In practice, for services supporting critical or important functions, banks will ask you to:

  • remain responsible for the services your subcontractors provide, and monitor them (Article 4(1)(a) and (b) of Delegated Regulation 2025/532);
  • identify the subcontractors concerned, so they can appear in the bank’s Register of Information;
  • give the bank and its competent and resolution authorities the same rights of access, inspection and audit at subcontractor level (Article 4(1)(j));
  • inform the bank of any intended material change to your subcontracting arrangements well in advance, within a notice period during which it can approve or object (Article 5);
  • accept that the bank may terminate the contract if you implement a change it objected to, implement it before the notice period ends without its approval, or subcontract a service the contract does not permit to be subcontracted (Article 6).

When a provider becomes a CTPP

The ESAs designate critical ICT third-party service providers (CTPPs) under Article 31. The criteria of Article 31(2), specified by Delegated Regulation (EU) 2024/1502, cover the systemic impact of a failure of the provider, the systemic character of the financial entities relying on it, its role in supporting critical or important functions, and its substitutability. The first list, published on 18 November 2025, contains 19 designated providers (ESAs, list of designated CTPPs). Our list of designated CTPPs gives the names.

Designation brings direct EU oversight:

  • a Lead Overseer, one of the three ESAs, with powers to request information, run general investigations and inspections, and issue recommendations (Articles 33 to 39), supported by a joint examination team (Article 40);
  • periodic penalty payments of up to 1% of the average daily worldwide turnover in the preceding business year where the provider fails to comply with information requests, investigations, inspections or reporting requests (Article 35(6) and (8)), imposed daily for no more than six months (Article 35(7));
  • oversight fees under Article 43, set by Delegated Regulation (EU) 2024/1505;
  • for a provider established outside the EU, banks may only use its services if it establishes a subsidiary in the Union within 12 months of designation (Article 31(12)).

A provider that is not designated may also request designation itself (Article 31(11)). The first designations concern large cloud, data, telecoms and IT services groups. For most smaller suppliers, the contractual route described above is what counts.

If you provide cloud services, see how banks apply these rules on their side in our guide to DORA cloud and outsourcing requirements.

DORA, NIS2 or both?

The two regimes can apply at the same time. NIS2 (Directive (EU) 2022/2555) may apply to your company in its own right, for example as a managed service provider. DORA reaches you through your financial-sector clients. For financial entities, DORA is the sector-specific Union legal act within the meaning of Article 4 NIS2. The detailed comparison is on our page on DORA vs NIS2.

Checklist: how to prepare

  1. Map your financial-sector clients and the services you provide to each (Article 2 for the list of financial entities).
  2. Ask each client how it classifies the function your service supports (Article 3(22) and Article 30(3)).
  3. Prepare a standard DORA addendum covering points (a) to (i) of Article 30(2), with a schedule for Article 30(3) contracts.
  4. Document your incident assistance process, including how you charge for it (Article 30(2)(f)). Your client has its own reporting deadlines; our DORA incident reporting reference shows them from its side.
  5. Formalise and test your business contingency plans, and keep the test evidence (Article 30(3)(c)).
  6. List your subcontractors and data locations, and set up a process to notify changes in advance (Article 30(2)(a) and (b), Delegated Regulation (EU) 2025/532).
  7. Write a reversibility and exit plan with a defined transition period and a data return format (Article 30(2)(d) and 30(3)(f)).
  8. Decide how you will host audits by clients and authorities without exposing other clients’ data (Article 30(3)(e)).

Your clients will score you on the same ground. Our third-party risk scorer shows the questions from the financial entity’s side, and our guide to ICT third-party risk under DORA shows how they frame the whole programme.

Frequently asked questions

Is my company directly regulated by DORA if I provide software or cloud services to a bank?

Generally not. DORA’s obligations reach you through your client’s contracts (Articles 28 and 30). Direct oversight applies only to providers designated as critical by the ESAs under Article 31.

Who decides whether my service supports a critical or important function?

The bank does, applying the definition in Article 3(22) DORA. Ask for its classification, because it determines whether the additional clauses of Article 30(3) apply.

Do existing contracts need to be amended?

DORA has applied since 17 January 2025, and Article 30 sets out what the contract must contain. Contracts in force that lack those elements are usually brought into line through amendments or addenda.

Can a bank audit my company under DORA?

For services supporting critical or important functions, yes. The contract must give the bank, a third party it appoints and the competent authority unrestricted rights of access, inspection and audit (Article 30(3)(e)).

Can I refuse to notify changes of data location?

Not under a contract that meets Article 30. Article 30(2)(b) requires every ICT contract to state the regions or countries where data is processed and stored, and to oblige you to notify the bank in advance if you envisage changing them.

Does DORA apply to ICT providers based outside the EU?

Yes, through your contracts. If you provide ICT services to EU financial entities, they must include the Article 30 clauses in your contract wherever you are established. DORA applies to you directly only if the ESAs designate you as a CTPP: a CTPP established outside the EU must then set up a subsidiary in the Union within 12 months of designation, or EU financial entities may no longer use its services (Article 31(12)).