Vendor Register
Standards ยท DORA

DORA (Regulation (EU) 2022/2554)

Rendered when the buyer ticks "DORA financial entity". The register cites 4 of its 26 clauses, behind 7 findings: single-source vendors with no fallback named, concentration at or above the threshold, contracts ending inside 90 days with no re-tender noted, critical vendors with no contract end recorded, dora register-of-information fields missing, cloud services with no exit plan, sub-outsourcing chains longer than one hop, and on the obligation rows of every vendor it reaches.

Edition: Regulation (EU) 2022/2554, OJ L 333, 27.12.2022. 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. Framework page. What it attaches to a vendor: the DORA regime page.

Clauses cited

4 of 26
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. 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 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 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 which clauses your list engages

Paste the list and every vendor names the clauses behind it, filtered to the regimes that apply to you. Eight vendors free, no account.

Build my vendor register