# DORA Subcontracting RTS 2025/532 & Nth-Party ICT Chains

> Implement EU DORA Commission Delegated Regulation (EU) 2025/532 (RTS on Subcontracting) governing Rank-2+ ICT chains supporting Critical or Important Functions.

Canonical: https://regtechcodex.org/briefings/nth-party-ict-subcontracting-rts-critical-function-chain-risk
Last updated: 2026-11-16T17:07:12.809Z

**Publication:** RegTech Codex
**Category:** Dora Operational Ict Compliance
**Published:** 2026-11-13T06:05: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

Adopted on March 24, 2025 as Commission Delegated Regulation (EU) 2025/532, DORA’s Subcontracting RTS closes the fourth-party blind spot—forcing financial entities to assess chain complexity before contract signature and hold contractual termination rights over material subcontractor changes.

## Key takeaways

- Commission Delegated Regulation (EU) 2025/532 (the DORA Subcontracting RTS supplementing Article 30(5)) governs all ICT subcontracting chains supporting Critical or Important Functions (CIFs) or material parts thereof!
- Before authorizing ANY CIF subcontracting (Article 3 of RTS 2025/532), the financial entity must perform a documented pre-contractual risk assessment covering chain length/complexity, fourth-party concentration, data location, and NCA auditability!
- Under Articles 4–6 of RTS 2025/532, Rank-1 ICT contracts MUST require advance written notice of material CIF subcontractor changes—with an explicit right for the firm to object, modify, and terminate!
- If the direct ICT vendor implements a material CIF subcontractor change BEFORE the notice window expires or OVER a documented objection (absent an emergency security fix), the firm holds an immediate right to terminate!

## 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

July 19, 2024 (`CrowdStrike Falcon kernel sensor update`), the `SolarWinds` Orion build compromise, and `MOVEit` MFT zero-day attacks proved a foundational truth of modern financial infrastructure: **catastrophic systemic outages rarely originate in your direct `Rank 1` contract—they erupt two or three hops deeper inside shared `Rank 2` and `Rank 3` ICT subcontractors**! Enacted as **Commission Delegated Regulation (EU) 2025/532 (`RTS specifying elements when subcontracting ICT services supporting critical or important functions`)** and enforced by [ECB](/regulators/european-central-bank-160), [EBA](/regulators/eba-65), [France AMF](/regulators/amf), and [Netherlands AFM](/regulators/afm) 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 institutions like [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), [Coinbase](/licence-holders/coinbase), and [Anycoin Direct](/licence-holders/anycoin-direct) operationalize graph-based fourth-party risk governance. Review 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).

## Four Mandatory Lifecycle Gates in `RTS (EU) 2025/532` (`Articles 1–7`)

Every procurement, TPRM, and legal team must wire these four articles of `Delegated Regulation (EU) 2025/532` into CIF vendor onboarding and change monitoring:

| RTS 2025/532 Article | Lifecycle Stage | Mandatory Financial-Entity Control | Flow-Down Duty on `Rank 1` Vendor | RoI Table Synchronization |
| :--- | :--- | :--- | :--- | :--- |
| **`Arts. 1–3` Pre-Contract Risk Check** | Before Signing / Enabling CIF Subcontracting | Assess **chain length & complexity**, **third-country insolvency/supervision obstacles**, & **hidden `Rank-2+` concentration**! | Disclose complete list of `Rank 2..N` ICT subcontractors underpinning the `CIF` (`with LEIs/EUIDs & ISO locations`) | Populate initial **`B_05.02` (`Rank 1..N`)** & `B_07.01` |
| **`Art. 4` Flow-Down Conditions** | Contract Execution | Verify `Rank 1` contract enforces security, incident-reporting, continuity/backup & **unrestricted FE + NCA audit pass-through**! | Continuously monitor `Rank 2..N` SLA/security KPIs; remains **100% contractually liable** to Financial Entity! | Record audit & location flags in `B_02.02` |
| **`Art. 5` Material Change Gate** | Ongoing Subcontractor Add/Swap | Ingest advance webhook/written notice -> Run **automated Concentration & Geo Risk Delta check** -> **Approve OR Object in writing**! | Provide **advance notice** (`prior to go-live!`) + risk evidence on any material CIF subcontractor change | Trigger `<=5d` live update to **`B_05.02`**! |
| **`Arts. 6–7` Termination Triggers** | Risk Breach / Unauthorized Change | Exercise **contractual right to terminate** (`triggering Art. 30(3)(f) transition support!`) if material risk unmitigated! | Forbidden from pushing unapproved material CIF subcontractor changes over valid FE objection! | Archive exit trigger & transition timeline |

