Regulation (EU) 2022/2554 · has applied since 17 Jan 2025
Around 22,000 financial entities in the EU fall under DORA, plus their critical IT service providers. Art. 24(6) requires annual testing of digital operational resilience. We deliver the technical part.
Source: Regulation (EU) 2022/2554, recital 3
Art. 25 DORA names a range of appropriate tests: vulnerability assessments, scenario-based tests, source code reviews, physical security reviews and penetration tests. From these, we provide evidence for six areas.
Segmentation, firewall configurations, exposed services, privileged access.
Infrastructure pentestActive Directory, privileged accounts, MFA enforcement, lateral movement.
AD pentestBanking portals, customer apps and APIs against the OWASP Top 10, with a source code review where needed.
Web app pentestAccess control for server rooms, data centres and sensitive areas.
Physical pentestPhishing, vishing and pretexting against your employees, the most common entry point.
Social engineeringRemote access, interfaces and third-party integrations. Art. 28 also requires a Register of Information.
Supply chainMandatory only for institutions the supervisor designates as significant: G-SIIs and O-SIIs, payment institutions with a payment volume of €150bn or more, insurers only from €1.5bn in gross premiums and €10bn in technical provisions.
From us you get the pentest and the technical evidence: a report with CVSS ratings, mapping to the DORA articles, a remediation plan and an executive summary.
Not from us: the regulatory classification of your company, legal advice, the register submission under Art. 28, or a certification.
The vast majority of the market covers its testing obligation entirely through Art. 25. A TLPT correctly carried out under TIBER-EU satisfies the DORA requirement at the same time.
| Criterion | Art. 25 DORA | Art. 26 DORA · TLPT |
|---|---|---|
| Target group | All DORA-obligated companies | Institutions designated as significant |
| Test type | Penetration test, vulnerability assessment | Threat-Led Penetration Testing under TIBER-EU |
| Frequency | Annual | Every 3 years |
| Effort | Manageable, plannable | Very high, specialised team |
| Our service | Fully covered | Not our offering |
DORA covers virtually the entire financial industry and its IT service providers. The full list is set out in Art. 2 DORA.
Art. 4 DORA provides for a proportionality principle: scope and intensity depend on the size, risk profile and complexity of your services. The testing scope is scaled to risk, but the obligation does not disappear.
Definition of the systems and processes to test, together with the articles that apply to your scope.
OSINT, network footprinting and planning of realistic attack paths.
Manual testing within the agreed scope, across the six areas of the testing field.
Every finding gets a CVSS rating and an article reference, for BaFin and internal audit.
Report within 5 working days, with a remediation plan and an executive summary. Walkthrough of the findings with your IT.
Art. 24(6) DORA requires annual testing, Art. 25 names the methods. We also recommend a test after significant changes to the infrastructure, after incidents and after new systems are introduced.
Yes. DORA requires financial entities to review their critical IT service providers. Conversely, a provider of critical functions can itself come under direct ESA oversight as a critical ICT third-party provider.
DORA itself names no amounts, Art. 50 leaves them to the member states. In Germany, section 56 KWG sets up to €5m for a failure to report an incident and for a TLPT not carried out, and up to €500,000 for all other breaches – with no turnover percentage. BaFin can also impose requirements.
In a free 30-minute initial call we clarify the scope. The fixed-price quote usually follows within 24 hours.