Request a quote
Emergency SectorsCareers About us Blog Get in touch
Analyst wearing a headset in front of a wall of monitoring screens in a darkened room

The DORA regulation for ICT suppliers: what the Digital Operational Resilience Act asks of you through your client

The DORA regulation has applied since 17 January 2025 to banks, insurers, payment institutions and other financial entities in the EU. Yet it often reaches their suppliers first: as a contract addendum, a questionnaire or a request for an exit plan. This piece is for that side of the table: what the Digital Operational Resilience Act asks of you through your client, what you can prepare now and where your responsibility ends.

6 min read Written by the ITproposal team
Short answer

DORA places the obligation on the financial entity, not the supplier. What reaches you comes through the contract, and the regulation prescribes what that contract must contain.

If your service supports a critical or important function, the bar rises: audit rights, a tested continuity plan, participation in testing and an exit strategy with a transition period.

Have four things ready before the first question: a service description with locations, a list of your subcontractors, your incident procedure and an exit plan you can actually deliver.

Who the DORA regulation applies to, and why it lands with you

The Digital Operational Resilience Act (Regulation (EU) 2022/2554) has applied directly in every EU member state since 17 January 2025. It covers financial entities: banks, insurers, investment firms, payment and e-money institutions, crypto-asset service providers, occupational pension funds and a range of others. In Ireland the Central Bank of Ireland supervises it; in the Netherlands, DNB and the AFM.

An ordinary IT supplier is not on that list. The regulation states explicitly that the financial entity remains responsible for what it outsources. Only a small group of large providers, designated as critical ICT third-party service providers by the European supervisory authorities, are overseen directly. For everyone else, DORA arrives through the client: in the contract, in the register the client must keep and in the questions its supervisor asks.

In the UK, DORA does not apply domestically. UK firms work under the PRA and FCA operational resilience rules and the UK’s own regime for critical third parties. A UK supplier with clients in the EU financial sector gets DORA through those contracts all the same.

What the DORA regulation puts in your contract

Article 30 lists what a contract with an ICT provider must contain as a minimum. There is little to negotiate on the topics and plenty on the detail. For each service it covers:

  • A complete description of the functions and services, and whether and on what terms you may subcontract.
  • Locations: the countries where the service is provided and where data is processed and stored, with an obligation to notify changes in advance.
  • Data protection: availability, integrity and confidentiality, and how the client gets its data back on insolvency, discontinuation or termination.
  • Service levels, and how they are updated.
  • Assistance with ICT incidents related to your service, on terms agreed in advance.
  • Cooperation with the client’s supervisor.
  • Termination rights and minimum notice periods, and your participation in the client’s security awareness programmes if it asks.

Most clients record this in a DORA addendum alongside the existing contract. Read it as a list of commitments, not boilerplate: every line is something you will have to deliver later, including at three in the morning.

Critical or important function: the distinction that raises the bar

The client decides whether your service supports a critical or important function. That is its judgement, not yours, but it changes what you must deliver. For those services, add:

  • Measurable service levels with precise quantitative and qualitative targets, so the client can act if you miss them.
  • A continuity plan that you test, and security measures that match the level the client must meet.
  • Participation in testing, including the threat-led penetration testing (TLPT) that larger financial entities must have carried out.
  • Unrestricted rights of access, inspection and audit for the client, for a party it appoints and for the supervisor.
  • An exit strategy with a mandatory, adequate transition period.

So ask at the start: does our service support a critical or important function for you? The answer decides whether you are signing a light addendum or entering a programme. That belongs in your planning and your pricing structure, not in a surprise halfway through.

Incident reporting: your clock runs ahead of the client’s

The financial entity must classify major ICT incidents and report them to its supervisor, with an initial notification within hours, followed by an intermediate and a final report. The client does the reporting, not you. But it can only classify an incident once it knows what is happening, and it often hears that from you first.

  • A notification deadline to the client that is shorter than its own. Agree how quickly you pass on a suspected incident, including out of hours, and to whom. A notification that arrives the next working day is too late for the client.
  • The information it needs to classify: which services and users are affected, for how long, which data, and whether it is recurring. Turn that into a standard form.
  • A named contact on both sides, with a deputy. On the day there is no time to work out who receives the notification.
  • Logs you retain and can hand over, because the final report asks for a root cause and that sits in your systems.

What you do yourself in the first hour is set out in our piece on the first hour after an incident.

An exit plan you can actually deliver

