Skip to content
pitch
NL Nederlands
Menu

DORA and ICT Third-Party Risk

For financial entities and the ICT providers that serve them. We keep the DORA register of information complete and bring ICT contracts in line with Article 30.

By
By , Attorney-at-Law
Published
Updated

The question

Your supervisor asks for your register of information, and the contracts behind it do not say what they should. Or you sell software or hosting to a bank, an insurer or an investment firm, and their procurement team sends you a DORA addendum with a deadline.

DORA, Regulation (EU) 2022/2554 on digital operational resilience for the financial sector, has applied since 17 January 2025. For financial entities it is the sector-specific act that takes the place of NIS2 on ICT risk management, incident reporting and ICT third-party risk (recital 28 of the NIS2 Directive). A financial entity that uses ICT services stays fully responsible for its own compliance (Article 28(1)(a)).

Two duties cause most of the work. Article 28(3) requires a register of information on all contractual arrangements for ICT services provided by ICT third-party service providers, kept at entity level and at sub-consolidated and consolidated levels. It must distinguish arrangements for services that support critical or important functions from the rest. The full register, or parts of it, must be made available to the competent authority on request, and the entity reports at least yearly on new arrangements. The templates are fixed by Commission Implementing Regulation (EU) 2024/2956.

Article 30 then lists what every ICT contract must contain: a full description of the services and whether subcontracting is allowed, the locations where services are provided and data is processed, data protection and the return of data on exit or insolvency, service levels, assistance with ICT incidents, cooperation with the authorities, termination rights and participation in security awareness training. For services that support critical or important functions, Article 30(3) adds precise performance targets, business contingency plans, participation in threat-led penetration testing, unrestricted rights of access, inspection and audit, and an exit strategy with a mandatory transition period.

Our approach

For financial entities, we start with the inventory. Which ICT services do you use, from whom, under which contract, and which of them support a critical or important function? That classification is a legal and business judgement, and we record the reasoning with it.

The register itself sits in our compliance registers, which hold DORA registers on the same engine as the GDPR record of processing. Entries cite the article they answer to, contracts and assessments are attached as evidence, and each version is dated and approved by a lawyer. The export matches what your supervisor will ask for.

Then the contracts. Our contract review reads each ICT agreement against our playbook and the Article 30 requirements: the list in Article 30(2) for all contracts, and Article 30(3) for critical or important functions. You get a risk ranking and redlines, so you negotiate first on what is missing. Where a provider will not move, we record the gap and the mitigation. Article 30(4) asks parties to consider standard clauses developed by public authorities for specific services, and we tell you where they fit.

For ICT providers, the work is the mirror image. Our Document Studio drafts a DORA addendum from our clause library, in Word and in the house style, that you can offer your financial clients. That gives you a position of your own before the first client sends theirs. Exit and transition clauses are the hardest part, and they often overlap with your switching duties under the Data Act (see switching cloud providers) and with SaaS terms you already use.

After signature, notice periods, audit windows, reporting dates and exit steps go into our rights and obligations register, each confirmed by a person against its source clause, with reminders.

Our technology is our own, including the AI that prepares reviews, drafts and register entries. A lawyer checks every result before it reaches you.

What you get

  • An inventory of your ICT arrangements, with the critical or important functions identified and the reasoning recorded.
  • A register of information built on the templates of Implementing Regulation (EU) 2024/2956.
  • A review of each ICT contract against Article 30, with a risk ranking and redlines.
  • For ICT providers: a DORA addendum and a negotiation position for financial clients.
  • Exit and transition terms that work in practice.
  • Confirmed contractual obligations with reminders.

There are limits. We do not test your systems, run penetration tests or assess an ICT provider's technical security. The classification of functions and the final register remain your entity's responsibility under DORA, and we document the legal side of those decisions.

Next step

Send us your current list of ICT providers, or the DORA addendum a client sent you, and tell us which licence you hold or which financial clients you serve. We will tell you where the gaps are.

Schedule a meeting or contact us.

In short

  • Register of information kept in the format the templates require
  • ICT contracts checked against Article 30, clause by clause
  • Extra terms for services supporting critical or important functions
  • Exit and transition arrangements that work in practice
  • For ICT providers, a DORA addendum you can offer your financial clients
  • Reviewed by a lawyer

Our proprietary Legal Tech

Background reading

Let’s talk

Tell us what you’re working on. We’ll get the right person on it and reply within one business day. The first chat is free.

Schedule a meeting