# DORA Art. 26 TLPT & TIBER-EU Live Red Teaming Guide (2026)

> Execute EU DORA Article 26-27 Threat-Led Penetration Testing (TLPT) aligned with TIBER-EU on live production systems, 3-year cycles, and Pooled CTPP testing.

Canonical: https://regtechcodex.org/briefings/dora-article-26-tlpt-tiber-eu-purple-teaming-3-year-cadence
Last updated: 2026-11-16T19:09:52.202Z

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

Standard staging-environment penetration tests do not satisfy DORA Article 26: systemically important banks, CCPs, trading venues, and top-tier brokers/CASPs must undergo intelligence-led TIBER-EU Red and Purple Team exercises directly against live production systems every three years.

## Key takeaways

- Under DORA Article 26 and the Joint ESA TLPT RTS, designated systemically important financial entities must execute Threat-Led Penetration Testing (TLPT) on LIVE PRODUCTION systems supporting Critical or Important Functions at least every 3 years!
- The TLPT RTS incorporates the ECB’s updated TIBER-EU framework directly: requiring an independent Threat Intelligence Provider (TIP), an accredited Red Team Tester (CREST/TIBER), a secret internal Control Team ("White Team"), and a defending Blue Team!
- Internal Red Teams face strict restrictions under Article 27: every 3rd test MUST use an external Red Team tester, AND any test using internal red-teamers STILL requires contracting an external Threat Intelligence Provider!
- After the covert Red-Team active phase concludes (>= 12 weeks), the TLPT RTS mandates a collaborative Purple-Teaming Replay Exercise before the TLPT Authority issues the formal regulatory Attestation!

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

Checkbox `OWASP Top 10` web-app pentests run against sanitized pre-production servers never catch how a nation-state `APT` pivots from a Spear-Phished developer laptop through CI/CD runners into live `SWIFT` Alliance gateways or `HSM` signing enclaves! Supervised by dedicated **TLPT Cyber Teams (`TCTs`)** inside the [European Central Bank](/regulators/european-central-bank-160), [De Nederlandsche Bank — TIBER-NL pioneer](/regulators/de-nederlandsche-bank-162), [National Bank of Belgium](/regulators/national-bank-of-belgium-371), and [Banque de France / ACPR](/regulators/autorit-de-contr-le-prudentiel-et-de-r-solution-france-166) under [EU DORA Regulation 2022/2554](/definitions/eu-dora-regulation-2022-2554) and [2026 DORA Benchmark Standards](/definitions/eu-dora-2022-2554-2026-benchmark-standard), **DORA Articles 26–27** codify **`TIBER-EU` Threat-Led Penetration Testing (`TLPT`)** into binding European law for systemic infrastructures and major trading firms such as [ICAP](/licence-holders/icap), [CMC Markets](/licence-holders/cmcmarkets), and [Coinbase](/licence-holders/coinbase). 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-Phase Lifecycle of a Compliant `DORA Article 26 / TIBER-EU` Engagement (`6–9 Months`)

Every TLPT follows a tightly milestone-gated regulatory sequence overseen directly by the national **TLPT Cyber Team (`TCT`)**:

| TLPT Phase | Duration | Active Actors | Statutory RTS Deliverables | Strict Anti-Contamination / Safety Gate |
| :--- | :--- | :--- | :--- | :--- |
| **1. Preparation & Scope** | `6–8 Weeks` | Control Team (`White`), `TCT` (`NCA`) | **TLPT Scope Specification** (`CIFs` + `Flags` to capture on live prod); procure accredited **TIP** & **Red Team (`Art. 27`)** | **Zero Blue-Team disclosure**; code-names & clean external communications |
| **2. Threat Intelligence** | `4–6 Weeks` | External **TIP** (`Threat Intel Provider`) | **Targeted Threat Intelligence Report (`TTIR`)**: OSINT recon on staff/cloud + **`>= 3` realistic APT Threat Scenarios** | Scenarios approved by `TCT` (`incl. 1 scenario without insider leg-up if feasible`) |
| **3. Active Red Teaming** | **`>= 12 Weeks`** | External **Red Team** vs Unaware **Blue Team** | **Red Team Test Plan (`RTTP`)** -> Live production phishing, initial access, lateral pivot & **Flag Capture proof** (`no data destruction!`) | **Control Team daily check-in** + Controlled ``Leg-Ups`` if stuck so full kill-chain is tested! |
| **4. Closure & Purple Team** | `6–10 Weeks` | Red + Blue + White + `TCT` | Red/Blue Reports -> **Mandatory Purple-Teaming Replay (`MITRE ATT&CK` tuning)** -> Remediation Plan -> **`TCT` Attestation (`Art. 26(7)`)** | Attestation withheld if Secrecy breached or Purple-Team skipped! |

