logo svg
logo

November 23, 2025

Updated: November 5, 2026

DORA Penetration Testing: TLPT Requirements for EU Firms

Understanding DORA’s mandatory penetration testing and threat-led TLPT rules.

Mohammed Khalil

Mohammed Khalil

Featured Image

The Digital Operational Resilience Act DORA EU Regulation 2022/2554 took effect on January 17, 2025. In simple terms, DORA forces banks, insurers, payment firms, crypto providers, and other financial institutions to prove they can survive serious cyberattacks. That means hacking yourself on a schedule set by regulators. Specifically, all in scope firms must run a risk-based resilience testing program, in which penetration tests, authorized attacks on their own systems, are one of the listed test types. For the most critical entities, DORA even mandates Threat-Led Penetration Testing TLPT a full scale, intelligence driven red team exercise. In this article, we explain what DORA penetration testing is, why it matters today, how TLPT under DORA differs from regular testing and from the ECB’s voluntary TIBER EU framework, and practical tips for compliance.

TIBER-EU is a related European framework for threat-intelligence-based testing; see TIBER-EU Framework Explained.

What Is DORA Penetration Testing?

DORA penetration testing is a controlled, simulated cyberattack performed as one test type within the ICT resilience testing program that in-scope financial entities must maintain. Article 25 lists it alongside vulnerability scans, network security assessments, source code reviews and scenario-based tests, and DORA adds Threat-Led Penetration Testing (TLPT) as an advanced option for top-tier firms.

“A holographic regulatory timeline unfolds, showing key DORA requirements as glowing data panels animate into view. Icons representing risk mapping and control testing pulse at the bottom as highlights glide across a dark, futuristic financial-system grid.”

Under DORA, penetration testing becomes one of the test types in a legally required testing program, not just a best practice. Essentially, any financial institution within DORA’s scope must maintain an ICT resilience testing program. This means regularly finding and fixing security holes before attackers do. The tests must cover all systems that support critical or important functions a DORA defined term. A penetration test or pen test is a controlled simulated cyberattack on an organization’s computer systems, applications or network to uncover vulnerabilities. If you’re new to this, see our guide What is Penetration Testing? for an overview. For DORA compliance, the stakes are higher: regulators expect financial firms to apply multiple test methods, vulnerability scans, code reviews, network tests, etc. on a risk based schedule, then promptly remediate any findings. Article 24(6) requires appropriate tests on all ICT systems and applications supporting critical or important functions at least yearly. Article 25 lists penetration testing as one possible test alongside vulnerability scans, network security assessments, source code reviews and scenario-based tests, so the mix should follow your risk assessment.

Crucially, DORA introduces Threat-Led Penetration Testing TLPT as an advanced option for top tier firms. TLPT is like a realistic red teaming exercise: experts use the latest threat intelligence to mimic the tactics of real cybercriminals or nation state hackers against live production systems. Unlike a one off automated scan, a TLPT is a multi week campaign involving reconnaissance, simulated attacks, and even a purple team debrief where attackers and defenders collaborate to learn lessons. The goal is to test not just technical controls but the firm’s entire ability to detect, respond, and recover under fire. In short, DORA’s definition of penetration testing now ranges from standard app/network pentests to these full scale TLPT scenarios.

Why DORA Penetration Testing Matters in 2025

Cyber threats against financial institutions are intensifying. Ransomware, supply chain attacks, and sophisticated data breaches can shake market confidence and disrupt economies. Regulators realized that simply holding capital reserves traditional risk buffers isn’t enough. DORA closes a gap: it forces firms to prove they can fend off and survive cyber incidents. Dutch financial firms can compare penetration testing companies in the Netherlands.

For 2025 and beyond, this is urgent. Recent surveys show industry is reacting: Pentera's 2023 State of Pentesting survey found 92% of CISOs increased their overall security budgets in 2023, and 85% upped their annual pentesting spend. Under DORA, resilience testing is a legal obligation: a risk-based testing program for in-scope firms, with penetration testing as one of the listed test types, and TLPT for designated entities.

