Regulatory Technical Standard
DORA TLPT RTS: Regulatory Technical Standards on Threat-Led Penetration Testing
This regulatory technical standard sets how threat-led penetration testingA framework that mimics the tactics, techniques and procedures of real attackers to test an organisation's live critical functions. DORA requires certain financial entities to carry out TLPT regularly. under Article 26 of DORADigital Operational Resilience Act is carried out, in line with the TIBER-EU framework: which financial entities must test, how tests are prepared, run and closed, the use of internal testers, and remediation and attestation.
- 3 years maximum interval between tests
- 12 weeks minimum active red teamA group authorised to imitate an attacker in order to test an organisation's security. The team uses realistic attack methods to show what an adversary could achieve and how well the organisation detects and responds. The results help defenders improve their controls and response. In financial-sector testing, the team's activities must follow the agreed test scope and safeguards. testing
- EUR 150 billion payment volume threshold
What Is DORA TLPT RTS?
It makes advanced, intelligence-led red teamA group authorised to imitate an attacker in order to test an organisation's security. The team uses realistic attack methods to show what an adversary could achieve and how well the organisation detects and responds. The results help defenders improve their controls and response. In financial-sector testing, the team's activities must follow the agreed test scope and safeguards. testing of the most important financial entities consistent across the EU and ensures that tests are mutually recognised between authorities.
Under Article 26 of DORADigital Operational Resilience Act, financial entities identified by their TLPTThreat-Led Penetration Testing authority carry out TLPTThreat-Led Penetration Testing at least every three years; the authority can ask for more or less frequent testing. Each test covers several or all critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. and is carried out on live production systems, with external testers at least every third test.
The RTSRegulatory Technical Standards sets the organisation (a control team and TLPTThreat-Led Penetration Testing test managers, Articles 3 and 4), risk management for the test and for pooled or joint tests (Articles 5 and 6), and the selection of threat intelligenceInformation about cyber threats that has been collected, combined and analysed to help people make security decisions. It adds context to facts about attackers, their methods or signs of an attack, helping an organisation judge what matters to its systems. It can guide monitoring, incident response, information sharing and realistic attack simulations. providers and testers (Article 7). The test has three phases: preparation, with scope approved by the TLPTThreat-Led Penetration Testing authority (Article 9); testing, with targeted threat intelligenceInformation about cyber threats that has been collected, combined and analysed to help people make security decisions. It adds context to facts about attackers, their methods or signs of an attack, helping an organisation judge what matters to its systems. It can guide monitoring, incident response, information sharing and realistic attack simulations. and a red teamA group authorised to imitate an attacker in order to test an organisation's security. The team uses realistic attack methods to show what an adversary could achieve and how well the organisation detects and responds. The results help defenders improve their controls and response. In financial-sector testing, the team's activities must follow the agreed test scope and safeguards. test whose active phase lasts at least 12 weeks (Articles 10 and 11); and closure (Article 12).
In the closure phase the testers deliver a red teamA group authorised to imitate an attacker in order to test an organisation's security. The team uses realistic attack methods to show what an adversary could achieve and how well the organisation detects and responds. The results help defenders improve their controls and response. In financial-sector testing, the team's activities must follow the agreed test scope and safeguards. test report within 4 weeks of the end of active testing, and the blue teamThe people responsible for defending an organisation's systems against cyberattacks, including detecting suspicious activity and responding to it. In a TIBER-EU test, the blue team includes relevant staff and service providers outside the small control team and is initially unaware of the simulated attack. Afterwards, it records its observations and works with the simulated attackers to identify improvements. Hong Kong's iCAST framework also uses blue team requirements to assess detection, response and recovery. report, replay and purple teaming follow within 10 weeks. The entity then submits a test summary report within 8 weeks for approval, and a remediation plan within 8 weeks (Article 13). The TLPTThreat-Led Penetration Testing authority issues an attestation (Article 14) that other authorities recognise (Article 16). Article 15 sets the conditions for using internal testers.
- Full title
- Commission Delegated Regulation (EU) 2025/1190 Specifying the Criteria Used for Identifying Financial Entities Required to Perform Threat-Led Penetration Testing, the Requirements Governing Internal Testers, the Testing Methodology and the Cooperation Needed for TLPT (DORA TLPT RTS)
- Official reference
- Commission Delegated Regulation (EU) 2025/1190
- Type
- Regulatory technical standard
- Issued by
- European Commission
- Adopted
- 13 February 2025
- Effective from
- 8 July 2025
- Status
- In force and applicable
- Applies to
- Financial entities
- Supplements
- Digital Operational Resilience Act (DORA)
Official text
Verified by
Ahmet Ucar
Principal Consultant (CISSPCertified Information Systems Security Professional, CISMCertified Information Security Manager, CISACertified Information Systems Auditor, CIPP/ECertified Information Privacy Professional/Europe)
Last updated 4 November 2026
Does It Apply to You?
Tools that work with this act, free and without signing up.
What DORA TLPT RTS Requires
Article 2
Entities required to perform TLPT
The criteria the TLPTThreat-Led Penetration Testing authority uses to decide which entities must test, based on impact, systemic character and ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. profile, and the listed entities it must require to test unless that assessment shows a test is not justified.
Articles 3 and 4
Test managers and organisation
Test managers at the TLPTThreat-Led Penetration Testing authority oversee each test. The entity appoints a control team lead and sets up the arrangements that keep the test confidential.
Articles 5 and 6
Risk management for TLPT
Managing the risks of a test, including pooled and joint tests.
Articles 7 and 15
Selection of testers
The requirements for threat intelligenceInformation about cyber threats that has been collected, combined and analysed to help people make security decisions. It adds context to facts about attackers, their methods or signs of an attack, helping an organisation judge what matters to its systems. It can guide monitoring, incident response, information sharing and realistic attack simulations. providers and external testers, and the arrangements an entity must have to use internal testers.
Show All 7 Requirements
Articles 9 to 12
Preparation, testing and closure
Scope and preparation, threat intelligenceInformation about cyber threats that has been collected, combined and analysed to help people make security decisions. It adds context to facts about attackers, their methods or signs of an attack, helping an organisation judge what matters to its systems. It can guide monitoring, incident response, information sharing and realistic attack simulations., the red teamA group authorised to imitate an attacker in order to test an organisation's security. The team uses realistic attack methods to show what an adversary could achieve and how well the organisation detects and responds. The results help defenders improve their controls and response. In financial-sector testing, the team's activities must follow the agreed test scope and safeguards. test on live production systems, and closure with a purple teaming exercise.
Articles 13 and 14
Remediation and attestation
A remediation plan for the findings, and the attestation of the test by the TLPTThreat-Led Penetration Testing authority.
Article 16
Cooperation and mutual recognition
How TLPTThreat-Led Penetration Testing authorities cooperate and recognise tests across Member States.
More Requirements in Related Documents
- DORAthe act it supplements · 7 requirements
| Covered entities | Kind | Article | Where defined |
|---|---|---|---|
| Identified financial entities | Legal status | Perform TLPTThreat-Led Penetration Testing at least every three years and remediate findings. | |
| TLPTThreat-Led Penetration Testing authorities | Legal status | Identify entities, oversee tests and issue attestations. | |
| Threat intelligenceInformation about cyber threats that has been collected, combined and analysed to help people make security decisions. It adds context to facts about attackers, their methods or signs of an attack, helping an organisation judge what matters to its systems. It can guide monitoring, incident response, information sharing and realistic attack simulations. providers and testers | Legal status | External or, under conditions, internal teams that run the test. | |
| Credit InstitutionsCredit institutions | Legal status | ||
| Electronic Money InstitutionsElectronic money institutions | Legal status | ||
| Insurance and Reinsurance UndertakingsInsurance and reinsurance undertakings | Legal status | ||
| Payment InstitutionsPayment institutions | Legal status |
Where it applies: Financial entities authorised or registered in the EU, including ICTInformation and Communication Technology systems and third-party providers in scope of the test, wherever located.
Local representative: Not required.
Financial entities that TLPTThreat-Led Penetration Testing authorities identify on the basis of impact, systemic and ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. factors (Article 2). Unless the assessment shows otherwise, these include credit institutions that are G-SIIs or O-SIIs or part of them; payment institutionsPayment Institution and electronic money institutionsElectronic Money Institution with more than EUR 150 billion in payment transactions in each of the two preceding years, or for e-moneyElectronic Money institutions more than EUR 40 billion of outstanding e-moneyElectronic Money; central securities depositories; central counterparties; trading venues with the largest national market share or more than 5% EU market share; and insurers and reinsurers above EUR 1.5 billion gross written premiums and EUR 10 billion technical provisions, with further thresholds.
MicroenterprisesMicroenterprise Under DORA and the entities of Article 16(1) of DORADigital Operational Resilience Act are not required to perform TLPTThreat-Led Penetration Testing. Groups sharing ICTInformation and Communication Technology systems can perform a joint test.
Every 3 years
Threat-led penetration test Article 26(1) DORA
When: At least every three years, or as the TLPTThreat-Led Penetration Testing authority decides.
TLPTThreat-Led Penetration Testing on live production systems supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions., with the scope approved by the TLPTThreat-Led Penetration Testing authority.
TLPT test summary report Article 12(7)
When: Within 8 weeks of the TLPTThreat-Led Penetration Testing authority confirming the red and blue teamThe people responsible for defending an organisation's systems against cyberattacks, including detecting suspicious activity and responding to it. In a TIBER-EU test, the blue team includes relevant staff and service providers outside the small control team and is initially unaware of the simulated attack. Afterwards, it records its observations and works with the simulated attackers to identify improvements. Hong Kong's iCAST framework also uses blue team requirements to assess detection, response and recovery. reports are complete.
Summary of the relevant findings, as set out in Annex VII, for approval.
TLPT remediation plan Article 13
When: Within 8 weeks of the notification under Article 12(7).
For each finding: weaknesses, remediation measures with priority, root cause analysisA structured investigation into the underlying causes of a problem or incident, rather than only its visible effects. For an IT incident, it examines how technical failures, working practices or other conditions combined to cause the disruption. The findings help an organisation choose corrective measures that address those causes and reduce the chance of recurrence., responsible staff and risks.
There are no penalties in this regulation itself. It supplements DORADigital Operational Resilience Act, under which Member States lay down administrative penalties and remedial measures for breaches (Article 50) and may lay down criminal penalties (Article 52); competent authorities apply them.
-
DORA
-
DORA ICT Risk Management RTS: Regulatory Technical Standards on ICT Risk Management
- JC 2024 34: Major ICT Incident Costs and Losses Guidelines
-
DORA Third-Party Policy RTS: Regulatory Technical Standards on the ICT Third-Party Policy
-
DORA Subcontracting RTS: RTS on Subcontracting of ICT Services
-
DORA Register of Information ITS: Implementing Technical Standards on the Register of Information
-
DORA Incident Classification RTS: Regulatory Technical Standards on the Classification of ICT-Related Incidents
-
DORA Incident Reporting RTS: Regulatory Technical Standards on Major Incident Reports
- DORA Incident Reporting ITS: Implementing Technical Standards on Incident Reporting Forms and Templates
-
DORA Critical Provider Criteria: Criteria for Designating Critical ICT Third-Party Service Providers
-
DORA Oversight Conditions RTS: Regulatory Technical Standards on the Conduct of Oversight Activities
Each mapping links requirements one by one, with how closely they match and what the other one adds. The full tables are available as spreadsheets.
Latest DORA TLPT RTS Updates
DORA TLPT RTS Milestones Since 2025
- In force
- Published in the Official Journal
- Adopted by the Commission
How We Help With DORA TLPT RTS
Start with an assessment, or have us run the work.
Questions
DORA TLPT RTS FAQ: Common Questions Answered
How often must TLPT be performed under DORA?
At least every three years for financial entities identified by their TLPTThreat-Led Penetration Testing authority. The authority can require more or less frequent testing based on the entity’s risk profile.
How does DORA TLPT relate to TIBER-EU?
The RTSRegulatory Technical Standards is based on and aligned with the TIBER-EU framework. TIBER-EU tests can be used for DORADigital Operational Resilience Act TLPTThreat-Led Penetration Testing where they meet the RTSRegulatory Technical Standards, and authorities recognise attestations from each other.
Can internal testers be used?
Yes, under the conditions of Article 15 of the RTSRegulatory Technical Standards and Article 27 of DORADigital Operational Resilience Act, but external testers must be used at least every third test, and credit institutions that are significant under the SSMSingle Supervisory Mechanism must use external testers.
Preparing for DORA RTS on TLPT?
Thirty minutes with a GRC+ consultant: we look at your scope, the requirements that apply and where to start.