![DORA Article 26 TIBER-EU four-phase Threat-Led Penetration Testing workflow from TIP reconnaissance to live production Red Team, Purple Team replay, and NCA Attestation](/api/figure?type=flow&title=DORA%20Art.%2026%20TIBER-EU%20Live-Production%20TLPT%20Workflow&subtitle=Coordinating%20Threat%20Intelligence%20Providers%20%28TIP%29%2C%20accredited%20Red%20Teams%2C%20secret%20White%20Control%20Teams%2C%20and%20Blue%20SOCs&steps=1.%20Scope%20%26%20CIF%20Flags%3A%3AWhite%20Team%20%2B%20NCA%20TCT%20define%20live%20production%20Crown-Jewel%20Flags%20%28e.g.%20read-only%20proof%20on%20SWIFT%2FMatching%29%7C2.%20Targeted%20APT%20Intel%3A%3AIndependent%20TIP%20maps%20firm%20dark-web%20leaks%2C%20GitHub%20exposures%20%26%20builds%20%3E%3D3%20MITRE%20ATT%26CK%20scenarios%7C3.%20%3E%3D12w%20Live%20Red%20Team%3A%3ARed%20Team%20executes%20covert%20campaign%20on%20live%20prod%3B%20White%20Team%20monitors%20safety%20%26%20grants%20Leg-Ups%7C4.%20Purple%20Replay%20%26%20Cert%3A%3AJoint%20Red%2BBlue%20replay%20tunes%20SIEM%2FEDR%20rules%20-%3E%20Submit%20Remediation%20Plan%20-%3E%20Receive%20Art.%2026%287%29%20Attestation!&metrics=TESTER%20EXPERIENCE%3A%3A%3E%3D%205%20Yrs%20Lead%3A%3AArt.%2027%20RTS%3A%20Red%20Team%20Manager%20%3E%3D5y%2C%20Staff%20%3E%3D3y%7CINSURANCE%20MANDATE%3A%3AArt.%2027%281%29%28e%29%3A%3AProfessional%20Indemnity%20Covering%20Live%20Prod%20Risk!%7CMUTUAL%20RECOGNITION%3A%3AEU-Wide%20Cert%3A%3ATCT%20Attestation%20Accepted%20Across%20All%2027%20EU%20NCAs!%7CUK%20%2F%20APAC%20ALIGNMENT%3A%3ACBEST%20%2F%20iCAST%3A%3AScope%20Joint%20Multi-Regulator%20TLPT%20Where%20Approved)

## How "Controlled Leg-Ups" Maximize Return on Investment Without Cheating

Suppose the accredited Red Team spends 4 weeks attempting external perimeter phishing and zero-day recon against your hardened Citrix/Zero-Trust edge and gets 100% blocked by your email gateway! In traditional pentesting, the report stops there—leaving **zero visibility into whether your internal East-West Kubernetes segmentation or `HSM` dual-control approvals actually work once an insider or supply-chain compromise lands inside**! Under the `DORA TLPT RTS` and `TIBER-EU`, after logging that perimeter victory for the Blue Team, the **White Control Team grants a documented "Leg-Up"** (`e.g., provisioning a standard unprivileged contractor VDI session`) so the Red Team can test internal lateral movement and detection across the remaining 8 weeks!

## Quantitative `MITRE ATT&CK` Blue-Team Detection & Dwell-Time Scoring in Purple Teaming

During Phase 4 Closure, CISOs quantify improvements across $K$ executed `MITRE ATT&CK` techniques (`before vs after` the mandatory Purple-Teaming tuning session):

```formula
Telemetry_Log_Rate = (1 / K) * sum_(k=1..K) I( Technique_Logged_In_SIEM(k) == 1 )
True_Alert_Rate = (1 / K) * sum_(k=1..K) I( Automated_SOC_Alert_Fired(k) == 1 AND Blue_Team_Escalated(k) == 1 )
Mean_Time_To_Detect = (1 / K_detected) * sum_(k in Detected) ( T_SOC_Alert(k) - T_Red_Execution(k) )

Purple_Team_Uplift = True_Alert_Rate_Post_Replay - True_Alert_Rate_Live_Red_Phase (Target Post-Replay Coverage >= 90% on Crown-Jewel Paths!)
```

![Initial access and internal lateral-movement vectors achieving Crown-Jewel Flag capture in European TIBER-EU financial red-team exercises](/api/figure?type=bars&title=Attack%20Vectors%20Reaching%20Crown-Jewel%20Flags%20in%20TIBER-EU%20Tests&subtitle=Empirical%20vulnerability%20pathways%20exploited%20during%20European%20financial-sector%20live%20TLPT%20campaigns&steps=AD%20%2F%20Kerberos%20%2F%20Cloud%20IAM%3A%3A37.9%25%20escalated%20domain%2Fcloud%20privileges%20via%20over-permissive%20service%20accounts%20%26%20ADCS%7CCI%2FCD%20%26%20Dev%20Secrets%20Sprawl%3A%3A28.6%25%20pivoted%20from%20developer%20laptops%2FConfluence%2FGitLab%20tokens%20into%20production!%7CVoice%2FTeams%20Vishing%20%26%20MFA%3A%3A19.8%25%20bypassed%20MFA%20via%20IT-helpdesk%20social%20engineering%20or%20AitM%20session%20tokens%7CSaaS%20%2F%20Vendor%20VPN%20Tunnels%3A%3A13.7%25%20traversed%20unsegmented%20third-party%20support%20jump-hosts%20into%20core%20ledgers&metrics=POOLED%20TLPT%20LEAD%3A%3A1%20Designated%20FE%3A%3AArt.%2026%284%29%20Multi-Bank%20Shared%20Cloud%20Vendor%20Test%7CART.%2025%20ANNUAL%20BASE%3A%3AAll%20Entities%3A%3AYearly%20Vuln%2C%20Source-Code%20%26%20Scenario%20Tests%20%28Non-TLPT%29%7CINDEMNITY%20%26%20ROE%3A%3ASigned%20Pre-Test%3A%3AStrict%20Rules%20of%20Engagement%20Ban%20DoS%2FData%20Wipe%7CREMEDIATION%20AUDIT%3A%3ANCA%20Tracked%3A%3AEvery%20Flag%20Path%20Tracked%20to%20Closure%20by%20Supervisor)

