GUIDE EUROPE · DIGITAL SOVEREIGNTY

DORA compliance for third-party ICT providers in the European financial sector

DORA requires banks and other financial entities to manage the risk of their ICT suppliers through contracts, evidence and oversight of critical providers. Here is how to prepare the documents financial clients will ask for and how to pass their resilience reviews. The earlier the evidence is ready, the less time a commercial negotiation loses.

Updated october 2026
7 min read
Altovar Technical Editorial Team

1. Who a third-party ICT provider is under DORA

Regulation (EU) 2022/2554, DORA, concerns the digital operational resilience of the financial sector: banks, insurance companies, payment institutions and other supervised entities. A third-party ICT provider is an organisation that supplies IT services to these entities, such as cloud, management software, security, systems support or data transmission. If the service supports processes that are important to the financial client, the provider falls within the scope of control, even when it is not itself a financial entity.

For an IT provider this means that a banking or insurance client will ask for more than a standard contract. It will want evidence on continuity, security, incident management and exit from the service. A provider that is not prepared to answer risks losing the client, not because of a technical defect, but because of a lack of documentation. The banking client often asks the same questions of several providers, so those who already have the evidence ready start with an advantage.

2. What DORA requires on contracts and risk management

DORA requires the financial entity to manage third-party ICT risk as part of its risk management framework. In practice this means contracts with mandatory minimum clauses, a register of providers and services that support important functions, and a prior risk assessment before a service is entrusted. The client must be able to demonstrate who does what and with what guarantees.

Contract clauses concern in particular measurable service levels, audit and access rights, cooperation in the event of an incident, data location and processing, and exit conditions. A generic reference to security is not sufficient. The provider must accept precise and verifiable obligations, otherwise the client cannot document compliance. This is why the clauses are often the first point of discussion in negotiations.

3. How the financial client assesses the provider

The typical process is due diligence, meaning a check before signing and then periodically. The client sends a questionnaire, asks for documents such as security policies, continuity plans, recovery test results and certifications, and assesses the consistency of the answers. For more important services it may request a direct audit or participation in exercises. This applies especially to services that support important processes.

A certification such as ISO/IEC 27001 is a useful element, because it demonstrates a security management system. It does not, however, complete the assessment. The client will want to know whether the certificate covers the specific service, which sub-suppliers are involved and how the provider handles concentration risk, that is, the case where many clients depend on the same service or the same provider.

4. Requirements and evidence to prepare

To respond in an orderly way it is advisable to prepare a reusable evidence pack. The table indicates five typical areas, the content the provider should produce and the proof the client tends to request. It is not an exhaustive list: each client has its own questionnaire and internal requirements. Use the table as a map for organising the evidence, not as a checklist to tick off.

Preparing the pack before the request arrives is the most effective way to avoid slowing down negotiations. Update the evidence whenever services, sites or sub-suppliers change, and keep earlier versions. A document months old that describes an architecture that has already been superseded weighs more than an incomplete answer. Always note the date of each version and who approved it.

AreaWhat the provider should produceProof the client requests
ContractMinimum clauses on service levels, audit, incidents and exitDraft contract with the clauses highlighted
Risk managementUp-to-date risk analysis of the serviceSigned document and date of last review
ContinuityContinuity and recovery plan with tests carried outTest report with results and corrective actions
IncidentsCommunication procedure with timescales and contactsWritten procedure and exercise log
ExitPlan for transferring data and service to another providerDescription of formats and return timescales

5. Documents to prepare for the first response

When a financial client opens an assessment, speed of response matters as much as quality. A ready list of documents allows you to respond consistently and avoid contradictions between one document and another. The list below can serve as the basis for a shared folder with the client. A stable structure reduces errors from one questionnaire to the next.

Next to each document indicate the owner, the review date and the version. This makes clear that the material is governed, not improvised. If a document does not yet exist, say so and indicate when it will be ready, rather than presenting a generic version. An honest answer with a precise deadline is better than one that does not survive the first check. The client notices immediately.

  • Information security policy and the perimeter of the services offered.
  • Certificate with its scope of application, where available.
  • List of sub-suppliers and the countries in which they operate.
  • Business continuity plan and report from the last recovery test.
  • Incident management procedure with contacts and communication timescales.
  • Description of the exit plan and of the data export formats.
  • Audit form, with a named contact and audit calendar.

6. Common mistakes made by providers

The first mistake is answering questionnaires with generic statements. Phrases such as 'we guarantee maximum security' do not pass any check. The client looks for precise descriptions, evidence and named owners. The second is forgetting sub-suppliers: if a service depends on another entity's infrastructure, the client wants to know that and wants that entity to meet the same rules. This too must be written into the contract, not left to trust.

The third mistake is not having an exit plan. The financial client must be able to replace the provider without interrupting its critical services, and this must be demonstrated. The fourth is thinking that compliance is a document to be handed over once. In reality it is a process that requires periodic updates and an accountable person. Assign responsibility to a defined role, not to an individual who may change jobs.

7. How to start: the first concrete step

The first step is to understand whether your services touch important processes for a financial client. List the clients in the sector, the services you provide and the data or systems involved. This map shows where an evidence pack is needed and where a standard response is enough. Involve the sales manager to understand which clients ask for the most evidence, and how often.

Then prepare the first version of the pack using the list in the previous section. Ask a legal adviser to check the model clauses, and compare your evidence against the requirements of your most demanding clients. Every document you complete today reduces the time of the next assessment. Choose the most requested first document and complete it first, before moving on to the others.

Frequently Asked Questions

How do you obtain the status of critical ICT third-party provider?

It is not obtained through an application or a self-declaration. The DORA framework provides for the European supervisory authorities to designate providers considered critical, on the basis of criteria set out in the regulation. The provider's role is to prepare documentation and processes that can withstand an assessment. For the current state of designations, consult the official sources of the supervisory authorities.

Is an ISO/IEC 27001 certification sufficient for a banking client?

It is an important element but not sufficient. The client will want to check that the certificate covers the service provided, that sub-suppliers are included and that continuity and exit plans exist. The certification demonstrates a management system, not that every contractual requirement is met.

What happens if the client asks for an audit right?

The contract should set out clear arrangements: who may carry out the review, with what notice, at which sites and systems, and with what confidentiality limits towards other clients. An organised response, with documents ready and a named contact, reduces the discomfort for both parties.

How do I manage sub-suppliers in the relationship with a financial client?

Keep an up-to-date list, communicate changes in line with the contract terms and make sure sub-suppliers meet equivalent obligations. The client must be able to know who takes part in the service and where the data is located. An unregistered sub-supplier is one of the most frequent reasons for rejecting an assessment.

How long does it take to prepare the evidence pack?

It depends on how much is already documented. Those who have up-to-date policies, continuity plans and procedures can prepare the base in a short time. Those starting from scratch must write first and then test, which takes longer. It is best to proceed area by area, starting with the evidence clients request most often.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →