Skip to content

Regulatory Compliance

DORA is far more than a single test

DORA has applied to the financial sector since 17 January 2025. We bring order to what the regulator actually enforces: ICT risk management, the register of provider contracts, incident reporting and a resilience testing programme - without reducing the whole regulation to one advanced penetration test.

Last updated: October 2026

30 minutes with a consultant who runs projects like yours. We agree the scope and tell you what the price depends on.

Industries
5
Years in the market
8+

Team certifications

  • CISSP - Certified Information Systems Security Professional
  • CISA - Certified Information Systems Auditor
  • CISM - Certified Information Security Manager
  • OSCP - Offensive Security Certified Professional
  • OSWE - Offensive Security Web Expert
  • GICSP - Global Industrial Cyber Security Professional
  • GRID - GIAC Response and Industrial Defense
  • IEC 62443 - ISA/IEC 62443 Cybersecurity Expert
  • BSCP - Burp Suite Certified Practitioner

Regulatory Compliance

  • Applicability assessment
  • ICT risk management framework
  • Register of Information

DORA (Regulation EU 2022/2554) has applied directly since 17 January 2025 and covers almost the entire financial sector - banks, investment firms, payment and e-money institutions, insurers, fund managers, crypto-asset service providers and critical ICT third-party providers. In practice most of the work lies not in spectacular testing but in day-to-day rigour: an ICT risk management framework with management-body accountability, a register of information on every ICT provider contract (submitted to the national supervisor), classification and reporting of major incidents, and the contractual clauses and exit strategies for services supporting critical functions. Threat-led penetration testing (TLPT) is only part of one of DORA's five pillars - resilience testing - and applies solely to entities identified by the authority - for most institutions the priority is getting governance, the provider register and reporting in order. We help separate what applies to everyone from what applies to the few, and bring the organisation to compliance without alarm over deadlines that do not concern it.

Scope of the service

  • Applicability assessment - which DORA provisions apply, whether the entity qualifies for the simplified framework under Article 16 or the microenterprise reliefs, and how the Article 4 proportionality principle shapes the remaining requirements

  • ICT risk management framework - policies, roles, management-body accountability, mapping of critical functions, business continuity and recovery plans

  • Register of Information - building and maintaining the register of all ICT provider contracts in the format required by the ESA technical standards, ready for submission to the supervisor

  • ICT third-party risk management - provider due diligence, contractual clauses required by DORA, concentration analysis and exit strategies for services supporting critical functions

  • Incident classification and reporting - procedures aligned with DORA deadlines (initial, intermediate and final report) and materiality thresholds

  • Digital resilience testing programme - vulnerability tests, scans, penetration tests and an assessment of whether the entity is subject to mandatory TLPT

  • TLPT readiness - for designated entities: preparation for threat-led testing per the TIBER-EU methodology, within the correct multi-year horizon

  • Remediation plan with prioritisation, timeline and mapping to specific DORA articles and the supplementary technical standards (RTS/ITS)

How we work, step by step

01

Applicability assessment

We establish which DORA pillars and provisions apply, whether the entity falls under the simplified framework of Article 16, and which services support critical functions.

02

Gap analysis

We compare the current state with DORA requirements across the five pillars - ICT risk governance, incidents, testing, provider risk, information sharing - and prioritise the gaps.

03

Register and governance

We build the register of information on ICT providers and put the risk management framework in order: policies, roles, board accountability, contractual clauses.

04

Incidents and testing

We implement incident classification and reporting procedures and a resilience testing programme fit for the profile - including whether the entity is subject to TLPT.

05

Remediation plan and support

We deliver a prioritised compliance plan mapped to DORA articles and support implementation at a pace matched to the real deadlines.

What you get from the DORA gap analysis

The first stage ends with a document that shows what applies to your institution and what needs to be done. It has these parts:

Applicability assessment
It shows which DORA pillars and provisions apply to the entity, whether it falls under the simplified framework of Article 16, and which services support critical or important functions.
Gap map across the five pillars
It compares the current state with the requirements for ICT risk management, incidents, testing, third-party risk and information sharing, and gives each gap a priority.
Register of Information
It assesses the register of ICT third-party contracts against the format required by the ESA technical standards and lists the gaps to close before submission to the competent authority.
Incidents
It assesses the procedures for classifying and reporting major incidents against the three reports: initial, intermediate and final.
Resilience testing and TLPT
It proposes a testing programme matched to the institution's profile and assesses whether it is subject to TLPT. Most often it is not, so this part is usually short.
Remediation plan
It sets out the actions over time and maps them to DORA articles and the RTS/ITS technical standards.

Who we serve

We've worked with national energy grid operators, systemically important banks, industrial automation manufacturers, renewable energy operators, and US DoD contractors.

Technology partnerships

Not sure this service fits your situation? Describe your environment and deadline in a few lines and we will propose a scope. We reply within one business day.

Frequently asked questions

Who does DORA apply to?

Almost the entire EU financial sector: banks, investment firms, payment and e-money institutions, insurers and reinsurers, fund managers and asset managers, crypto-asset service providers, credit rating agencies, crowdfunding service providers and critical ICT third-party providers designated by the European supervisory authorities. The proportionality principle (Article 4) applies to every entity, while the simplified ICT risk management framework (Article 16) is available only to listed categories, such as small and non-interconnected investment firms, exempted payment and e-money institutions and small IORPs.

When does DORA apply?

The DORA Regulation (EU 2022/2554) has applied directly since 17 January 2025. As an EU regulation it requires no transposition into national law - it applies directly. It is complemented by regulatory and implementing technical standards (RTS/ITS), drafted by the European supervisory authorities (EBA, EIOPA, ESMA) and adopted by the European Commission as delegated and implementing regulations.

What are DORA's five pillars?

1) ICT risk management - governance framework and management-body accountability. 2) Management and reporting of ICT-related incidents to the supervisor. 3) Digital operational resilience testing - from vulnerability scans to penetration tests, and TLPT for selected entities. 4) ICT third-party risk management, including the register of information on contracts. 5) Information sharing on cyber threats (voluntary).

What is the register of information on ICT providers?

The Register of Information is a maintained and updated register of all contractual arrangements for the use of ICT services provided by third-party providers, in a standardised format defined by the ESA technical standards. Financial entities submit it to the supervisor. It is one of DORA's most tangible and pressing obligations - and a frequent point at which organisations discover they lack a full map of their own provider dependencies.

Does DORA mean mandatory TLPT for our bank?

Most often, no. Threat-led penetration testing (TLPT) applies only to entities designated by the supervisor based on their systemic importance and risk profile, and the testing cycle spans several years. For the vast majority of institutions the priority is putting ICT risk management, the provider register and incident reporting in order. We help determine whether the entity is genuinely subject to TLPT and - if so - prepare within the correct horizon, without treating it as a fire.

How does DORA relate to NIS2 and national cybersecurity law?

DORA is sector-specific regulation (lex specialis) for financial entities - for the area it governs it takes precedence over the general NIS2 requirements. A financial entity may, however, be subject to both regimes in different respects. In the audit we map the requirements so as not to duplicate work between DORA, NIS2 and internal standards.

What are DORA's incident reporting requirements?

Major ICT-related incidents must be reported to the competent supervisor in three stages: initial report, intermediate report and final report - within deadlines and materiality thresholds defined by the technical standards. We help implement incident classification procedures and prepare the organisation to meet these deadlines under the pressure of a real event.

Where should DORA implementation start?

With an applicability assessment and a gap analysis. In practice we start with the register of information on ICT third-party providers and the ICT risk management framework, because these obligations apply to every financial entity.

How do you price DORA compliance support?

The price is the estimated number of days times the daily rate, broken down by stage: applicability assessment, gap analysis, Register of Information, incident procedures and testing programme. An institution that qualifies for the simplified framework under Article 16 has fewer obligations, so it needs fewer stages and days. For others the scope depends on size, complexity and the number of critical or important functions. We agree the scope on a free call.

We'll discuss scope, methodology, and timeline.

Free consultation, no strings attached.

Book a call