DORA requires the client to have an exit strategy for critical and important functions that it can carry out without disrupting its business. The client writes that strategy, but it can only do so with your input. Be honest about it: an exit plan that looks good and that you cannot deliver is the first thing a review exposes.

  • What you hand over: data in a usable format, configurations, documentation, admin accounts and logs.
  • How long you keep delivering after notice is given, during the transition period, and on what terms.
  • What you do if the contract ends in a dispute, because that is exactly when cooperation is needed.
  • When the handover was last tested. Data that has demonstrably been restored at another party or in the client’s own environment says more than a plan on paper.

How such a move works when it actually happens is described in changing IT supplier without damage.

Subcontractors and locations: the chain behind your service

The client must keep a register of information on all its contracts with ICT providers, and that register goes beyond your name. It also asks about the chain: which subcontractors help support a critical or important function, and from which country. A data centre, a cloud platform, a software vendor you rely on yourself: they all belong in it.

So build that overview before the client asks: per service, which third parties are involved, what they do, where they deliver from and whether they touch the client’s data. Agree too how you notify a change in that chain in advance. A new subcontractor brought in quietly can be a breach of contract for the client.

This is where DORA meets the GDPR. A subcontractor with access to personal data is already in your data processing agreement. Keep the two lists aligned, or you will give two different answers to the same question.

What to prepare as a supplier now

The questions usually arrive in the same order: a questionnaire first, then a contract addendum, then a request for the exit plan and test results. A supplier that already has the answers negotiates on substance instead of searching.

  • A service description per service, with the locations of delivery and storage.
  • Your subcontractor overview, as above.
  • Your incident procedure, with notification deadline, contacts and the notification form.
  • Your continuity plan and the latest test result, dated.
  • An exit plan per service that you can deliver.
  • Your certificates, with the caveat that belongs with them. An ISO/IEC 27001 certificate shows you manage information security, but it is not a DORA statement. It answers some of the questions, not all of them.

Does your own organisation fall under NIS2? For financial entities DORA takes precedence as the more specific regime, but NIS2 may apply to you directly as a supplier. Many measures overlap, so one set of documents that covers both saves duplicate work.

Where our work stops

What we do. We are an IT supplier ourselves, so we sit on the same side of the table. We deliver the technical side that ends up in a DORA contract: service descriptions with locations, an incident procedure with notification deadlines, continuity plans we test, an exit plan we can deliver ourselves, and documentation and admin accounts in the client’s name. Our own processes are certified under ISO 9001, ISO/IEC 27001 and ISO 14001.

What we do not do. We are not lawyers and not a supervisor. We do not assess whether a contract complies with the DORA regulation, we do not decide whether a service supports a critical or important function, we do not classify incidents for the client and we report nothing to a supervisory authority. Nor do we declare anyone DORA compliant. Under the regulation, the financial entity remains responsible for what it outsources. Have the legal side reviewed by a lawyer who knows financial regulation.

Frequently asked

Questions we get about this

The five that come up most often.

Does the DORA regulation apply to IT suppliers?

Not directly, except for a small group of large providers that the European supervisory authorities designate as critical. The regulation places the obligation on the financial entity, which must pass the requirements on in its contracts with ICT providers. As a supplier, you feel DORA through your client: in a contract addendum, a questionnaire and requests for plans and test results.

What must a DORA-compliant contract with an ICT provider contain?

Among other things a complete service description, the locations of delivery and data processing, data protection and data return arrangements, service levels, assistance with ICT incidents, cooperation with the supervisor and termination rights. If the service supports a critical or important function, measurable service levels, a tested continuity plan, audit rights, participation in testing and an exit strategy are added.

Does an IT supplier have to report incidents under DORA?

Reporting to the supervisor is done by the financial entity itself. The supplier must inform the client quickly and fully enough for it to report on time, and help with the investigation. Agree a notification deadline to the client that is shorter than the client’s deadline to its supervisor.

When did DORA come into effect?

The regulation entered into force in January 2023 and has applied since 17 January 2025. From that date financial entities must meet its requirements, including for contracts with ICT providers that were already running.

Can you certify us as DORA compliant?

No. We are not lawyers or a supervisor, and under the regulation responsibility lies with the financial entity. What we do, as a supplier, is deliver and keep the technical commitments: service description, incident procedure, continuity plan, exit plan and documentation. The legal review belongs with a lawyer.

Related services

Further reading

Where this piece connects.

An IT partner that can answer DORA questions?

If we manage your IT, or you are considering it, we deliver the service description, incident procedure and exit plan your clients in the financial sector ask of you. The legal review we leave to your lawyer.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call