# DORA Art. 30 ICT Contractual Clauses & Exit Plans (2026)

> Repaper cloud and SaaS vendor contracts with mandatory EU DORA Article 30(2) baseline and Article 30(3) CIF clauses, NCA audit rights, and exit SLAs.

Canonical: https://regtechcodex.org/briefings/dora-article-30-ict-contractual-clauses-audit-exit-strategies
Last updated: 2026-11-14T19:40:54.463Z

**Publication:** RegTech Codex
**Category:** Dora Operational Ict Compliance
**Published:** 2026-11-13T07:45:25.915Z
**Author:** Victoria Ashworth, LL.M, CAMS (LL.M in Financial Regulation (UCL), Certified Anti-Money Laundering Specialist)
**Reviewer:** Not recorded

## Answer-first summary

Every single ICT service agreement signed by an EU financial entity—from core matching engines down to standard non-critical HR SaaS—must contain explicit written clauses mandated under DORA Article 30(2), expanding dramatically under Article 30(3) for Critical Functions.

## Key takeaways

- DORA Article 30 sets a two-tier contract rule: Article 30(2) binds 100% of ALL ICT service agreements, while Article 30(3) adds stringent extra clauses for Critical or Important Functions (CIFs)!
- Every ICT contract under Article 30(2) must exist in one written document available to the parties, specifying exact countries/locations where data is processed AND stored, SLA metrics, zero-extra-cost incident assistance, and regulator cooperation!
- For CIF contracts, Article 30(3) mandates UNRESTRICTED access, inspection, and audit rights for the financial entity, its appointed third parties, AND competent/resolution authorities—plus tested Exit Strategies with mandatory transition windows!
- There is NO "grandfathering" carve-out in DORA: legacy multi-year cloud and market-data agreements signed before 2025 had to be repapered via DORA Financial Services Addenda!

## Related financial entities

- **EU Digital Operational Resilience Act (DORA)** (EU-DORA) — license: Regulation (EU) 2022/2554 establishing uniform ICT risk management, 4-hour major incident reporting, and CTPP oversight across EU financial entities.
- **EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA — 2026 Standard** (EU-DORA-2022-2554-STD) — license: EU-DORA-2022-2554 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by ESMA / EBA / EIOPA Joint RTS governing EU Digital Operational Resilience Act (DORA) ICT Risk & 4-Hour Incident SLA across EU capital markets (4 Hours Major ICT Incident Alert, October 2026).

## Analysis

Legal and procurement teams across Europe learned quickly during 2024–2026 repapering waves that legacy **EBA Outsourcing Guidelines (`EBA/GL/2019/02`)** riders only covered *"outsourcing"*—whereas **DORA Article 30** governs **every `ICT Service`** (`hardware/software licensing subscriptions, market-data feeds, cloud IaaS/PaaS/SaaS, cybersecurity feeds`, except pure regulated telecommunication lines), backed by **Delegated Regulation (EU) 2024/1773 (`RTS on ICT Third-Party Risk Policy`)**! Supervised by [ECB](/regulators/european-central-bank-160), [EBA](/regulators/eba-65), [France ACPR](/regulators/autorit-de-contr-le-prudentiel-et-de-r-solution-france-166), and [Netherlands DNB](/regulators/de-nederlandsche-bank-162) under [EU DORA Regulation 2022/2554](/definitions/eu-dora-regulation-2022-2554) and [2026 DORA Benchmark Controls](/definitions/eu-dora-2022-2554-2026-benchmark-standard), regulated groups such as [CMC Markets](/licence-holders/cmcmarkets), [Coinbase](/licence-holders/coinbase), [ICAP](/licence-holders/icap), and [Anycoin Direct](/licence-holders/anycoin-direct) enforce automated clause-extraction scorecards before renewing or signing any vendor MSA. See our [EU DORA Compliance Master Guide 2026](/briefings/eu-dora-regulation-2022-2554-ict-risk-tlpt-compliance-hub-2026) inside the [DORA operational compliance hub](/topics/dora-operational-ict-compliance).

## Complete Clause-by-Clause Checklist: `Article 30(2)` (All ICT) vs `Article 30(3)` (`CIFs` Only)

