Vendor Register
Regimes ยท DORA

DORA, the Digital Operational Resilience Act

Attaches to contractual arrangements for ICT services: cloud, software, network, managed services and data feeds. A supply of hardware, a bank or a courier is recorded in the register only where a service element sits in the contract.

On the register, tick "DORA financial entity" and these rows appear on every vendor the regime reaches. Framework page.

Which vendors it reaches

FamiliesCloud and hosting, Software and SaaS, Network and connectivity, Managed and professional services, Data and content
On every vendorDORA Art. 28, DORA Art. 30, DORA RTS 2024/1773 Art. 8(1) and (2), DORA RTS 2024/1773 Art. 9
Cloud and hostingthe clauses on every vendor only
Software and SaaSthe clauses on every vendor only
Network and connectivitythe clauses on every vendor only
Managed and professional servicesthe clauses on every vendor only
Data and contentthe clauses on every vendor only
Supports a critical or important function (rated critical or important on the register)DORA Art. 29, DORA RTS 2024/1773 Art. 6, DORA RTS 2025/532 Art. 3(2) and (3)
Informational, cloud and hosting, managed and professional servicesDORA Art. 31: the ESAs designate critical ICT third-party providers; the entity accounts for their use, it owes them no clause

DORA Article 30, key contractual provisions

The clauses the register expects in every vendor agreement the regime reaches, and the further clauses for a vendor rated critical.

  1. A clear and complete description of the functions and ICT services provided
  2. The locations, by region or country, where the service is provided and the data processed, with notice before a change
  3. Availability, authenticity, integrity and confidentiality of data, including personal data
  4. Access, recovery and return of data on the provider's insolvency, resolution or the termination of the arrangement
  5. Service level descriptions, including their updates and revisions
  6. Assistance on an ICT incident affecting the service, at no or pre-set cost
  7. Cooperation with the competent and resolution authorities
  8. Termination rights and the minimum notice period, in line with the supervisors' expectations
  9. Participation of the provider's staff in the entity's ICT security awareness and training
  10. Material changes set out in a written document dated and signed by all parties, and the renewal process stated (Delegated Regulation (EU) 2024/1773 Art. 8(4))

Where the vendor supports a critical or important function (rated critical or important on the register)

  1. Full service level agreements with performance targets and the remedies when they are missed
  2. Notice periods and reporting obligations, including notice of developments that could affect the service
  3. Business continuity plans and ICT security measures, tested, with results shared
  4. Participation in threat-led penetration testing where the entity runs it
  5. Unrestricted rights of access, inspection and audit, for the entity and for the competent authority (a microenterprise may agree that its own rights pass to an independent party the provider appoints, Art. 30(3))
  6. Exit strategies, with a transition period long enough to migrate without disruption
  7. Which ICT services supporting critical or important functions, or material parts of them, may be subcontracted and on what conditions, with the provider responsible for what its subcontractors deliver (Delegated Regulation (EU) 2025/532 Art. 4(1))
  8. Notice of intended material changes to the subcontracting, in time to assess them, with a notice period to approve or object before anything is implemented (Delegated Regulation (EU) 2025/532 Art. 5)
  9. A termination right where a critical or important service is subcontracted without the contract permitting it, or a material change is made over the entity's objection (Delegated Regulation (EU) 2025/532 Art. 6)

The register of information

Article 28(3) asks every financial entity to keep a register of information on its contractual arrangements for ICT services and to report it to the competent authority. Vendor Register exports one row per vendor with these fields, as Vendor Register names them, following what the supervisory template asks for:

  1. Vendor
  2. Identification (LEI or registration, if held) template B_05.01: a valid and active LEI or EUID of the provider, listed with the providers and their subcontractors (DORA ITS 2024/2956 Art. 3(5))
  3. Type of ICT service template B_02.02: the ICT services in scope of each contractual arrangement (DORA ITS 2024/2956 Art. 5(1)(d) to (f))
  4. Category (register)
  5. Function supported (systems) template B_06.01: the functions that use the ICT services, one identifier per entity, activity and function (DORA ITS 2024/2956 Art. 5(1)(m))
  6. Criticality template B_06.01: whether the function is critical or important (DORA ITS 2024/2956 Art. 5(1)(m))
  7. Country of the provider
  8. Country of provision
  9. Annual spend
  10. Share of spend
  11. Substitutability template B_07.01: substitutability of the provider and the reason where it is hard to substitute (DORA ITS 2024/2956 Art. 5(1)(n))
  12. Single source template B_07.01: whether alternative providers have been identified (DORA ITS 2024/2956 Art. 5(1)(n))
  13. Sub-outsourcing chain template B_05.02: the ICT service supply chain with each provider's rank (DORA ITS 2024/2956 Art. 5(1)(k) and (l))
  14. Contract end
  15. Exit plan template B_07.01: whether an exit plan exists and whether the service could be reintegrated (DORA ITS 2024/2956 Art. 5(1)(n))
  16. ICT service in DORA scope

