What is threat-led penetration testing (TLPT) under DORA?
Direct answer
Threat-led penetration testing (TLPT) is the advanced form of resilience testing that DORA requires of financial entities identified as significant. Unlike routine vulnerability scanning or standard penetration tests, TLPT simulates the tactics, techniques, and procedures of real threat actors against an entity's live production systems, covering the critical or important functions that support its business.
It is performed by testers who meet the requirements of Article 27(1) of DORA, scoped and validated with the competent authority, and carried out at least every three years. Internal testers are allowed only under the conditions of Article 27(2), an entity that uses them contracts external testers every three tests, and credit institutions classified as significant under Article 6(4) of Regulation (EU) No 1024/2013 use external testers only (Article 26(8)). TLPT draws on the TIBER-EU framework for threat-led testing. TLPT sits at the demanding end of DORA's testing pillar. Most in-scope entities run a general resilience testing programme; significant entities additionally run TLPT, because the regulation treats their disruption as a bigger systemic risk. A standard penetration test checks whether known weaknesses can be exploited. TLPT is intelligence-led: it starts from a picture of the threats that realistically target your kind of entity, then tests whether your live systems and your people would withstand those specific adversary behaviours. It runs against production, not a test environment, which is what makes it a genuine test of operational resilience rather than of a lab setup. TLPT is a structured engagement: scoping the critical or important functions to be tested, developing threat intelligence, running the red-team test against live systems, and producing findings that feed remediation. Tester qualification, scoping, and the outcome are handled with the competent authority.
Which financial entities have to carry out TLPT?
Only those their authority identifies. Article 26(8) of DORA has competent authorities identify the financial entities required to perform TLPT, based on impact-related factors, possible financial stability concerns and the entity’s ICT risk profile and maturity. Microenterprises and the entities under the simplified regime of Article 16(1) are outside the obligation. An identified entity tests at least every 3 years, and the authority can ask it to test more or less often (Article 26(1)).
Commission Delegated Regulation (EU) 2025/1190 sets the identification criteria. Under its Article 2(2), TLPT authorities require the following entities to perform TLPT, unless the assessment shows that their impact, financial stability concerns or ICT risk profile do not justify it:
- credit institutions identified as global or other systemically important institutions (G-SIIs or O-SIIs), or that are part of one;
- payment institutions and electronic money institutions above the payment volume or outstanding electronic money thresholds set in the regulation;
- central securities depositories and central counterparties;
- trading venues with an electronic trading system that meet the market share criteria;
- insurance and reinsurance undertakings that meet the criteria set in the regulation.
Authorities assess other financial entities against the same criteria and can identify them as well.
How does a TLPT run, from notification to attestation?
Delegated Regulation (EU) 2025/1190 splits the test into a preparation phase, a testing phase (threat intelligence, then the red team test) and a closure phase:
- Preparation. Within 3 months of the TLPT authority’s notification, the entity submits a project charter, the contact details of its control team lead, the intended use of internal or external testers, the communication channels and a code name (Article 9). A control team runs the test, and information about it stays on a need-to-know basis (Article 4). The entity selects the critical or important functions in scope, and the authority validates the scope (Article 26(2) of DORA).
- Threat intelligence. The threat intelligence provider analyses generic and targeted threat intelligence on the entity and proposes scenarios that target each critical or important function in scope (Article 10).
- Red team test. The testers write a red team test plan, approved by the control team and the TLPT authority, then attack live production systems. The active red team testing phase lasts at least 12 weeks (Article 11(5)).
- Closure. The blue team, the defenders, is told only after the active phase ends. The testers deliver their report within 4 weeks, and the blue team report, the replay of the attack and a purple teaming exercise follow within 10 weeks of the end of the active phase (Article 12). The entity then submits the summary of findings and the remediation plans, each with a root cause analysis per finding, within 8 weeks (Articles 12(7) and 13).
The authority finally issues an attestation that the test met the requirements, which allows mutual recognition between authorities (Article 26(7) of DORA).
Who can perform the test, and what about ICT providers?
Article 27(1) of DORA allows only testers who are of the highest suitability and reputability, have specific expertise in threat intelligence, penetration testing and red team testing, are certified by an accreditation body in a member state or adhere to formal codes of conduct or ethical frameworks, provide independent assurance or an audit report on how they manage the risks of TLPT, and hold professional indemnity insurance covering misconduct and negligence.
Internal testers are possible under conditions: the competent authority (or the single public authority designated under Article 26(9) and (10)) approves their use, it verifies that the entity has sufficient dedicated resources and that conflicts of interest are avoided throughout the design and execution of the test, and the threat intelligence provider is external to the entity (Article 27(2)). An entity using internal testers contracts external testers every three tests, and credit institutions classified as significant in accordance with Article 6(4) of Regulation (EU) No 1024/2013 use only external testers that meet Article 27(1), points (a) to (e) (Article 26(8)).
When ICT third-party providers support functions in scope, they are part of the test, and the entity keeps full responsibility for compliance (Article 26(3)). Where a provider’s participation could harm its other clients, the provider can contract an external tester directly for a pooled test covering several financial entities (Article 26(4)). Contracts for ICT services supporting critical or important functions must oblige the provider to take part in and fully cooperate with the entity’s TLPT (Article 30(3)(d)); see the DORA register of information.
How Acuna GRC handles it
- Solution
DORA
Keep one ICT third-party register, map critical processes with RTO and RPO, find single points of failure and follow ICT incidents in one place.
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
- Service
CISO as a service
A virtual CISO from Swiss experts: risk reviews, BIA and policy reviews run in Acuna GRC all year, while you review and decide. Your audit stays independent.
Sources
- Regulation (EU) 2022/2554 (DORA), Articles 3(17), 16, 26, 27 and 30(3)
- Commission Delegated Regulation (EU) 2025/1190 of 13 February 2025, regulatory technical standards on threat-led penetration testing
This page explains the rules in general terms and is not legal advice.
Frequently asked
Is DORA TLPT the same as TIBER-EU?
They are closely linked. Article 26(11) of DORA required the European Supervisory Authorities, in agreement with the ECB, to draft the TLPT technical standards in accordance with the TIBER-EU framework. For DORA purposes, the binding rules are those of Delegated Regulation (EU) 2025/1190.
Does the TLPT attestation shift responsibility to the authority?
No. The attestation confirms that the test was performed in accordance with the requirements, so that other authorities can recognise it. Article 26(7) states that the financial entity remains fully responsible for the impact of the tests. The wider testing programme that every in-scope entity runs is covered in operational resilience testing under DORA.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

