Last month, the Panorays Threat Center tracked several confirmed breaches at software and platform providers, among them a contact-center software vendor and a developer-tool marketplace. For a bank or insurer, each headline like that raises the same DORA compliance questions: whether the service is on your register, whether it supports a critical or important function, what the contract says about incident assistance, and whether a tested exit plan exists. Here is what the Digital Operational Resilience Act requires for ICT third parties, and the evidence to keep ready.
Who does DORA apply to?
DORA applies to the 20 categories of financial entities listed in Article 2(1), points (a) to (t). They include credit institutions, payment and e-money institutions, investment firms, crypto-asset service providers, insurers and reinsurers, and fund managers. ICT third-party service providers sit in point (u), mainly through the oversight regime for critical providers, and Article 2(3) excludes a short list of entities, most of them small.
Under Article 28(1)(b), third-party risk management follows the principle of proportionality, scaling with the complexity of each ICT dependency and the criticality of the function it supports.
What does DORA require for ICT third parties?
DORA treats ICT third-party risk as part of the entity’s ICT risk management framework, and the entity stays fully responsible for compliance, whatever it outsources. It must keep a strategy on ICT third-party risk, assess every arrangement before signing, contract only with providers that meet appropriate information security standards, and keep the right to audit and to terminate.
Article 28(4) defines the pre-contract work: classify the function, check supervisory conditions, identify all relevant risks including concentration, complete due diligence, and assess conflicts of interest. But the exit door has to be built in too. Article 28(7) makes the contract terminable for a significant breach, monitoring findings that could alter performance, evidenced weaknesses in the provider’s ICT risk management, or a supervisor no longer able to supervise effectively.
What goes in the DORA register of information?
The DORA register of information records every contractual arrangement for ICT services from third-party providers. Article 28(3) requires it at the entity level and at the sub-consolidated and consolidated level, distinguishing arrangements that support critical or important functions from those that do not. Commission Implementing Regulation (EU) 2024/2956 sets the standard templates the register must follow.
At least yearly, the entity reports new arrangements, provider categories, contract types and the services and functions provided. And supervisors can ask for the full register at any time, while planned arrangements for critical or important functions must be notified in a timely manner. Our guide to the register of information covers the templates field by field.
What must an ICT contract contain under Article 30?
Article 30 requires both parties’ rights and obligations in writing, with the full contract and its service levels in one document. Every ICT contract must cover nine minimum elements. Contracts for services supporting critical or important functions add six more, covering performance targets, notice duties, contingency testing, participation in threat-led penetration testing, unrestricted audit rights and an exit transition period.
The minimum set runs from the service description, subcontracting conditions and data locations to data return on termination, incident assistance at no extra cost or a cost fixed in advance, cooperation with supervisors, and termination rights with notice periods. Delegated Regulation (EU) 2024/1773 specifies what the Article 28(2) policy on ICT services supporting critical or important functions must contain.
What is a DORA exit strategy?
A DORA exit strategy is the documented plan, required by Article 28(8) for ICT services supporting critical or important functions, to leave a provider without disrupting the business, limiting regulatory compliance, or harming service to clients. It must anticipate provider failure, degraded service, disruption, and contract termination, and exit plans must be comprehensive, documented, sufficiently tested, and reviewed periodically.
So the plan names alternative solutions in advance and a transition route to move services and data to another provider or back in-house, securely and in full. Article 30(3)(f) covers the contract side with a mandatory transition period during which the provider keeps delivering while you migrate.
How does DORA treat concentration risk and subcontracting?
For critical functions, Article 29 adds a concentration check to the pre-contract risk assessment. Two triggers count: a provider that is not easily substitutable, and several such arrangements with the same or closely connected providers. Where either applies, the entity weighs the costs and benefits of alternatives, such as using different providers.
Subcontracted critical services get the same scrutiny, especially in a third country, including the applicable insolvency law, limits on urgent data recovery, and whether long chains would stop the entity from monitoring the function. Under Article 29, fourth-party risk in financial services becomes a regulatory question.
What evidence will auditors ask for?
Auditors and supervisors will ask you to show each obligation working, so DORA compliance rests on artefacts you can produce on request. The table maps each third-party article to the evidence that answers it. Owners vary by organization, and cadence follows the regulation where it sets one and your documented policy elsewhere.
| Obligation | Article | Evidence to have ready | Typical owner | Cadence |
|---|---|---|---|---|
| ICT third-party risk strategy | 28(2) | Approved strategy and policy for critical or important functions, management body review records | CISO or CRO | Regular review |
| Register of information | 28(3) | Register at all levels in the 2024/2956 templates, critical or important flag per arrangement | TPRM or GRC lead | Kept current, reported at least yearly |
| Pre-contract assessment | 28(4), 29 | Due diligence file, risk and conflict assessment, concentration and substitutability analysis | TPRM lead, procurement | Before each signature |
| Security standards | 28(5) | Evidence the provider meets appropriate standards | Security team | At selection, then monitored |
| Audit rights | 28(6), 30(3)(e) | Risk-based audit plan with frequency and scope | Internal audit | Set in advance |
| Contract clauses | 28(7), 30 | Clause map per contract, including all four termination grounds | Legal | At signing and renewal |
| Exit strategy | 28(8), 30(3)(f) | Exit plan, alternatives, transition plan, test results | Service owner | Tested and reviewed periodically |
Our DORA compliance checklist turns these rows into tasks, and the post on threat-led penetration testing covers the testing clause.
What changes for critical ICT third-party providers?
Under Article 31, the European Supervisory Authorities designate the ICT providers that are critical for financial entities, based on criteria such as systemic impact, reliance and substitutability, and appoint a Lead Overseer for each. The ESAs published the first designations on 18 November 2025 and built them from data in financial entities’ registers.
Designation brings the provider under direct oversight, yet Article 28(1)(a) still holds each financial entity fully responsible, so your due diligence, contract and exit evidence for that provider stays on your file.
Where third-party cyber risk management supports DORA compliance
DORA’s unit of analysis is the relationship, meaning one contractual arrangement and the function it supports. A provider can be critical for payments and minor for a marketing tool, and the register, the clauses, and the exit plan all follow from that distinction. Third-party cyber risk management works at the same level. By tying each provider’s security posture to the business context of the relationship, contextual risk scoring and continuous monitoring point attention at the arrangements behind critical or important functions.
Ownership stays where DORA puts it. A financial entity owns the strategy, the register, the assessment and the decision to exit, and a TPCRM program keeps the evidence for each one current.
See how a third-party cyber risk management program can support your DORA obligations.
DORA Compliance FAQs
When did DORA start to apply?
DORA has been fully applicable since January 2025. Adopted as Regulation (EU) 2022/2554 in December 2022, it is directly applicable in every member state, so no national transposition is needed for it to bind financial entities. Supporting technical standards, including the register templates in Implementing Regulation (EU) 2024/2956, were adopted during 2024 and apply alongside the regulation.
Does DORA apply to ICT providers outside the EU?
DORA places its third-party obligations on EU financial entities, and those entities apply them to every ICT provider they use, wherever it is based. A provider outside the EU meets DORA through its customers’ contracts and due diligence. Article 29 asks entities to weigh third-country providers and subcontractors with particular care, including data protection compliance and effective enforcement of the law there.
How often must the register of information be reported?
Article 28(3) requires financial entities to report to their competent authority at least yearly on new ICT arrangements, provider categories, contract types and the services and functions provided. The register itself must be maintained and kept up to date. Supervisors can request the full register or specific sections whenever they need it, so it should be ready to produce at short notice.
Does every ICT contract need an exit strategy?
Article 28(8) requires documented exit strategies for ICT services that support critical or important functions. Other arrangements still need the Article 30(2) minimum clauses, including termination rights and the return of data on termination, so every contract has a basic exit path. Scaling the depth of planning to the criticality of the function fits DORA’s proportionality principle.
Can a financial entity rely on a critical provider’s oversight?
No. The Lead Overseer’s oversight of a critical ICT third-party provider covers the provider’s own risk management and governance. Article 28(1)(a) keeps each financial entity fully responsible for its own compliance, so the entity still needs its register entry, due diligence, Article 30 contract clauses, concentration assessment, and tested exit plan for that provider.