A column the paste cannot fill is exported blank and raised as the finding "DORA register-of-information fields missing". The template named beside a column is the one whose text in Implementing Regulation (EU) 2024/2956 asks for it; a column with no template is one that text does not name.

Level 2 instruments cited on the same tick

Three delegated and implementing regulations under Article 28 to 30 are cited beside the Regulation's own articles, on the register's findings and obligation rows, with no further tick:

  1. Commission Implementing Regulation (EU) 2024/2956, the register of information templates: Commission Implementing Regulation (EU) 2024/2956, OJ L, 2024/2956, 2.12.2024. 11 clauses cited.
  2. Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy: Commission Delegated Regulation (EU) 2024/1773, OJ L, 2024/1773, 25.6.2024. 9 clauses cited.
  3. Commission Delegated Regulation (EU) 2025/532, ICT subcontracting: Commission Delegated Regulation (EU) 2025/532, OJ L, 2025/532, 2.7.2025. 6 clauses cited.

DORA (Regulation (EU) 2022/2554): Regulation (EU) 2022/2554, OJ L 333, 27.12.2022.

The clauses, quoted

8 of 26 in the framework

Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim.

DORA Art. 28 ICT third-party risk: general principles

Financial entities manage ICT third-party risk as part of ICT risk inside the ICT risk management framework, remain fully responsible for their obligations when they use ICT services, and apply proportionality according to the nature and importance of ICT dependencies and the criticality of each service. They keep a register of information on all ICT service arrangements at entity, sub-consolidated and consolidated level, distinguishing those supporting critical or important functions; report at least yearly to the authority on new arrangements, provider categories, contract types and services; provide the full register or sections of it on request; and inform the authority in time of planned arrangements for critical or important functions. Before contracting they assess criticality, supervisory conditions, risks including concentration, due diligence and conflicts of interest; they use only providers meeting appropriate security standards, set risk-based audit frequencies, ensure contracts can be terminated in the listed cases, and keep tested exit strategies for services supporting critical or important functions. The ICT third-party risk strategy with its policy on critical or important functions (Art. 28(2)) is required only of entities other than Article 16(1) entities and microenterprises.

Evidence an auditor accepts: Register of information on all ICT service arrangements at entity and consolidated level, flagging critical or important functions; Yearly report to the competent authority on new arrangements, provider categories, contract types and services, with submission confirmation; Pre-contract assessment files covering criticality, supervisory conditions, risk and concentration, due diligence and conflicts of interest
Common gap: Register omits intra-group or low-value ICT arrangements
Source framework: DORA (Regulation (EU) 2022/2554)
DORA Art. 30 Key contractual provisions

Contracts set out the rights and obligations of both parties in one written document, available on paper or another durable, downloadable format, including the service levels. Every ICT services contract covers at least: the functions and services and whether and how subcontracting is permitted; service and data processing locations, with advance notice of changes; data protection provisions; access, recovery and return of data on insolvency, resolution, discontinuation or termination; service level descriptions; incident assistance at no cost or a cost fixed in advance; cooperation with competent and resolution authorities; termination rights and minimum notice periods; and participation in security awareness training. Contracts for services supporting critical or important functions add: full service levels with quantitative and qualitative targets, notice and reporting duties, provider contingency testing and security measures, participation in the entity's TLPT, unrestricted access, inspection and audit rights for the entity and the authority, and exit strategies with a mandatory transition period (Art. 30(3)). A microenterprise may agree with the provider that its access, inspection and audit rights are handed to an independent party that the provider appoints, from which it can request information and assurance at any time (Art. 30(3), final subparagraph). Standard contractual clauses from public authorities should be considered.

Evidence an auditor accepts: ICT service contracts held as a single written document that includes the service level agreement; Contract clause checklist per contract mapped to the Article 30(2) minimum elements; For critical or important functions: clauses on quantitative service targets, TLPT participation, unrestricted audit and access rights and exit transition periods
Common gap: Contract silent on data location changes or data return on termination
Source framework: DORA (Regulation (EU) 2022/2554)
DORA RTS 2024/1773 Art. 8(1) and (2) Article 8(1) and (2): Written contracts with DORA clauses and audit and testing rights

Contracts must be in writing and include all elements of DORA Article 30(2) and (3), plus elements on Article 1(1)(a) and other relevant law. They must give the entity rights to access information, inspect, audit and test ICT, which it exercises through its own internal audit or an appointed third party and, where appropriate, pooled audits and pooled ICT testing including TLPT with other clients of the provider, third-party certifications, and internal or third-party audit reports made available by the provider, without reducing its own ultimate responsibility.

