Vendor Register
Standards ยท DORA RTS 2024/1773

Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy

Rendered when the buyer ticks "DORA financial entity", as a Level 2 instrument under DORA, beside the Regulation's own articles. The register cites 9 of its 14 clauses, behind 5 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, cloud services with no exit plan, and on the obligation rows of every vendor it reaches.

Edition: Commission Delegated Regulation (EU) 2024/1773, OJ L, 2024/1773, 25.6.2024. 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

9 of 14
DORA RTS 2024/1773 Art. 4 Article 4: Main phases of the contract lifecycle

The policy must set rules, responsibilities and processes for each lifecycle phase: management body involvement in decisions on using providers for critical or important functions; planning, including risk assessment, due diligence and approval of new or materially changed contracts; involvement of business units, internal control and other relevant units; implementation, monitoring and management, including at group level; documentation and record-keeping, including the register of information under DORA Article 28(3); and exit strategies and termination.

Evidence an auditor accepts: Lifecycle procedure covering planning, approval, implementation, monitoring, documentation and exit; Approval records for new and materially changed contracts; Evidence of business unit and control function involvement
Common gap: Material contract changes approved without the planned assessments
Source framework: Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy
DORA RTS 2024/1773 Art. 1 Article 1: Proportionality of the third-party policy

The policy on ICT services supporting critical or important functions must reflect the entity's size, risk profile and the complexity of its services, taking into account the type of ICT services contracted; where the provider and its parent are located; whether services come from a Member State or a third country, including where they are delivered from and where data is processed and stored; the nature of data shared; whether the provider is in the same group; whether the provider is authorised, registered, supervised or overseen in the Union or a third country, or designated under the DORA oversight framework; concentration on one or few providers; transferability to another provider; and the potential impact of disruption on continuity and service availability.

Evidence an auditor accepts: Third-party policy section explaining how proportionality factors were applied; Provider location and data location analysis per critical service; Concentration and transferability assessment
Common gap: Policy is a generic template not reflecting the entity's provider landscape
Source framework: Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy
DORA RTS 2024/1773 Art. 5 Article 5: Ex-ante risk assessment

Before a contract is concluded the policy must require the business need to be defined and a risk assessment at entity level and where applicable at group level, covering all DORA and sectoral requirements and the impact on the entity and all risks of the service, including operational, legal, ICT, reputational, confidential and personal data protection, data availability, data location, provider location and ICT concentration risks at entity level.

Evidence an auditor accepts: Business need statement for each new critical ICT arrangement; Pre-contract risk assessment covering each listed risk; Concentration risk analysis at entity level
Common gap: Risk assessment performed after signing
Source framework: Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy
DORA RTS 2024/1773 Art. 8(4) Article 8(4): Formalising material changes and renewal

The policy must require material changes to a contract to be set out in a written document dated and signed by all parties, and must specify the renewal process for the contracts.

Evidence an auditor accepts: Signed and dated contract amendments for material changes; Contract renewal procedure; Renewal calendar with decision records
Common gap: Material changes agreed by email only
Source framework: Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy
DORA RTS 2024/1773 Art. 10 Article 10: Exit from and termination of contracts

The policy must require a documented exit plan for each contract, reviewed and tested periodically, that takes account of unforeseen and persistent service interruptions, inappropriate or failed delivery and unexpected termination. The plan must be realistic and feasible, based on plausible scenarios and reasonable assumptions, with an implementation schedule compatible with the contract's exit and termination terms.

Evidence an auditor accepts: Documented exit plan per contract supporting a critical or important function; Exit plan test or walkthrough records; Scenario analysis for interruption, failed delivery and sudden termination
Common gap: Exit plans written but never tested
Source framework: Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy
DORA RTS 2024/1773 Art. 3(1) and (2) Article 3(1) and (2): Annual review and critical service methodology

The management body must review the policy at least yearly and update it where needed, with changes implemented promptly in the relevant contracts and a documented implementation timeline. The policy must set or refer to a methodology for deciding which ICT services support critical or important functions and state when that assessment is done and reviewed.

Evidence an auditor accepts: Management body minutes of the annual policy review; Implementation timeline for policy changes in contracts; Methodology for classifying ICT services as supporting critical or important functions
Common gap: Policy not reviewed by the management body within the year
Source framework: Commission Delegated Regulation (EU) 2024/1773, the ICT third-party contractual policy
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 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

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