Regulation (EU) 2022/2554 · Article 26

DORA TLPT. Threat-Led Penetration Testing, explained.

The independent reference for designated EU financial entities preparing for their first TLPT cycle. What the regulation requires, what the phases involve, and what good preparation looks like. Anchored to the primary sources.

DORA applied
17 January 2025
TLPT RTS applicable
8 July 2025
First TLPT cycle by
17 January 2028

A single binding standard for ICT resilience across the EU financial sector.

The Digital Operational Resilience Act, Regulation (EU) 2022/2554, replaced a patchwork of national rules and sector-specific guidance with a uniform standard for how regulated EU financial entities prepare for, withstand, respond to, and recover from ICT disruptions. It applies directly across all 27 Member States with no national transposition.

DORA covers 21 categories of financial entities, from credit institutions and payment institutions to crypto-asset service providers, insurers, fund managers, and audit firms. It also reaches their ICT third-party providers. It is built on five pillars. The third pillar, Digital Operational Resilience Testing, is where Threat-Led Penetration Testing lives.

What makes a Threat-Led Penetration Test different.

Real threat intelligence drives the scenarios. Testing runs on live production systems for at least 12 weeks. The Blue Team does not know it is happening. Once it ends, mandatory purple teaming converts the test into measurable defensive uplift, and the competent authority issues a formal attestation.

Read Article 26 and 27 in full

The board-ready version, in four sentences.

DORA Article 26 requires designated EU financial entities to conduct a Threat-Led Penetration Test (a structured adversary simulation using real threat intelligence against live production systems) at least every three years. The first cycle must be completed by 17 January 2028.

Findings are summarised to the competent authority; a formal attestation enables mutual recognition across EU jurisdictions. Non-compliance is subject to administrative penalties set by Member State law, with turnover-based ceilings ranging from 5% (Spain) to 10% (Sweden).

Need the operational detail behind this summary? Read the Article 26 breakdown →

Seven phases. Typically 12 to 18 months from notification to attestation.

From the moment your competent authority issues the notification letter, you are on a regulated clock. Open any phase for the detail and operational artefacts.

Engagement timeline

From notification letter to attestation

Setup & closure Threat intelligence Red-team workstream Purple teaming (mandatory)
Total engagement is typically 12 to 18 months from notification to attestation, longer for complex Tier 1 institutions. Open any phase for the full detail. Phases 05 and 06 run in parallel: the red team report is due within 4 weeks of active testing ending, while purple teaming and the blue team report complete within 10 weeks.

The questions CISOs ask first.

Are we required to conduct TLPT, or just basic testing?
TLPT (Article 26) does not apply to all DORA-regulated entities. It applies to a designated subset identified by the competent authority based on systemic importance, ICT risk profile and financial stability considerations. Basic testing (Article 25) applies to all in-scope entities. Entities with the profile of G-SIIs, O-SIIs, SSM significant institutions, or large payment / e-money institutions should assume they are likely to be designated. Run the 60-second scope check →
Can we use our existing TIBER-EU test results to satisfy DORA?
Only with explicit NCA confirmation, and only if your test meets the current RTS. The DORA TLPT RTS introduced several changes from the pre-2025 TIBER-EU framework: purple teaming became mandatory where it was previously only encouraged; scenarios must now address the full CIA triad (Confidentiality, Integrity, Availability); the function scope term moved from "Critical Function" to "Critical or Important Function" per Article 3(22); and delivery timelines that were guidance-based are now RTS obligations. A pre-2025 TIBER-EU test will not automatically satisfy DORA TLPT by adding a purple team exercise after the fact. Take the question to your NCA directly with your prior test documentation.
What is the difference between a TLPT and a standard penetration test?
A standard penetration test typically follows a predefined scope, uses generic attack techniques, and is conducted without regard to which actual threat actors target the entity. TLPT begins with real threat intelligence specific to the entity, uses the TTPs of genuine adversaries relevant to the sector and threat profile, operates covertly on live production systems, runs for a minimum of 12 weeks of active testing, and concludes with mandatory purple teaming. It is significantly more complex, more costly, and more operationally demanding than a standard penetration test.