Evidence an auditor accepts: Executed written contracts with a DORA Article 30 clause mapping; Audit, inspection and testing right clauses; Audit plan for critical providers including pooled audits where used
Common gap: Contracts missing Article 30(3) clauses for critical services
Source framework: Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy
DORA RTS 2024/1773 Art. 9 Article 9: Monitoring of the contractual arrangements

The policy must require contracts to set measures and key indicators to monitor provider performance continuously, including data confidentiality, availability, integrity and authenticity and compliance with the entity's policies, and remedies such as contractual penalties when service levels are missed. It must specify how the entity checks that providers meet performance and quality standards, ensuring that providers deliver periodic, incident, service delivery, ICT security and business continuity and testing reports; performance is assessed through KPIs, key control indicators, audits, self-certifications and independent reviews; other relevant information is received; the entity is notified of ICT-related incidents and operational or security payment-related incidents; and independent reviews and audits verify compliance. The assessment must be documented and used to update the risk assessment, and the policy must set measures for provider shortcomings and how their timely implementation is monitored according to materiality.

Evidence an auditor accepts: KPI and key control indicator dashboards per critical provider; Provider reports on service delivery, security, incidents and continuity testing; Service level breach log and penalties applied
Common gap: Provider incident notifications not required by contract
Source framework: Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy
DORA Art. 29 Preliminary assessment of ICT concentration risk at entity level

When assessing ICT third-party arrangements supporting critical or important functions, financial entities shall assess ICT concentration risk, including the risks of contracting providers that are not easily substitutable or of multiple arrangements with the same or closely connected providers, and the implications of subcontracting.

Evidence an auditor accepts: ICT concentration-risk assessment for critical/important-function arrangements
Common gap: Concentration risk not assessed
Source framework: DORA (Regulation (EU) 2022/2554)
DORA RTS 2024/1773 Art. 6 Article 6: Due diligence on prospective providers

The policy must set a proportionate selection and assessment process, noting whether the provider is intra-group, and require the entity to assess before contracting whether the provider has the reputation, abilities, expertise, financial, human and technical resources, security standards, organisation, risk management, internal controls and any required authorisation; can track technology and adopt security leading practice; uses or plans to use subcontractors for the service or material parts; is located or processes or stores data in a third country and how that affects operational, reputational or sanctions risk; agrees to effective audits including on-site by the entity, appointed third parties and authorities; and acts ethically and responsibly, respecting human and children's rights, environmental principles and working conditions. The policy must set the required level of assurance on the provider's risk management, including its continuity measures, and state which assurance sources are used: own or commissioned audits, independent audit reports, the provider's internal audit reports, certifications or other information, using more than one where appropriate.

Evidence an auditor accepts: Due diligence questionnaire and assessment per prospective provider; Financial standing and reputation checks; Subcontracting and third-country location disclosures
Common gap: Due diligence relies on a single certification
Source framework: Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy
DORA RTS 2025/532 Art. 3(2) and (3) Article 3(2) and (3): Periodic reassessment and retained responsibility

Entities whose providers subcontract ICT services supporting critical or important functions must periodically repeat the assessments of Article 3(1)(f) to (j) in the light of changes in their business environment, supported functions, ICT threats, concentration and geopolitical risks. Relying on the provider's own assessment of its subcontractors does not limit the entity's final responsibility for its DORA obligations.

Evidence an auditor accepts: Periodic subcontracting reassessment records with dates; Triggers for reassessment such as geopolitical or concentration changes; Evidence of the entity's own review where provider assessments are used
Common gap: Reassessment never repeated after onboarding
Source framework: Commission Delegated Regulation (EU) 2025/532, ICT subcontracting
DORA Art. 31 Designation of critical ICT third-party service providers

The ESAs, through the Joint Committee, designate which ICT third-party service providers are critical, according to systemic impact, the importance of the institutions relying on them, reliance for critical or important functions and substitutability, and publish the list yearly; each designated provider gets a Lead Overseer and must tell the financial entities it serves of its designation. Designation does not cover financial entities that supply ICT services to other financial entities, providers under oversight supporting Article 127(2) TFEU tasks, intra-group providers, or providers serving only entities active in a single Member State (Art. 31(8)). For financial entities the duty is to track which of their providers are designated and reflect it in third-party risk management; a designated provider established in a third country may be used only if it has set up a Union subsidiary within 12 months of designation (Art. 31(12)).

Evidence an auditor accepts: Dated cross-check of the entity's ICT provider register against the published list of critical providers; Designation notices received from providers; Evidence that any designated third-country provider in use has a Union subsidiary established within 12 months of designation
Common gap: Register not reconciled with the yearly ESA list
Source framework: DORA (Regulation (EU) 2022/2554)

See what it attaches to your list

Paste the vendor list, tick the regime, and every vendor it reaches carries these rows. Eight vendors free, no account.

Build my vendor register