Meeting these mandates is not just red tape, it delivers real benefits. Penetration testing for compliance under DORA uncovers hidden weaknesses in systems handling transactions or customer data, so you can fix them proactively. It boosts customer confidence, as you can demonstrate you are finding and fixing issues on an ongoing basis in fact, proof of regular testing may be requested by cyber insurers. It also satisfies upcoming audits: many firms will need to show regulators test records, reports, and remediation logs.

Global cybersecurity spending is surging. Gartner forecasted that companies will spend $188.3B on risk & security in 2023 an 11.3% increase year over year. For readers curious about the overall security landscape, see our article on top cybersecurity statistics. The bottom line: for 2025, neglecting pentesting isn’t an option if you want to stay in business or avoid fines.

DORA Penetration Testing Requirements

DORA defines a two tier testing regime:

In short, all DORA firms do regular annual tests, the big ones also do intense red team TLPT triennially. Think of basic pentesting vs TLPT like routine checkups vs a full body stress test. Table 1 below compares their key features:

DORA TLPT vs Traditional Penetration Testing

FeatureThreat-Led Penetration Test DORA TLPTTraditional Penetration Test
ScopeCritical functions on live production systems incl. 3rd party providers.Specific applications/networks, often lower risk or dev systems.
FrequencyAt least once every 3 years or per regulator.Risk based, often annual or per release. No strict cycle mandated.
TeamExternal testers by default; internal testers only with authority approval and never for significant credit institutions; threat intelligence provider must be external when internal testers are used. Must use a Control Team for oversight.Can be internal or external teams doing focused tests e.g., app pentest, network pentest.
MethodologyFull red team engagement: reconnaissance, stealth exploitation, with threat intelligence scenarios. Mandatory purple teaming debrief.Usually limited duration attacks on known vulnerabilities, no mandated threat intelligence or purple teaming.
ObjectivesDemonstrate end-to-end compromise of critical functions under controlled conditions: penetrate deeper and reach target flags without real disruption.Find known vulnerabilities SQLi, XSS, misconfigs. Less emphasis on stealth persistence.
ReportingFormal multi phase reports to both firm and regulator. Must include root causes, impact, and mandatory fix plans.Detailed technical report for IT, often without third party oversight.

The distinctions above highlight why TLPT is considered more rigorous. It borrows the established TIBER EU framework, updated under DORA. In fact, the EU’s ECB has aligned TIBER EU with DORA requirements, so doing a DORA TLPT using the TIBER methodology will generally check all the compliance boxes. The difference is legal status: TLPT is an obligation for entities designated under DORA Article 26 and the TLPT RTS, Commission Delegated Regulation (EU) 2025/1190 (adopted 13 February 2025, in force since 8 July 2025), while TIBER-EU is a voluntary Eurosystem framework. The ECB's February 2025 TIBER-EU update aligned it with that RTS, so a TIBER-EU test can serve as a DORA TLPT where the national authority uses the framework.

TLPT = advanced, intelligence driven red teaming on steroids. For more on differences between TLPT and a routine test, see our comparison Penetration Testing Methodology guide.

How to Conduct DORA Compliant Penetration Tests Step by Step

“A futuristic step-by-step timeline animates across a holographic grid. Each stage of DORA’s TLPT cycle appears as glowing panels, with icons for risk scoping and attack simulation pulsing beneath. Data streams and neon paths connect each step, showing the progression from scoping to validation.”