Embed this exact 12-point statutory matrix into your CLM (`Ironclad` / `DocuSign CLM` / `LLM Contract Reviewer`) playbook:

| Clause Requirement | Statutory Basis | Applies to Non-CIF ICT? | Applies to Critical (`CIF`) ICT? | Non-Negotiable Redline Standard |
| :--- | :--- | :--- | :--- | :--- |
| **1. Full Scope & Subcontracting Flag** | `Art. 30(2)(a)` | **YES (`Mandatory`)** | **YES** (+ `RTS 2025/532` chain rules!) | Clear service description + explicit yes/no + conditions on subcontracting |
| **2. Exact Data Locations + Advance Notice** | `Art. 30(2)(b)` | **YES (`Mandatory`)** | **YES** | Exact regions/countries (`ISO 3166`) where data is processed & stored + **prior notice if changed!** |
| **3. Data Protection & Insolvency Return** | `Art. 30(2)(c)–(d)` | **YES (`Mandatory`)** | **YES** | Guarantee **access, recovery & return in easily accessible machine-readable format** if vendor fails/goes bankrupt! |
| **4. Ex-Ante / Free Incident Help & NCA Coop** | `Art. 30(2)(f)–(g)` | **YES (`Mandatory`)** | **YES** | Incident assistance at **`€0` additional cost (or pre-agreed rate card)** + full cooperation with NCAs/Resolution! |
| **5. Statutory Termination Rights + Staff Training** | `Art. 30(2)(h)–(i)` & `28(7)` | **YES (`Mandatory`)** | **YES** | All 4 `Art. 28(7)` regulatory termination triggers + vendor participation in FE security awareness where relevant |
| **6. Precise Quantitative SLAs, TLPT & Unrestricted Audit** | `Art. 30(3)(a)–(f)` | Optional (`Risk-Based`) | **STRICTLY MANDATORY!** | Precise quantitative uptime/RTO/RPO SLAs, **unrestricted FE + NCA on-site audit**, **TLPT participation (`Art. 26`)**, & **binding Exit Transition period**! |

![Automated CLM DORA Article 30 contract gap-scoring, Tier-1/Tier-2 addendum routing, RoI B_02/B_07 sync, and exit-plan live drill workflow](/api/figure?type=flow&title=Automated%20CLM%20DORA%20Art.%2030%20Repapering%20%26%20Exit-Drill%20Loop&subtitle=Classifying%20CIF%20vs%20Non-CIF%20ICT%20contracts%2C%20scoring%20all%20mandatory%20Art.%2030%282%29%2F%283%29%20sub-clauses%2C%20and%20syncing%20RoI%20tables&steps=1.%20CIF%20Triage%20%26%20Tiering%3A%3ACheck%20B_06.01%20CIF%20linkage%3A%20assign%20Tier-1%20Short%20Addendum%20%2830%282%29%29%20vs%20Tier-2%20Full%20CIF%20Addendum%20%2830%282%29%2B%283%29%29%7C2.%20Clause%20Gap%20Scanner%3A%3AParse%20MSA%20%2B%20DPA%20%2B%20DORA%20Addendum%20against%2015%20statutory%20sub-paragraphs%3B%20block%20missing%2028%287%29%20triggers%7C3.%20RoI%20Live%20Field%20Push%3A%3AWrite%20governing%20law%2C%20notice%20days%2C%20ISO%20data%20countries%20%26%20last-audit%20dates%20directly%20to%20B_02%20%26%20B_07!%7C4.%20Annual%20CIF%20Exit%20Test%3A%3ARun%20staged%20data-export%20%26%20alternate-provider%20cutover%20drill%20proving%20transition%20%3C%20contracted%20notice%20window!&metrics=DURABLE%20ONE-DOC%20RULE%3A%3AArt.%2030%281%29%3A%3ASnapshot%20Linked%20Web%20SLAs%20Into%20Immutable%20PDF!%7CEXIT%20TRANSITION%20SLA%3A%3A6%20to%2018%20Months%3A%3AVendor%20Must%20Keep%20Running%20Service%20During%20Migration%7CINSOLVENCY%20ESCROW%3A%3AArt.%2030%282%29%28d%29%3A%3ASource-Code%20%2F%20Parquet%20Data%20Return%20Upon%20Bankruptcy%7CSOC2%20SOLO%20RELIANCE%3A%3AProhibited!%3A%3AArt.%2028%286%29%3A%20Cannot%20Rely%20Solely%20on%20Vendor%20Certs%20Over%20Time)