## Cross-Border Efficiency: Running One Synchronized `TIBER-EU + UK CBEST` Test!

Global investment banks and trading venues operating major hubs in both Frankfurt/Amsterdam (`ECB`/`DNB`/`AFM`) and London ([UK PRA](/regulators/prudential-regulation-authority-uk-173) / [UK FCA](/regulators/financial-conduct-authority-uk-121) `CBEST`) should engage both cyber authorities **6 months prior to scoping**! Because `UK CBEST`, `TIBER-EU`, `HKMA iCAST`, and `MAS AASE` share common intelligence-led roots, joint supervisory scoping frequently allows a single coordinated multi-jurisdiction campaign (`with tailored local flags`) rather than subjecting live production trading engines to overlapping covert attacks every 12 months.

## Connecting DORA TLPT to CTPP Oversight, UK Resilience & KMS Cryptography

Link `Article 26` live red-teaming directly to [Pooled CTPP cloud provider oversight](/briefings/critical-ict-third-party-providers-ctpp-lead-overseer-powers), [UK FCA PS21/3 & PRA SS2/21 impact-tolerance testing](/briefings/uk-fca-ps21-3-pra-ss2-21-impact-tolerances-vs-eu-dora-mapping), and [DORA RTS 2024/1774 cryptographic key-vault hardening](/briefings/dora-rts-ict-risk-management-encryption-cryptographic-key-life).

## Frequently asked questions

### Are all 22,000 DORA-regulated firms required to run full Article 26 TLPT live-production red-teaming?

No! While ALL non-micro entities must perform annual Article 24–25 vulnerability scans, gap analyses, and network security tests, full Article 26 TLPT applies ONLY to high-impact/systemic entities designated by their NCA/TLPT Authority based on RTS quantitative impact criteria (G-SIIs/O-SIIs, CCPs, CSDs, major trading venues, large payment systems, and systemically significant investment firms/CASPs).

### Why must DORA Article 26 TLPT run on LIVE PRODUCTION systems rather than a UAT/Staging clone?

Staging environments lack real SOC telemetry noise, live Active Directory privilege paths, production PAM/HSM policies, and human ops workflows! Under Article 26(2), testing must occur on live production systems—managed safely by a strictly NDA-bound Control Team ("White Team Lead") holding real-time emergency abort switches.

### What is "Pooled TLPT" versus "Joint TLPT" when a critical cloud or core-banking vendor is in scope?

Under DORA Article 26(3)–(4), where testing a Critical Function requires penetrating an ICT third-party provider’s production systems: a Joint TLPT involves one financial entity + its ICT vendor testing together, whereas a Pooled TLPT allows multiple financial entities sharing the same ICT vendor to pool a single coordinated TLPT led by one Designated Financial Entity!

### Who is allowed to know that a live DORA TLPT is underway inside the bank or brokerage?

Strict secrecy (Need-to-Know) is legally enforced by the TLPT Authority! ONLY the tiny internal Control Team (typically 3–5 senior risk/CISO officers outside daily SOC monitoring) knows; tipping off the Blue Team SOC analysts invalidates the entire TLPT and triggers regulatory re-testing at the firm’s expense!


## Source URLs

- https://www.ecb.europa.eu/paym/cyber-resilience/tiber-eu/html/index.en.html
- https://www.esma.europa.eu/sites/default/files/2024-07/JC_2024_29_-_Final_report_DORA_RTS_on_TLPT.pdf
- https://eur-lex.europa.eu/eli/reg/2022/2554/oj

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). DORA Article 26 Threat-Led Penetration Testing (TLPT): TIBER-EU Live Production & Purple Teaming. RegTech Codex. https://regtechcodex.org/briefings/dora-article-26-tlpt-tiber-eu-purple-teaming-3-year-cadence
- Canonical article: [DORA Article 26 Threat-Led Penetration Testing (TLPT): TIBER-EU Live Production & Purple Teaming](https://regtechcodex.org/briefings/dora-article-26-tlpt-tiber-eu-purple-teaming-3-year-cadence)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