Use this practical checklist when evaluating professional penetration testing services for DORA:

  1. Identify Critical Functions and Scope: Start by mapping your business’s critical or important functions also called CIFs. These are services or processes whose outage would hurt customers or the market e.g. payment clearing, trading engine, core banking. Then list all IT systems and third party services that support those functions; a maintained third-party risk management inventory makes this list much faster to build. This scoping document is crucial for any DORA test. For a TLPT, the competent authority must validate the scope.
  2. Select Qualified Testers: Engage a specialized team. For annual tests, any independent security firm or in-house team properly segregated will do. For TLPT, DORA strongly prefers external certified professionals. For example, CREST accredited providers are recognized for high standards. CREST itself emphasizes that TLPT must use highly qualified, reputable professionals. Ensure your testers have experience with financial sector systems and threat intel. If you do use internal red teams, remember DORA’s rules: you need authority approval and an external threat intelligence provider, every third TLPT must use external testers, and significant credit institutions may only use external testers.
  3. Gather Threat Intelligence: Before launching the attack phase, collect threat intel specific to your sector. Identify likely adversaries, cybercrime groups, hacktivists, nation states targeting finance and their TTPs tactics/techniques. This informs your attack scenarios. DORA TLPT is threat led, meaning your simulated attack should mirror a real world campaign. For example, if phishing based breaches have spiked in your industry, ensure your red team tests phishing vectors. See our OAuth security best practices and SSRF attack examples content for common exploit patterns.
  4. Define Rules of Engagement: Document clear rules. Agree what methods are allowed or off limits e.g. you might exclude physically destructive attacks. Decide on safe kill switches conditions to immediately stop the test like detection of unintended outages. Ensure business continuity: schedule the test to limit any impact on critical processes or use realistic test accounts. DORA expects firms to manage TLPT risk, so demonstrating strong planning per TIBER EU guidance is key.
  5. Execute the Test: Run the pentest or red team campaign. For routine tests, this might be a weekend vulnerability assessment or a multi day network pentest. For TLPT, the red team will stealthily attempt to breach your defenses over an active testing phase of at least 12 weeks, using multiple vectors phishing, malware, zero days, etc.. Meanwhile, your blue team incident responders, SOC, operate normally, they should be unaware of the timeline, so their detection skills are truly tested. Document all findings: vulnerabilities exploited, data accessed, time taken to detect, etc.
  6. Purple Teaming and Debrief: After the red team phase, conduct a purple team session. DORA now requires that the red attackers and blue defenders compare notes in a structured review. This helps your teams learn: the red team can explain how they breached defenses, and the blue team can validate detection coverage. Capture all lessons learned, update monitoring tools and response playbooks accordingly.
  7. Report and Remediate: Produce reports tailored to different audiences. A technical report should detail every finding with evidence, risk level, CVSS scores, etc., and a concise executive summary should highlight key vulnerabilities and impacts. Critically, DORA requires that you not just report issues but fix them. Prioritize high/critical findings and apply patches or controls swiftly. Track fixes to completion and keep evidence. Regulators will likely ask for proof that vulnerabilities have been overcome.
  8. Respond to Supervisors: If you’re TLPT designated, submit a summary of the test to your regulator as required by Article 26(6); the authority then issues an attestation under Article 26(7). This doesn’t have to reveal every secret detail, but it should note any show stopping gaps and how you will address them. Establishing trust with supervisors e.g. the ECB for major banks or national agencies for insurers is important. They may also coordinate joint examination teams for cross border firms to avoid duplicate tests.

Throughout this process, keep internal teams informed sans spoilers and document everything. Use tools or platforms if you have them some organizations use a continuous testing framework or a continuous penetration testing platform to track and automate parts of this cycle. And always align with recognized standards: following TIBER EU protocols ensures you cover DORA’s criteria.

Don’t treat DORA tests like checkboxes. For example, performing a quick scan and claiming we did a pentest won’t cut it. It’s not just about ticking the annual box, you need quality and follow through. Don’t ignore non technical controls either incident response processes and staff readiness count as part of resilience. And crucially, avoid using the same internal team without oversight. Make sure whoever tests is independent of the systems under test.

Key Benefits of DORA Aligned Testing

