Dora Operational Ict Compliance
DORA Article 26 Threat-Led Penetration Testing (TLPT): TIBER-EU Live Production & Purple Teaming
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.

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, De Nederlandsche Bank — TIBER-NL pioneer, National Bank of Belgium, and Banque de France / ACPR under EU DORA Regulation 2022/2554 and 2026 DORA Benchmark Standards, 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, CMC Markets, and Coinbase. Review our EU DORA Compliance Master Guide 2026 inside the DORA operational compliance hub.
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! |
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):
- TrueAlertRate = (1 / K) * sum(k=1..K) I( AutomatedSOCAlertFired(k) == 1 AND BlueTeamEscalated(k) == 1 )
- MeanTimeToDetect = (1 / Kdetected) * sum(k in Detected) ( TSOCAlert(k) - TRed_Execution(k) )
- PurpleTeamUplift = TrueAlertRatePostReplay - TrueAlertRateLiveRed_Phase (Target Post-Replay Coverage >= 90% on Crown-Jewel Paths!)
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 / UK FCA 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, UK FCA PS21/3 & PRA SS2/21 impact-tolerance testing, and DORA RTS 2024/1774 cryptographic key-vault hardening.
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!
Publication record
- Published
- 13 November 2026
- Updated
- 16 November 2026
- Author
- Victoria Ashworth, LL.M, CAMS
- Review
- Review not recorded
- Automated fact check
- Passed in the stored pipeline record
- Source URLs
- 3 recorded
AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.
Academic & Institutional Attribution
Cite This Research & Embed Live Data Card
Standard academic & institutional research paper citation format.
Victoria Ashworth, LL.M, CAMS. (2026, November 16). 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-cadenceRelated Dora Operational Ict Compliance & Institutional Briefings
Explore Dora Operational Ict Compliance Hub (20) →Dora Operational Ict Compliance
EU DORA Regulation (EU) 2022/2554 Master Guide: ICT Risk, 4h/72h Reporting, RoI & TLPT (2026)Dora Operational Ict Compliance
DORA Critical ICT Third-Party Providers (CTPPs): Designation Math, Lead Overseers & 1% Daily FinesDora Operational Ict Compliance
DORA Article 30 ICT Contractual Clauses: Two-Tier SaaS Repapering, Audit Rights & Exit PlansDora Operational Ict Compliance
UK Operational Resilience (FCA PS21/3 & PRA SS2/21) vs EU DORA: Cross-Mapping Dual ProgramsDora Operational Ict Compliance
US SEC Regulation S-P Amendments (2024–2026) & Form 8-K Item 1.05: 4-Day & 30-Day Cyber ClocksDora Operational Ict Compliance
DORA vs NIS2 Directive (Article 1(2) Lex Specialis): Dual-Scope Financial Groups & CSIRT SyncDora Operational Ict Compliance
DORA Subcontracting RTS (EU) 2025/532: Nth-Party ICT Supply-Chain Monitoring & Exit TriggersDora Operational Ict Compliance
AI & LLM Governance in Trade Surveillance & AML: EU AI Act (2024/1689), DORA & SR 11-7Regulatory and Market Glossary
Tron and Tether bring in Chainalysis after T3 crime unit foldsRegulatory Compliance
Thailand proposes $148K daily cap on stablecoin deposits and withdrawalscybersecurity
NEWS: French bank Credit Mutuel Arkea says €100m missing after cyberattack - AML IntelligenceRegulatory Compliance
After 900 IT Incidents, BaFin Expands Cybersecurity Oversight, Sets 2030 Encryption Target - Finance Magnates
RegTech Codex Data, Benchmarks & Contributor Records
CC BY 4.0 Open Data
Open Institutional Datasets (CSV / JSON) →
Download desk-compiled quantitative series & schemas.
2026 Reference Matrix
2026 Institutional Benchmarks & Thresholds →
Statutory capital, clearing, margin & rate conventions.
Editorial Records
Authors & Review Records →
View named contributors where those records are available.
Complete Index
Master Research & Dossier Archive →
Browse all published briefings by topic pillar & date.