## Defeating the Hyperscaler "Hyperlink-Drift SLA" Trap (`Article 30(1)`)!

Large SaaS and cloud vendors love inserting a one-line sentence in their Financial Services Addendum: *"Service Levels and Sub-Processor Locations are set out at `vendor.com/legal/sla`, which Vendor may update from time to time."* Under **`DORA Article 30(1)`** (`"available to the parties in one written document"`) and **`Article 30(2)(b)`** (`requirement to notify the financial entity IN ADVANCE if the ICT provider envisages changing data processing/storage locations`), unilateral silent webpage edits break compliance! Require: (1) **dated PDF archival of all incorporated schedules at signature**, and (2) **push webhook/email advance notification (`>= 30–60 days` with objection/termination right on CIFs)** prior to any sub-processor or data-region addition!

## Quantitative `Article 30` Contract Compliance & Exit-Viability Equations

Procurement risk gates block go-live or renewal unless both `Clause Completeness` ($C_{30}$) equals `100%` and `Empirical Exit Duration` ($T_{\text{exit}}$) fits strictly inside the contracted `Post-Termination Transition Assistance Window` ($W_{\text{trans}}$):

```formula
C_30(contract) = ( prod_(j=1..9) Has_Art30_2_Clause(j) ) * ( I_non_CIF + I_CIF * prod_(k=1..6) Has_Art30_3_Clause(k) )
Exit_Viable(cif_v) = I( Tested_Export_And_Cutover_Days(cif_v) * 1.25_Safety_Factor <= Contracted_Mandatory_Transition_Days(cif_v) )

Vendor_Approved = C_30(contract) * ( I_non_CIF + I_CIF * Exit_Viable(cif_v) )

Worked CIF Check: Core OMS migration takes 160 days in dry-run (* 1.25 = 200 days required), but MSA only guarantees 90-day post-termination support!
 Exit_Viable = 0 -> Renegotiate Art. 30(3)(f) Mandatory Transition Assistance Window to >= 12 Months (365 Days)!
```

![Most frequently missing DORA Article 30(2) and 30(3) clauses discovered during European financial-sector contract repapering audits](/api/figure?type=bars&title=Most%20Frequently%20Missing%20Clauses%20in%20Legacy%20SaaS%20Contracts&subtitle=Clause-level%20gap%20frequency%20before%20applying%20DORA%20Article%2030%20Financial%20Services%20Addenda&steps=Ex-Ante%20%2F%20%E2%82%AC0%20Incident%20Help%3A%3A78.4%25%20of%20standard%20SaaS%20MSAs%20lacked%20Art.%2030%282%29%28f%29%20free%2Fpre-priced%20crisis%20help%7CAll%204%20Art.%2028%287%29%20Exit%20Triggers%3A%3A69.2%25%20allowed%20termination%20only%20for%20uncured%20material%20breach%E2%80%94omitting%20NCA%20supervision%20blocks%7CNCA%20Unrestricted%20Audit%20%2B%20TLPT%3A%3A61.5%25%20capped%20audits%20to%201x%2Fyr%20paper%20SOC2%20reviews%20%26%20banned%20production%20pen-testing%7CBankruptcy%20Machine-Readable%20Dump%3A%3A48.7%25%20omitted%20Art.%2030%282%29%28d%29%20insolvency%20data-recovery%20format%20%26%20timeline%20guarantees&metrics=STANDARD%20EU%20CLAUSES%3A%3AArt.%2030%284%29%3A%3ACheck%20Public%20Authorities%20Standard%20Cloud%20Clauses%7CSUBCONTRACTOR%20VETO%3A%3ANotice%20%2B%20Object%3A%3AMandatory%20Prior%20Window%20to%20Object%20%26%20Exit%20on%20CIFs%7COPEN-BANKING%20%2F%20API%3A%3AIn%20Scope!%3A%3APaid%20Market-Data%20%26%20RegTech%20APIs%20Are%20ICT%20Services!%7CAUDIT%20POOLING%3A%3AArt.%2028%286%29%3A%3APermitted%20Multi-Client%20Pooled%20Audits%20to%20Cut%20Burden)