DORA represents a paradigm shift: resilience testing is no longer optional in EU finance, it’s mandatory. Financial firms must build a continuous testing culture from automated vulnerability checks to full scale threat led war games to meet DORA’s requirements. Those who do will not only stay in the regulator’s good graces, but significantly beef up their cyber defenses. Ready to strengthen your defenses? Today’s threats demand action. If you need to validate your security posture, uncover hidden risks in your critical systems, or simply ensure compliance, DeepStrike can help. Our team of expert practitioners provides clear, actionable guidance to protect your business.

Explore our Penetration Testing Services to see how we can uncover vulnerabilities before attackers do. Drop us a line,we’re always ready to dive in.

About the Author

Mohammed Khalil is a Cybersecurity Architect at DeepStrike, specializing in advanced penetration testing and offensive security operations. With certifications including CISSP, OSCP, and OSWE, he has led numerous red team engagements, focusing on cloud security, application vulnerabilities, and adversary emulation. His work involves dissecting complex attack chains and developing resilient defense strategies for clients in the finance, healthcare, and technology sectors.

FAQs

It’s the EU mandated requirement for financial firms to run structured cybersecurity tests. This includes, at least yearly, appropriate tests of every ICT system and application supporting critical or important functions, with penetration testing one of the listed test types, plus advanced red team exercises TLPT for designated institutions. The goal is to prove the firm can withstand serious cyberattacks under DORA rules.

DORA specifies categories of large or systemically important entities, big banks, insurers, trading venues, etc.. If your regulator identifies you as in scope for TLPT, you have to run a threat led red team test at least once every 3 years. Other in-scope firms must still run, at least yearly, appropriate tests of every ICT system and application supporting critical or important functions, with penetration testing one of the listed test types, but aren’t required to do TLPT unless designated. Micro enterprises very small firms are largely exempt.

TLPT is more intense and realistic. A typical pentest might be a 1- 2 week test of one app or network segment. In a DORA TLPT, the active red-team phase alone must last at least 12 weeks under the TLPT RTS, Delegated Regulation (EU) 2025/1190, and preparation, threat intelligence, closure, replay and purple teaming add to that, so plan for the full cycle to take considerably longer. A TLPT targets the firm’s crown jewels e.g. payment engines, uses real attacker TTPs, and includes mandatory purple teaming at the end. Also, TLPT results are reported to regulators, whereas regular pentest reports normally stay internal. Entities that also sit on the SWIFT network run a separate cycle again; see SWIFT CSP penetration testing for how that scope differs.

Sometimes. Internal testers need approval from the TLPT authority, verified resources and no conflicts of interest, and the threat intelligence provider must still be external. Firms using internal testers must contract external testers every third test. Significant credit institutions under ECB supervision must use external testers only. In practice, using a certified external red team e.g. CREST certified is the safer choice.

For the regular testing program, at least yearly, appropriate tests of every ICT system and application supporting critical or important functions; penetration testing is one of the listed test types. For TLPT if applicable, at least once every 3 years. Remember, additional testing is recommended after major changes or incidents.

Regulators can impose fines, force remediation, or take corrective actions. Since DORA is already in effect, supervisory exams will check testing records. Member States set administrative penalties and remedial measures for DORA breaches, and supervisors can require corrective action.

Look for experience in financial cyber resilience and DORA/TIBER frameworks. CREST accreditation or OSCP/OSWE certifications are good signs. Ensure the firm offers the required TLPT components: threat intelligence, red teaming, purple teaming, and solid remediation reporting. See our Penetration Testing Services for how DeepStrike approaches DORA TLPT. Financial entities sourcing a tester inside the EU can also review the penetration testing companies in Belgium or, in the Baltics, the penetration testing companies in Lithuania.

background
Let's hack you before real hackers do

Stay secure with DeepStrike penetration testing services. Reach out for a quote or customized technical proposal today

Contact Us