Guide Compliance Financial Services

DORA gap analysis: how to assess and remediate compliance

The EU Digital Operational Resilience Act (DORA) has applied since 17 January 2025 and sets requirements for ICT risk management, incident reporting, resilience testing and ICT third-party risk. For a FinTech in scope, assessing compliance starts with identifying which obligations apply to your regulatory category, comparing existing controls against them and documenting the gaps. This guide sets out a practical method for organising evidence, assessing risk and building a remediation plan.

3 June 2026
Updated 19 November 2026
7 min read
Key takeaways
  • DORA has applied since 17 January 2025 to 20 categories of financial entity. There is no general grace period.
  • The five pillars are an explanatory model. Information sharing (Article 45) is voluntary and should not be scored as non-compliance.
  • An incident is major only if it affects critical services and either involves malicious unauthorised access that may lead to data losses or meets at least two other materiality thresholds.
  • Keep three moments apart: becoming aware of an incident, classifying it as major and reporting it. Under Article 5 of Delegated Regulation (EU) 2025/301, the initial notification goes through the channel set by the competent authority within 4 hours of classification and, as a rule, no later than 24 hours after becoming aware.
  • Testing is proportionate: systems supporting critical or important functions are tested at least yearly, and TLPT applies only to entities identified by their competent authority.

Start with a gap analysis, not a programme

Your instinct may be to start DORA compliance by drafting policies. That approach puts outputs before inputs. A gap analysis comes first: it identifies where you are exposed, which your policies cannot tell you.

DORA's requirements are often described as five pillars: ICT risk management, incident reporting, resilience testing, ICT third-party risk and information sharing. Treat this as an explanatory model rather than a legal structure. The obligations sit in specific articles of Regulation (EU) 2022/2554 and in the regulatory and implementing technical standards (RTS and ITS) adopted under it. The gap analysis maps what exists, compares it with the requirements that apply to your category of entity, and produces a prioritised list of actions. Without it, you build programmes around assumptions and discover the gaps when a supervisor asks.

20
categories of financial entity in Article 2(1), including payment institutions and crypto-asset service providers
4h
for the initial notification after classifying an incident as major, and as a rule no later than 24 hours after becoming aware of it (Delegated Regulation (EU) 2025/301, Article 5)
6.5%
of registers analysed in the ESAs' 2024 voluntary dry run passed all 116 data quality checks

Before the analysis: confirm your scope

DORA applies to financial entities in the 20 categories listed in Article 2(1), points (a) to (t). These include credit institutions, payment institutions, account information service providers, electronic money institutions, investment firms, crypto-asset service providers, insurance and reinsurance undertakings and crowdfunding service providers, among others. ICT third-party service providers appear separately in point (u). They are not financial entities, and those designated as critical fall under a separate oversight framework (Articles 31 to 44).

Scope is not always obvious for FinTechs. A company providing a payment initiation service is a payment institution. A company embedding insurance products into a platform may be an insurance intermediary, depending on its size and activities. A company that holds crypto-assets in custody for clients is a crypto-asset service provider under MiCA, which brings it within DORA's scope. Confirm your classification with your legal counsel before running a gap analysis. The classification determines which obligations apply and at what level of detail.

Two different mechanisms reduce the burden, and they are often confused. The proportionality principle in Article 4 applies to every financial entity: requirements are implemented in line with its size, overall risk profile and the nature, scale and complexity of its services, activities and operations. The simplified ICT risk management framework in Article 16 replaces Articles 5 to 15 only for the entity types listed there: small and non-interconnected investment firms, exempted payment institutions, exempted electronic money institutions, small institutions for occupational retirement provision and certain institutions exempted under Directive 2013/36/EU. Being a microenterprise (fewer than 10 persons and an annual turnover and/or balance sheet total of no more than EUR 2 million, Article 3(60)) brings some specific relief, for example a periodic rather than annual review of the framework, but it does not by itself place you under Article 16.

ICT suppliers and critical third-party providers

If you supply ICT services to EU financial entities, you are not a DORA financial entity yourself. Your clients remain responsible for managing their ICT third-party risk and will flow requirements down to you through contracts under Article 30. Only providers designated as critical by the European Supervisory Authorities (ESAs) are overseen directly, through a Lead Overseer; the ESAs published the first list of designated providers in November 2025. A supplier based outside the EU, for example in the UK or Brazil, should therefore expect contract clauses, audit rights and information requests from its financial-sector clients rather than direct supervision, unless it is designated.

How to record each gap

