Skip to main content
Home/Services/DORA Penetration Testing
Security Testing

DORA Penetration Testing

Security testing for EU Digital Operational Resilience Act

DORA (EU 2022/2554) TIBER-EU EBA Guidelines EIOPA Guidelines
engagement log DORA Penetration Testing testing
day 01scopetargets confirmed · rules of engagement signedagreed
day 01reconattack surface mappedcomplete
day 02findingInsufficient ICT Third-Party Risk Managementcritical
day 03findingWeak Incident Detection and Classificationhigh
day 04triagereviewed and countersigned by a Lorikeet pentesterpublished
day 04delivertickets opened in your tracker201
afterretestfixes verified · included in scopeno charge
retest included human countersigned report your auditor accepts
3-4 weekstypical duration $15,000fixed scope, from 8deliverables 8methodology stages
Scope

What this engagement covers

The service

The Digital Operational Resilience Act (DORA) requires financial entities in the EU to maintain robust ICT risk management and undergo threat-led penetration testing (TLPT). Our DORA penetration testing validates your digital operational resilience and satisfies Article 26 TLPT requirements.

What we test

We assess your ICT systems, platforms, and infrastructure supporting critical financial functions. Testing covers live production systems that support critical or important functions, including payment systems, trading platforms, customer-facing portals, and third-party ICT service provider integrations.

Testing Modes

Scoping & Assessment Depth

Black Box Assessment

Zero-Knowledge

Simulates an external adversary targeting DORA Penetration Testing with no internal credentials, source code, or architecture documentation. Assesses perimeter exposure, unauthenticated attack paths, and edge resilience.

Gray Box Assessment (Recommended)

Credentialed

Simulates an authenticated user, tenant, or insider threat within DORA Penetration Testing. We evaluate role segregation, authorization boundaries, privilege escalation, and business logic flaws across user tiers.

White Box / Source-Assisted

Full-Knowledge

Conducted with direct access to architecture schematics, configuration files, and API/code documentation. Eliminates blind spots and provides exhaustive coverage of security mechanisms governing DORA Penetration Testing.

Vector Breakdown

Attack Surface & Vulnerability Vectors

Insufficient ICT Third-Party Risk Management

Rigorous testing and validation to uncover Insufficient ICT Third-Party Risk Management across your DORA Penetration Testing environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.

Weak Incident Detection and Classification

Rigorous testing and validation to uncover Weak Incident Detection and Classification across your DORA Penetration Testing environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.

Missing Recovery Time Objectives for Critical Functions

Rigorous testing and validation to uncover Missing Recovery Time Objectives for Critical Functions across your DORA Penetration Testing environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.

Inadequate ICT Change Management Controls

Rigorous testing and validation to uncover Inadequate ICT Change Management Controls across your DORA Penetration Testing environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.

Insufficient Access Controls on Critical Systems

Rigorous testing and validation to uncover Insufficient Access Controls on Critical Systems across your DORA Penetration Testing environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.

Missing ICT Concentration Risk Assessment

Rigorous testing and validation to uncover Missing ICT Concentration Risk Assessment across your DORA Penetration Testing environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.

Method

How we run it

Our DORA TLPT methodology follows the TIBER-EU framework as required by Article 26. We conduct threat intelligence-led red team testing against your critical functions, assess ICT third-party risk, validate incident reporting capabilities, and evaluate your digital operational resilience framework. Testing is coordinated with relevant financial supervisory authorities.

01

Critical function identification and scoping

Rigorous technical execution, boundary verification, and manual exploitation testing targeting critical function identification and scoping across your dora penetration testing deployment.

02

Threat intelligence gathering and scenario development

Rigorous technical execution, boundary verification, and manual exploitation testing targeting threat intelligence gathering and scenario development across your dora penetration testing deployment.

03

Red team testing of live production systems

Rigorous technical execution, boundary verification, and manual exploitation testing targeting red team testing of live production systems across your dora penetration testing deployment.

04

ICT risk management control validation

Rigorous technical execution, boundary verification, and manual exploitation testing targeting ict risk management control validation across your dora penetration testing deployment.