![Graph-database Nth-party ICT supply-chain concentration analyzer and RTS 2025/532 material subcontractor change objection workflow](/api/figure?type=flow&title=RTS%202025%2F532%20Nth-Party%20Graph%20%26%20Change-Objection%20Engine&subtitle=Ingesting%20vendor%20sub-processor%20webhooks%2C%20computing%20Rank-2%2B%20Herfindahl%20concentration%20spikes%2C%20and%20gating%20B_05.02%20updates&steps=1.%20Sub-Processor%20Webhook%3A%3AIngest%20Rank-1%20vendor%20sub-processor%20change%20notice%20%2860d%20advance%29%20%2B%20parse%20GLEIF%20LEI%20%26%20ISO%20country%7C2.%20Graph%20Blast%20Simulation%3A%3AQuery%20Neo4j%2FSQL%20B_05.02%20graph%3A%20how%20many%20CIFs%20already%20depend%20on%20this%20proposed%20Rank-2%2F3%20node%3F%7C3.%20Geo%20%26%20Sanctions%20Gate%3A%3ACheck%20third-country%20data-localization%20laws%2C%20CLOUD%2FFISA%20exposure%20%26%20NCA%20audit%20obstacles%20%28Art.%203%29%7C4.%20Approve%20or%20Art.%206%20Exit%3A%3AClear%20%26%20update%20RoI%20B_05.02%20OR%20serve%20formal%20Art.%205%20Written%20Objection%20%28unlocking%20Art.%206%20Exit!%29&metrics=GRAPH%20VISIBILITY%3A%3ARank%201%20to%20N%3A%3AFull%20CIF%20Chain%20Mapped%20in%20RoI%20Table%20B_05.02%7CCONCENTRATION%20ALERT%3A%3A%3E%2035%25%20CIF%20Share%3A%3AFlags%20Single%20Rank-2%20Cloud%20Region%20%2F%20CDN%20Node!%7CUNNOTIFIED%20CHANGE%3A%3ABreach%20%3D%20Exit%3A%3ARTS%20Art.%206%281%29%28b%29%20Statutory%20Termination%20Right%7CSBOM%20INTEGRATION%3A%3ACycloneDX%20%2F%20SPDX%3A%3ATracks%20Embedded%20Commercial%20Libraries%20%26%20Agents)

## Exposing "Illusory Multi-Vendor Redundancy" via `Rank-2` Graph Queries!

Suppose your trading desk hires **Primary Market-Data Vendor X** and **Backup Market-Data Vendor Y**, paying €400,000/year for "dual-vendor resilience." When you populate **`B_05.02`** under `RTS 2025/532`, your graph query reveals that **both Vendor X and Vendor Y terminate fiber cross-connects in the exact same Frankfurt data-center hall (`Rank 2`) and authenticate API tokens through the exact same identity SaaS (`Okta/Auth0 tenant region`, `Rank 2`)**! Without `Rank-2/3` graph modeling, your "backup vendor" fails at the exact millisecond your primary vendor fails.

## Quantitative `Nth-Party` Node Centrality & Hidden Concentration Index ($H_{\text{nth}}$)

Operational risk teams compute **CIF Supply-Chain Node Concentration** ($S_{\text{node}}(u)$) across every `Rank >= 2` provider or cloud availability zone $u$ in the `B_05.02` directed acyclic graph:

```formula
CIF_Reach(u) = { f in All_CIFs : Exists_Directed_Supply_Path( f -> Rank_1 -> ... -> u ) }
Weighted_Blast(u) = ( sum_(f in CIF_Reach(u)) Revenue_And_Regulatory_Weight(f) ) / ( sum_(f in All_CIFs) Revenue_And_Regulatory_Weight(f) )

Change_Risk_Block = I( Weighted_Blast_Post_Change(u_new) > Max_Board_Concentration_Appetite OR NCA_Audit_Blocked_Jurisdiction(u_new) == 1 )

Worked Graph Discovery: 11 distinct Rank-1 SaaS tools route through AWS eu-central-1 -> Weighted_Blast = 78.5% of CIFs! Mandate Multi-Region / Secondary Cloud!
```

![Practical obstacles encountered by EU financial entities implementing DORA Subcontracting RTS (EU) 2025/532 across SaaS chains](/api/figure?type=bars&title=Implementation%20Challenges%20in%20DORA%20RTS%202025%2F532%20Chains&subtitle=Survey%20of%20TPRM%20engineering%20bottlenecks%20across%20Rank-2%20and%20Rank-3%20ICT%20supplier%20discovery&steps=Opaque%20SaaS%20Sub-Processor%20Webs%3A%3A36.9%25%20listed%2040%2B%20generic%20sub-processors%20without%20mapping%20which%20touch%20CIFs%7CPassive%20RSS%20Pull-Only%20Notices%3A%3A27.8%25%20forced%20clients%20to%20poll%20a%20webpage%20instead%20of%20pushing%20active%20advance%20notice%7CShort%20%3C14d%20Objection%20Windows%3A%3A20.6%25%20gave%20only%2010-14%20days%20notice%E2%80%94too%20short%20for%20Art.%203%20risk%20assessment%20%2B%20exit!%7CMissing%20Rank-2%2F3%20GLEIF%20LEIs%3A%3A14.7%25%20disclosed%20marketing%20brand%20names%20%28%22AWS%22%20%2F%20%22Twilio%22%29%20instead%20of%20exact%20legal%20entity%20LEI&metrics=BRAND%20!%3D%20LEGAL%20ENTITY%3A%3AExact%20Sub%20LEI!%3A%3ALog%20AWS%20EMEA%20SARL%20LEI%2C%20Not%20Generic%20%22Amazon%22!%7CPUSH%20NOTIFICATION%3A%3AMandatory%3A%3ARequire%20Active%20Email%2FWebhook%20Sub-Processor%20Alerts%7CNOTICE%20WINDOW%20TARGET%3A%3A%3E%3D%2030%20-%2060%20Days%3A%3AGives%20TPRM%20Time%20to%20Assess%20%26%20Challenge%20Under%20Art.%205%7CFOURTH-PARTY%20DRILL%3A%3ATabletop%20Yearly%3A%3ASimulate%20Simultaneous%20Rank-2%20Cloud%2FEDR%20Outage)

