What is the DORA ICT third-party register?
Direct answer
The DORA register of information is the record, required by Article 28 of Regulation (EU) 2022/2554, of all your contractual arrangements for the use of ICT services provided by third parties. Every financial entity must keep it current, maintain it at entity and, where relevant, sub-consolidated and consolidated group level, and make it available to its competent authority on request.
It is the backbone of DORA's third-party risk regime: supervisors use it to see, across the financial sector, which providers the system depends on. The register is not a one-time inventory. It is a living record that has to reflect your ICT supply chain as it actually is, including which arrangements support critical or important functions, because those carry stricter contractual and oversight requirements. That distinction, critical-or-important versus the rest, drives much of what DORA asks of the relationship. The register documents each ICT contractual arrangement: the provider, the service, whether it supports a critical or important function, and the contractual terms DORA requires. The European Supervisory Authorities set the detailed template and fields through technical standards, so the precise columns are defined centrally rather than left to each entity. The register has to be complete and consistent enough that a supervisor can read your ICT dependency map from it. A register maintained as a spreadsheet, separate from the vendor relationships it describes, is accurate the day it is built and wrong the week a contract changes and nobody updates the file. That is the failure mode DORA's "keep it current" requirement is aimed at, and it is why the register cannot be a document you refresh before an inspection.
What must the DORA register of information contain?
The fields are fixed by Commission Implementing Regulation (EU) 2024/2956, which sets the standard templates required by Article 28(9) of DORA. Financial entities use the templates in its Annexes I to IV to maintain the register at entity level, or at sub-consolidated and consolidated level. Article 5 of that regulation lists what goes in, template by template:
- the entity maintaining the register and, for groups, the entities in the consolidation and their branches outside the home country (templates B_01);
- general and specific information on each contractual arrangement, and the links between intra-group arrangements and those with external providers (templates B_02);
- the entities that sign the arrangements, on both sides (templates B_03), and the entities that use the ICT services (template B_04);
- the direct ICT third-party service providers and their subcontractors, and the ICT service supply chain (templates B_05);
- the identification of functions (template B_06) and the assessment of ICT services that support critical or important functions (template B_07);
- the terminology and closed lists used to fill in the templates (template B_99).
The register covers all ICT services provided by direct providers, plus the subcontractors that effectively underpin ICT services supporting critical or important functions or material parts of them (Article 3(2)). Each provider gets a rank in the supply chain: the direct provider is always rank 1 and subcontractors rank higher (Article 2). Providers that are legal persons are identified by a valid and active legal entity identifier (LEI) or a European Unique Identifier (EUID), and both where available (Article 3(5)).
The information must meet six data quality principles: accuracy, completeness, consistency, integrity, uniformity and validity. Financial entities review it regularly and correct errors or discrepancies promptly (Article 3(3) and (4)).
What do you report to the competent authority, and when?
Article 28(3) of DORA sets three duties on top of keeping the register:
- At least yearly, report to the competent authorities the number of new arrangements on the use of ICT services, the categories of ICT third-party service providers, the type of contractual arrangements and the ICT services and functions being provided.
- On request, make available the full register or the sections the authority asks for, with any information needed for effective supervision.
- In a timely manner, inform the authority about any planned contractual arrangement on ICT services supporting critical or important functions, and when a function has become critical or important.
For groups, the parent undertaking decides which entities to include by applying the relevant sectoral Union legislation, and a sub-consolidated or consolidated register includes all financial entities and ICT intra-group service providers in the group (Article 6 of Implementing Regulation (EU) 2024/2956). The entity responsible for the group register also checks that entity-level data is consistent with it (Article 3(3)).
How does the register connect to contracts and exit plans?
The register records what the contracts say, so it is only as good as the contracting process behind it. Before entering into an arrangement, Article 28(4) requires the financial entity to assess whether it supports a critical or important function, check that supervisory conditions for contracting are met, assess the risks including ICT concentration risk, carry out due diligence on the provider and identify conflicts of interest.
Article 30(2) then sets the minimum content of every ICT contract, including a full description of the services and whether subcontracting is allowed, the regions or countries where services are provided and data is processed and stored, data protection provisions, and termination rights with minimum notice periods. Where the service supports a critical or important function, Article 30(3) adds full service level descriptions with quantitative and qualitative performance targets, participation in threat-led penetration testing, unrestricted rights of access, inspection and audit, and exit strategies with a mandatory transition period.
In practice, the register is where those requirements become visible. If a contract is renewed, a subcontractor changes or a function is reclassified as critical or important, the register entry has to change with it. Testing and incident duties depend on the same classification: see threat-led penetration testing under DORA and the DORA scope test.
How Acuna GRC handles it
- Solution
DORA
Keep one ICT third-party register, map critical processes with RTO and RPO, find single points of failure and follow ICT incidents in one place.
- Module
TPRM (Supplier Shield)
Suppliers, questionnaires, assessments and campaigns, with a supplier portal and supplier risk intelligence: daily scans condensed into an A to F grade, with breach and sanctions checks.
Sources
- Regulation (EU) 2022/2554 (DORA), Articles 28, 29 and 30
- Commission Implementing Regulation (EU) 2024/2956 of 29 November 2024, standard templates for the register of information
This page explains the rules in general terms and is not legal advice.
Frequently asked
Do intra-group ICT services go in the DORA register?
Yes. Implementing Regulation (EU) 2024/2956 counts ICT intra-group service providers as direct providers when they sign an arrangement to provide ICT services (Article 1), and a consolidated register includes all ICT intra-group service providers in the group (Article 6(2)).
Does the register have to list subcontractors?
Those that effectively underpin ICT services supporting critical or important functions, or material parts of them, yes (Article 3(2)(b) of Implementing Regulation (EU) 2024/2956). Each is ranked in the ICT service supply chain, and the financial entity makes sure, through the direct provider, that they use a valid LEI or provide their EUID.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