05

Third-party ICT concentration risk assessment

Rigorous technical execution, boundary verification, and manual exploitation testing targeting third-party ict concentration risk assessment across your dora penetration testing deployment.

06

Incident classification and reporting testing

Rigorous technical execution, boundary verification, and manual exploitation testing targeting incident classification and reporting testing across your dora penetration testing deployment.

07

Business continuity and recovery testing

Rigorous technical execution, boundary verification, and manual exploitation testing targeting business continuity and recovery testing across your dora penetration testing deployment.

08

DORA evidence documentation and supervisory coordination

Rigorous technical execution, boundary verification, and manual exploitation testing targeting dora evidence documentation and supervisory coordination across your dora penetration testing deployment.

Deliverables

What you receive

Findings land in your tracker as you go, not only in a PDF at the end. Retest is in scope, not a change order.

  • DORA-compliant TLPT report
  • TIBER-EU aligned assessment results
  • ICT risk management validation
  • Critical function resilience assessment
  • Third-party ICT risk evaluation
  • Incident reporting capability assessment
  • Digital operational resilience gap analysis
  • Retest validation report
Typical results

What we usually find

The issues this engagement surfaces most often. Yours will differ, but this is the shape of it.

Insufficient ICT Third-Party Risk Management Weak Incident Detection and Classification Missing Recovery Time Objectives for Critical Functions Inadequate ICT Change Management Controls Insufficient Access Controls on Critical Systems Missing ICT Concentration Risk Assessment Incomplete Incident Reporting Procedures Gaps in Digital Operational Resilience Testing
Fit

Who this is for

Banks and Credit Institutions
Investment Firms and Funds
Insurance and Reinsurance Companies
Payment Service Providers
Crypto-Asset Service Providers
Critical ICT Third-Party Service Providers

Auditor-Ready Compliance Crosswalk

Framework Control Section Testing Evidence & Report Deliverable
SOC 2 Type II CC4.1, CC7.1 Technical evaluation and testing evidence fulfilling vulnerability management and access control testing requirements for DORA Penetration Testing.
ISO/IEC 27001:2022 Control A.8.8 Management of technical vulnerabilities through objective, independent assessment of DORA Penetration Testing.
PCI DSS v4.0 Requirement 11.4 Penetration testing evidence and remediation verification satisfying annual audit validation requirements.
Standards this supports

Findings are mapped to DORA (EU 2022/2554), TIBER-EU, EBA Guidelines, EIOPA Guidelines, so the report drops into an audit package rather than needing to be translated first. If you need the readiness work behind one of those, that is a separate engagement.

FAQ

Frequently Asked Questions

Direct answers on scoping, methodology, compliance validation, and deliverables.

Our DORA Penetration Testing service combines deep manual testing with automated verification. We cover: DORA-compliant TLPT report, TIBER-EU aligned assessment results, ICT risk management validation, Critical function resilience assessment, Third-party ICT risk evaluation. Every engagement includes reproducible proof-of-concept exploits, developer-ready remediation guidance, and a free retest.

Yes. Findings are directly mapped to DORA (EU 2022/2554), TIBER-EU, EBA Guidelines, EIOPA Guidelines control requirements. The resulting report is auditor-ready and formatted for immediate submission to SOC 2 CPAs, PCI QSAs, and enterprise vendor risk assessment teams.

Yes. Every Lorikeet Security engagement includes free retesting within 30 to 60 days to validate that your remediation patches successfully resolve the identified vulnerabilities before your final report is issued.

Typical active testing turnaround is 3-4 weeks, with critical findings reported immediately via your Talon portal so your engineering team can begin remediation without waiting for the final PDF.

Pricing starts from $15,000. We scope the engagement in one call based on your environment's surface area, user roles, and complexity, providing a transparent, fixed-price quote with no hidden change orders.

Next

Scope it in one call

Tell us what is in scope and we come back with a fixed price and a start date. No discovery-call maze, no hourly estimate that moves.

Lory waving

Hi, I'm Lory! Need help finding the right service? Click to chat!