Record every requirement in the same format so findings can be compared, prioritised and evidenced. A simple register with these fields works well:

1
DORA reference
Article and paragraph, plus the relevant RTS or ITS (for example Delegated Regulation (EU) 2024/1772 for incident classification).
2
Requirement
The obligation in plain language.
3
Applicability
Applies, applies in simplified form, or not applicable, with the reason (entity category, Article 16, microenterprise status).
4
Expected evidence
What a supervisor would expect to see: a policy, register, test report, contract clause or management body minutes.
5
Current evidence
What exists today, with document references.
6
Assessment
Compliant, partially compliant, non-compliant or not applicable.
7
Gap
The specific difference between the requirement and the current state.
8
Risk
The operational and regulatory impact if the gap stays open.
9
Owner and deadline
A named person and a target completion date.

Assess both design and operation. A control can be adequately designed without operating effectively: a backup policy may meet the requirement on paper, but a failed restore test shows the control does not work in practice. Record these as separate findings.

Our companion page, DORA gap assessment by pillar, sets out what to check in each area: the ICT risk management framework, incident classification and reporting deadlines, resilience testing and TLPT, ICT third-party risk and the Register of Information, and information sharing.


Building the remediation roadmap

A gap analysis produces findings across all five areas. Rather than following a fixed order, rate each gap on a few factors:

  • Operational risk. How likely the gap is to cause or worsen a disruption.
  • Criticality. Whether it affects critical or important functions.
  • Regulatory exposure. Whether a deadline or reporting obligation depends on it.
  • Compensating controls. What reduces the risk while the gap stays open.
  • Effort and lead time. How long the fix takes and whether it depends on third parties.

Then run the main workstreams in parallel rather than one after another:

  1. Time-bound obligations. Incident classification and reporting must work now, because a major incident can happen at any time. Put the classification step, reporting templates and named roles in place early.
  2. The most critical technical gaps. A failed restore test or untested systems supporting critical functions carry operational risk that documentation will not fix. Address them alongside the documentation work, not after it.
  3. Third-party contracts and the RoI. Renegotiating contracts and collecting register data depend on suppliers and take lead time you do not control, so start them early.
  4. Documenting existing practice. Writing down controls that already work is quick and closes design gaps, but it only counts if those controls also operate effectively.
  5. Testing aligned to your cycle. If your annual testing is due in three months, plan the testing remediation to feed into that cycle rather than scheduling a standalone assessment.

Give each action an owner, a target completion date and a status, and report progress to the management body. Under Article 5 the management body bears ultimate responsibility for managing ICT risk, so it should see the gap analysis results and oversee the remediation plan. How formally it approves individual documents depends on your governance arrangements.

DORA has applied since 17 January 2025 and there is no general grace period. Supervisory priorities differ between authorities and sectors, but an entity that can show a completed gap analysis, an evidence-based assessment and a remediation plan with owners and target dates is in a stronger position than one that cannot.

Frequently asked questions

Who does DORA apply to?

DORA (Regulation (EU) 2022/2554) applies to the 20 categories of financial entity listed in Article 2(1), including credit institutions, payment and electronic money institutions, investment firms, insurance undertakings and crypto-asset service providers. It has applied since 17 January 2025. ICT third-party service providers are not financial entities: they are affected through their contracts with financial entities, and those designated as critical are overseen directly by the ESAs. The proportionality principle in Article 4 applies to every financial entity, while the simplified ICT risk management framework in Article 16 is limited to the entity types listed there.

What are the five pillars of DORA?

DORA is commonly described through five pillars: ICT risk management (Articles 5 to 16), ICT-related incident management and reporting (Articles 17 to 23), digital operational resilience testing (Articles 24 to 27), ICT third-party risk management (Articles 28 to 44) and information sharing (Article 45). This is an explanatory model rather than a legal structure. The first four contain mandatory requirements; information sharing is voluntary and should not be scored as non-compliance in a gap analysis.

Does every financial entity under DORA need to do Threat-Led Penetration Testing?

No. TLPT under Article 26 applies only to financial entities identified by their competent authority. Those entities carry out TLPT at least every three years, unless the authority sets a different frequency, following Delegated Regulation (EU) 2025/1190, which is aligned with TIBER-EU. Other financial entities, apart from microenterprises, still need a proportionate testing programme under Article 24, in which ICT systems and applications supporting critical or important functions are tested at least yearly.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

DORA Gap Analysis

Know exactly where your DORA gaps are

We run structured DORA gap analyses across all five pillars and deliver a prioritised, risk-based remediation plan your management body can oversee and your team can act on.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.