In this guide
DORA requires financial entities within its scope to maintain and update a comprehensive Register of Information on contractual arrangements with ICT third-party service providers. The register’s value goes beyond recording information: it connects every provider and service to the functions it supports, risk, contracts, subcontracting and the ability to transition or exit. UniLoud can handle technical discovery, vendor and service mapping, evidence gathering, register structure and operational monitoring in collaboration with compliance, procurement and legal advisers.
Why third-party risk is central to DORA
Financial organisations rely on cloud platforms, SaaS, telecommunications, managed services, data centres, security providers and specialist applications. An incident at a third-party provider can affect a critical function without the business making any changes to its own network.
DORA treats this dependency as part of ICT risk management. Since 17 January 2025, in-scope financial entities must maintain a comprehensive register of contractual arrangements with ICT third-party providers. Authorities use these data for supervision and to identify critical ICT third-party providers.
What we need to know about each ICT provider
- The exact ICT service it provides and the business function it supports.
- Whether the service supports a critical or important function and who the business owner is.
- Which data, systems, locations or identities are affected by the service.
- The contract duration, renewal and termination arrangements, and main service dependencies.
- Where subcontracting or concentration risk needs to be assessed.
- Available monitoring, SLA, incident notification, backup, portability and exit capabilities.
- The technical information required to transition to another provider or return in-house.
How we can help build a practical Register of Information
- We identify vendors and services through invoices, contracts, IT documentation, Microsoft 365, firewall and network records, cloud subscriptions and operational interviews.
- We standardise service and provider names to remove duplicates and unclear entries.
- We map each service to the infrastructure and business functions it supports.
- We collect technical information: environments, data locations, connectivity, administrators, dependencies and subcontractors where known.
- We connect the register to ownership, risk ratings, review dates and evidence locations.
- We deliver a structured export or working register and a process to update it when a provider or contract changes.
What is needed beyond the register
- Vendor due diligence before a new critical ICT relationship.
- Risk review before major changes, migrations or new cloud dependencies.
- Operational SLA monitoring and recording of recurring incidents or outages.
- Exit readiness: accounts, data, configurations, backups, portability and a migration plan.
- A tabletop exercise for failure of a critical provider or loss of access.
- A clear process for procurement, legal, compliance and IT to update the same source of truth.
What UniLoud can handle and where our role ends
UniLoud can cover the technical and operational aspects: discovery, architecture mapping, risk evidence, vendor and service inventory, resilience testing, monitoring, backup/DR, migration readiness and technical remediation.
Contractual clauses, formal legal interpretation and regulatory acceptance remain the responsibility of the business and its legal and compliance advisers. Our role is to provide an accurate technical picture and implement the agreed controls.
Frequently asked questions
Must all in-scope financial entities maintain a Register of Information?
Official ESA guidance states that financial entities subject to DORA must maintain a register of contractual arrangements with ICT third-party providers, applying proportionality within risk management.
Is a supplier spreadsheet enough?
Not if it does not connect the provider, ICT service, contract, function, ownership and risk. The goal is an operational source of truth that can be maintained and used in an audit, incident or migration.
Can UniLoud review contracts too?
We can identify technical and operational gaps and provide requirements to procurement or legal teams. We do not replace legal assessment or issue legal opinions.
Note: This material is informational and technical. It is not legal advice. Final applicability, official notifications and contractual requirements should be confirmed with the responsible management, compliance team and legal advisers.
Related services and guides
- Technical support for compliance
- UniLoud Monitoring
- UniLoud Disaster Recovery
- Hybrid IT
- UniLoud Protection
- Managed IT
Discuss your next step with UniLoud
If you do not currently have a unified view of ICT providers, their services and critical dependencies, UniLoud can start with a DORA Third-Party ICT Discovery Workshop and deliver a structured register, gap list and remediation roadmap.
