- 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.
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.
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:
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:
- 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.
- 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.
- 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.
- 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.
- 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.