DORA compliance means meeting the requirements of the Digital Operational Resilience Act, Regulation (EU) 2022/2554, which has applied since 17 January 2025. It requires EU financial entities to manage ICT risk, report major ICT incidents, test resilience, and control ICT third-party risk, and it reaches the technology providers that serve them through contracts and oversight.
For banks, insurers, investment firms, and fund managers, DORA is a direct legal obligation. For the software, cloud, and data companies that sell to them, it shows up a different way: longer contract negotiations, new due diligence questions, and requests for evidence about where services run, who subcontracts them, and how they would be exited. This guide covers what the regulation requires, which parts reach ICT providers, and how to answer client requests consistently.

DORA compliance at a glance
The official text of the regulation organizes its requirements into five main areas. The table below summarizes each one and the kind of request an ICT provider can expect from financial clients as a result.
| DORA PILLAR | WHAT FINANCIAL ENTITIES MUST DO | WHAT ICT PROVIDERS ARE USUALLY ASKED FOR |
|---|---|---|
| ICT risk management | Maintain a documented framework to identify, protect against, and recover from ICT risk | Security policies, control descriptions, and certifications |
| ICT-related incident management, classification and reporting | Classify ICT incidents and report major ones to competent authorities | Incident notification commitments and assistance during incidents |
| Digital operational resilience testing | Run a testing program, with threat-led penetration testing for entities that authorities identify | Test evidence, and cooperation in threat-led testing for critical or important functions |
| Management of ICT third-party risk | Keep a register of information and include required contract terms | Service locations, subcontractors, service levels, audit rights, and exit terms |
| Information-sharing arrangements | Optionally exchange cyber threat information and intelligence | Rarely a direct vendor request |
Most vendor questions trace back to the fourth pillar, because it is the one that makes financial entities accountable for the providers they rely on.
Who DORA applies to
DORA applies to financial entities across the EU financial sector, from credit institutions and payment institutions to investment firms, insurers, and fund managers. ICT third-party service providers are covered in two ways. Most are affected indirectly, through the contract terms and oversight duties their financial clients must apply. A smaller group is affected directly: providers designated as critical come under oversight by the European Supervisory Authorities (ESAs).
That designation is no longer theoretical. On 18 November 2025, the ESAs published the first list of designated critical ICT third-party providers. The list names 19 providers, including Amazon Web Services, Google Cloud, Microsoft, Oracle, SAP, and Bloomberg. If you are not on it, DORA still reaches you whenever an EU financial entity uses your service.
DORA requirements that reach ICT providers
The register of information
Under Article 28(3), financial entities must maintain and update a register of information covering all contractual arrangements for ICT services. They must also report at least yearly to their competent authorities on new ICT arrangements, including the categories of providers, the types of contracts, and the services and functions provided. To fill in that register, clients need accurate, structured data from you: legal entity details, the services delivered, whether those services support a critical or important function, and the subcontractors involved.
Article 30 contract terms
Article 30 sets the minimum contents of every contract for ICT services. Expect clients to ask for, or negotiate, terms covering the following:
- A full description of the services, and whether subcontracting of critical or important functions is allowed and on what conditions.
- The locations where services are provided and data is processed and stored, with advance notice of any change.
- Provisions on the availability, authenticity, integrity, and confidentiality of data, and on access, recovery, and return of data if the contract ends or the provider fails.
- Service level descriptions, assistance during ICT incidents, cooperation with competent authorities, and termination rights with minimum notice periods.
- Participation in the client's ICT security awareness and digital operational resilience training where relevant.
For services that support critical or important functions, Article 30(3) adds stricter terms: precise quantitative and qualitative performance targets, notice of developments that could affect delivery, tested business contingency plans, cooperation in threat-led penetration testing, unrestricted access, inspection, and audit rights, and exit strategies with a mandatory transition period.
Incident support and resilience testing
Because financial entities must classify and report major ICT incidents, they need to know how quickly you will tell them about an incident affecting their service and what information you will provide. Testing works the same way. Clients will ask what testing you run, how often, and whether you will take part in their own tests when your service supports a critical or important function.

What DORA due diligence questions look like
DORA does not prescribe a single vendor questionnaire, so requests vary by client. Some financial entities send a dedicated DORA addendum, while others fold new questions into the security questionnaires they already use. Either way, the questions tend to follow the contract terms above: where is data stored and processed, which subcontractors support the service, what are the service levels, how are incidents notified, what audit rights are available, and what does exit support look like.
The overlap with existing security reviews is large, which is good news. If you already answer formats like SIG and CAIQ, covered in our guide to the vendor security questionnaire, much of your evidence is reusable. The gap is usually in operational and contractual detail, such as subcontractor chains, data locations, and exit plans, that security teams have not historically kept in one place.
How to build a DORA compliance answer set
Treat DORA responses as a maintained body of knowledge rather than a one-time project. A practical sequence looks like this:
- Map each service you sell to the functions it supports, so you can say which clients are likely to classify it as critical or important.
- Document service and data locations and your full subcontractor chain, with an owner responsible for keeping both current.
- Align published service levels, incident notification commitments, and support terms with what your contracts actually say.
- Prepare evidence for business continuity, security testing, and certifications, with dates that show when each item was last reviewed.
- Write approved language on audit rights, exit assistance, and transition periods, reviewed by legal before anyone reuses it.
- Store everything in one governed library and set review dates, so answers are refreshed when facts change.
The last step is where most teams struggle. The Consortium for Service Innovation's Knowledge-Centered Success (KCS) methodology offers a useful model: capture knowledge as it is used, reuse it, and improve it with every interaction. The Consortium for Service Innovation developed KCS for support organizations, and the same discipline applies to compliance answers that many people reuse across many clients.

In practice, that means an approved answer library with owners, review cycles, and expiration status, so a sales engineer never sends last year's subcontractor list. A content library built this way keeps DORA answers consistent with the answers in your security questionnaires, your DDQs, and your contracts.
Common DORA compliance mistakes for vendors
The most frequent problems are inconsistency and staleness. A questionnaire says data stays in one region while the contract allows another. A subcontractor was added but the answer library still lists the old chain. An exit plan is described in sales materials but never written into the contract. Each of these creates friction during procurement, and for clients they can become findings in their own supervisory reviews.
This guide is a general overview, not legal advice. Your legal and compliance teams should confirm how DORA and its technical standards apply to your services and contracts.
RocketDocs helps teams that serve banks, insurers, and asset managers keep regulatory answers governed and reusable. Explore our financial services solutions or see how the platform handles security questionnaires, including the DORA questions now arriving alongside them.
Looking for the platform behind this? See the RocketDocs platform or book a demo.