## Practical Fix: Never Log "Brand Names" (`AWS`, `Azure`, `Cloudflare`) in `B_05.02`!

In `RoI` table `B_05.02`, typing `"Microsoft Azure"` fails immediately—because Microsoft operates separate US (`Microsoft Corporation`) and European (`Microsoft Ireland Operations Limited`) contracting and infrastructure legal entities, each holding its own distinct **20-character `GLEIF LEI`**! Require every `Rank 1` vendor's `DORA Sub-Processor Schedule` to state the **exact legal corporate name, country of incorporation, `LEI`/`EUID`, and `ISO 3166` data-center country** of each `Rank 2` CIF subcontractor.

## Connecting Subcontracting RTS 2025/532 to RoI Tables, Art. 30 & Multi-Cloud DR

Wire `RTS 2025/532` supply-chain graphs directly into [ITS 2024/2956 RoI table `B_05.02`](/briefings/dora-article-28-its-2024-2956-register-of-information-templates), [DORA Article 30 CIF contract clauses](/briefings/dora-article-30-ict-contractual-clauses-audit-exit-strategies), and [multi-cloud concentration risk & active-active failover design](/briefings/multi-cloud-concentration-risk-active-active-failover-rto-rpo).

## Frequently asked questions

### Does DORA RTS (EU) 2025/532 require monitoring every minor 5th-tier utility vendor used by a SaaS company?

No—proportionality is built directly into RTS (EU) 2025/532! The Financial Entity must map and monitor the chain of ICT subcontractors that effectively underpin the ICT service supporting Critical or Important Functions (CIFs) (e.g., cloud IaaS/PaaS hosting, managed DBs, HSMs, core authentication, sub-processors touching financial data), not office catering or non-ICT facilities!

### Who is legally responsible for auditing Rank 2 and Rank 3 subcontractors under RTS (EU) 2025/532?

Under Article 4 of RTS 2025/532, the contract MUST obligate the direct (Rank 1) ICT third-party provider to continuously monitor all its subcontractors and ensure flow-down of security, location, and NCA/FE inspection rights—while the Financial Entity retains ultimate DORA Article 28 responsibility and verifies the direct vendor’s oversight!

### How much advance notice must an ICT vendor give before adding or replacing a material CIF subcontractor?

Under RTS (EU) 2025/532 Article 5, the contract must specify an explicit advance notice period long enough for the financial entity to conduct a thorough risk assessment of the proposed subcontractor change (typically 30 to 90 calendar days in institutional FS addenda) before the change goes live!

### How does hidden Nth-party concentration risk emerge across seemingly diversified SaaS vendors?

Suppose a broker prides itself on using 4 "independent" vendors for KYC, Trade Surveillance, CRM, and Client Portal—yet Table B_05.02 reveals that all 4 SaaS vendors host 100% of their European clusters inside us-east-1 or eu-central-1 of the exact same cloud hyperscaler (Rank 2) and use the same CDN/WAF (Rank 2)! One regional cloud or WAF outage takes down all 4 CIFs simultaneously!


## Source URLs

- https://eur-lex.europa.eu/eli/reg_del/2025/532/oj
- https://www.esma.europa.eu/sites/default/files/2024-07/JC_2024_53_Final_report_DORA_RTS_on_subcontracting.pdf
- https://eur-lex.europa.eu/eli/reg_impl/2024/2956/oj

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). DORA Subcontracting RTS (EU) 2025/532: Nth-Party ICT Supply-Chain Monitoring & Exit Triggers. RegTech Codex. https://regtechcodex.org/briefings/nth-party-ict-subcontracting-rts-critical-function-chain-risk
- Canonical article: [DORA Subcontracting RTS (EU) 2025/532: Nth-Party ICT Supply-Chain Monitoring & Exit Triggers](https://regtechcodex.org/briefings/nth-party-ict-subcontracting-rts-critical-function-chain-risk)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