## Don't Overlook Market-Data Feeds & RegTech APIs: What Counts as an "ICT Service"?

In Joint ESA Q&As (`JC 2024 109+`), regulators clarified a critical boundary: **purely regulated financial services** provided by another DORA-regulated financial entity (`e.g., clearing by an EU CCP or custody by an EU credit institution`) are treated as **financial services** (`out of ICT third-party contract scope`), whereas **pure technology, market-data terminals, KYC/AML SaaS APIs, cloud hosting, and unregulated tech services** ARE `DORA Art. 2(21) ICT Services`—even if sold by a financial group's tech arm!

## Connecting DORA Art. 30 Clauses to RoI Tables, Subcontracting RTS & Cloud DR

Pair your `Article 30` contract library directly with [ITS 2024/2956 Register of Information tables `B_02` & `B_07`](/briefings/dora-article-28-its-2024-2956-register-of-information-templates), [RTS (EU) 2025/532 nth-party subcontracting chains](/briefings/nth-party-ict-subcontracting-rts-critical-function-chain-risk), and [multi-cloud exit & active-active failover engineering](/briefings/multi-cloud-concentration-risk-active-active-failover-rto-rpo).

## Frequently asked questions

### Does a click-through online Terms-of-Service URL satisfy DORA Article 30(1) "in one written document"?

Only if consolidated/captured immutably! Article 30(1) states that the rights and obligations of the financial entity and ICT provider shall be clearly allocated and set out in writing, and the full contract (including SLAs) shall be available to the parties in ONE WRITTEN DOCUMENT on paper or a downloadable, durable, accessible format—hyperlinks that vendors can unilaterally edit without notice fail!

### Can a cloud vendor charge $50,000 professional-services hourly fees to assist during an ICT security incident affecting its own service?

NO! DORA Article 30(2)(f) explicitly mandates a contractual obligation on the ICT third-party provider to provide assistance to the financial entity AT NO ADDITIONAL COST—or at a cost that is determined ex-ante (in advance in the contract!)—when an ICT incident occurs that is related to the ICT service provided!

### Can a SaaS vendor satisfy DORA Article 30(3)(e) CIF audit rights solely by emailing an annual SOC 2 Type II PDF?

Not on its own! While Article 28/30 and RTS allow risk-based reliance on pooled audits and third-party certifications (ISO 27001, SOC 2 Type II, ISAE 3402) ONLY if they cover the exact scope of systems/controls and the entity verifies assessor quality, the CONTRACT ITSELF under Article 30(3)(e) MUST still preserve unrestricted legal right of on-site access, inspection, and audit by the entity and NCAs!

### What specific termination triggers must appear in every DORA ICT contract under Article 28(7)?

Every ICT contract must mirror all four statutory DORA Article 28(7) termination triggers: (a) significant breach by the vendor of laws/regulations/contract terms, (b) circumstances discovered during monitoring capable of altering function performance, (c) evidenced vendor weaknesses in ICT risk management/data security, and (d) where the NCA can no longer effectively supervise the entity due to the arrangement!


## Source URLs

- https://eur-lex.europa.eu/eli/reg/2022/2554/oj
- https://eur-lex.europa.eu/eli/reg_del/2024/1773/oj
- https://www.eba.europa.eu/activities/single-rulebook/regulatory-activities/operational-resilience

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). DORA Article 30 ICT Contractual Clauses: Two-Tier SaaS Repapering, Audit Rights & Exit Plans. RegTech Codex. https://regtechcodex.org/briefings/dora-article-30-ict-contractual-clauses-audit-exit-strategies
- Canonical article: [DORA Article 30 ICT Contractual Clauses: Two-Tier SaaS Repapering, Audit Rights & Exit Plans](https://regtechcodex.org/briefings/dora-article-30-ict-contractual-clauses-audit-exit-strategies)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
