DORA Penetration Testing Requirements (2026 Guide)

Here is the position every organization bound by DORA is in. DORA has been legally binding since 17 Jan 2025 — EU regulators can now demand proof of penetration testing on your critical functions, and designated firms must pass a live-production TLPT every 3 years or face supervisory action; failing to show a conformant test puts your license and board on the line.

Most teams answer this the expensive way: they buy a single, five-figure, point-in-time manual penetration test, sweat through weeks of scheduling, then hope nothing changes until the next cycle. It always changes. This guide breaks down exactly what the DORA penetration testing requirements demand, what an assessor needs to see, and how to stay continuously in-scope — without a five-figure invoice every time your environment moves.

Two tiers. (1) Art. 24-25 (Digital operational resilience testing programme) requires all in-scope entities to run a full range of tests including vulnerability assessments and penetration testing on ICT systems supporting critical/important functions, with critical ICT systems tested at least yearly. (2) Art. 26-27 requires Threat-Led Penetration Testing (TLPT) — a live-production, intelligence-driven red-team exercise on critical/important functions — at least every 3 years for systemically important financial entities identified by competent authorities (frequency adjustable up/down by the authority). TLPT specifics are set by the Joint RTS (EBA/ESMA/EIOPA) and follow the TIBER-EU framework. In force since 17 January 2025.

Who must comply: EU financial entities under Reg. 2022/2554: credit institutions/banks, payment & e-money institutions, investment firms, insurers/reinsurers, crypto-asset service providers (MiCA), central securities depositories, central counterparties, trading venues, fund managers, and more — plus their critical ICT third-party providers (cloud, software, MSSPs). Art. 24-25 testing applies broadly (microenterprises get proportional relief); Art. 26 TLPT applies to the largest/most systemically significant entities designated by national competent authorities.

A compliant test has to hit the environment from two directions — the external internet-facing surface and the internal surface reachable from inside your network — and at both the network and application layers. The most common reason a first attempt fails review is incomplete scope: the public site was tested, but the internal APIs, admin panels, and the controls that isolate sensitive systems were not.

A traditional manual penetration test runs roughly $10,000–$30,000 and lands as a PDF that is accurate for about a day. Then your environment changes and you are out of coverage until the next cycle. That is a lot of money for a snapshot, and it leaves you blind between assessments.

Pentestas is pentesting as a service: an AI penetration testing system that runs DORA-aligned internal and external tests on your environment continuously — automatically, after every deploy — starting at $79/month. It is penetration testing with AI at the core, orchestrated by frontier models (we run penetration testing with Claude for deep reasoning and cost-controlled penetration testing with DeepSeek for high-volume passes), delivered as a B2B SaaS pentest platform that maps every finding straight to the requirement it satisfies.

The platform exercises the external surface from the internet and the internal surface through a lightweight agent inside your network, so one engagement covers both directions. It tests the application and network layers, re-tests every exploitable finding after you fix it (capturing before-and-after evidence), and — because it re-runs after every change — handles the “after significant change” obligation automatically instead of turning it into a fire drill. Every finding ships with real exploit evidence, a severity rating, and remediation steps.

Bottom line: DORA is not satisfied by one lucky PDF per cycle. It rewards continuous coverage of the whole environment, internal and external, re-tested after every change — exactly the shape of problem an AI penetration testing system is built to solve, at a fraction of the cost of being compliant for one day out of the year.