DORA for Fintechs: What the EU’s Operational Resilience Rules Require
Guide
- Topic: What DORA (Regulation (EU) 2022/2554) requires of EU financial firms and their ICT providers
- Applies since: January 17, 2025
- Five pillars: ICT risk management, incident reporting, resilience testing, third-party risk and information sharing
- Incident clock: Initial notification for a major incident within four hours of classification, an intermediate report in 72 hours and a final report within a month
- Takeaway: Supervisors want evidence that controls work, not only documents that describe them
If your fintech serves customers in the EU, the Digital Operational Resilience Act (DORA) probably applies to you, or to the financial institutions you supply. It sets common rules for how firms manage technology risk, report incidents, test their systems and oversee outside technology providers. This guide explains what it asks for and how to prepare.
Who is in scope
- Banks, payment institutions, e-money institutions and investment firms.
- Crowdfunding service providers and crypto-asset service providers.
- Insurers, asset managers and other regulated financial entities.
- ICT third-party providers, directly if designated as critical, and indirectly through their contracts with financial firms.
Rules scale with size and risk, so smaller firms face lighter requirements in some areas. Confirm how proportionality applies to you with your national supervisor.
The five pillars
| Pillar | What it requires | What to prepare |
|---|---|---|
| 1. ICT risk management | A documented framework approved and overseen by the management body, with asset inventories, protection, detection, response and recovery | Board-approved policy, a current asset map and tested backups |
| 2. Incident management and reporting (Articles 17 to 23) | Classify incidents and report major ones on fixed clocks: an initial notification within four hours of classifying an incident as major (and no later than 24 hours after becoming aware), an intermediate report within 72 hours and a final report within one month | A classification playbook, named owners and a tested reporting route to your supervisor |
| 3. Resilience testing (Articles 24 to 27) | Regular testing of critical systems, and threat-led penetration testing at least every three years for firms the authorities designate | A test calendar, evidence of fixes and scope covering key providers |
| 4. Third-party risk (Articles 28 to 44) | A register of information on all ICT contracts, mandatory contract terms such as audit rights and exit plans, and management of concentration risk | A complete, current register and renegotiated contracts |
| 5. Information sharing | Voluntary arrangements to exchange cyber threat information | A route to join trusted industry groups |
What has already happened
- January 17, 2025: DORA began to apply.
- April 30, 2025: the first registers of information were due to supervisors.
- November 18, 2025: the European supervisory authorities published their first list of 19 designated critical ICT third-party providers, which includes major cloud, software and telecom providers, according to Nemko and Motadata. These providers now face direct EU oversight.
- 2026: compliance advisers report that supervisors are moving from reviewing paperwork to asking for proof of how controls work.
Where firms struggle
- The register of information. Advisers describe it as the place where DORA work most often stalls: it must list every ICT arrangement, including subcontractors, in a prescribed format.
- Contracts. Older supplier agreements often lack audit rights, incident duties or exit plans.
- Incident classification. Firms need clear criteria that staff can apply under pressure.
- Testing evidence. It is not enough to schedule tests; supervisors expect results and follow-up.
A practical checklist for a fintech
- Confirm your status: which entity is in scope, and whether you are a financial firm or a supplier to one.
- Map your ICT services and the providers behind each critical function.
- Build or update the register of information and assign an owner.
- Review contracts against the required terms, starting with critical providers.
- Write and rehearse an incident playbook that includes the four-hour, 72-hour and one-month steps.
- Schedule resilience tests and keep evidence of findings and fixes.
- Brief the board. The management body is responsible for ICT risk.
- Prepare an exit plan for each critical provider.
A twelve-month implementation plan (suggested)
This is a practical way to sequence the work. Adjust it to your size, your supervisor’s expectations and what you already have in place.
| Period | Focus | Outputs |
|---|---|---|
| Months 1 to 2 | Scope and gap analysis | A list of in-scope entities and services, plus a gap assessment against each pillar |
| Months 3 to 4 | Third-party risk | A complete register of information, a ranking of critical providers and a contract review plan |
| Months 5 to 6 | Incident management | A classification method, reporting templates and named incident roles |
| Months 7 to 9 | Testing | A test calendar, completed tests and a log of fixes |
| Months 10 to 12 | Governance and assurance | Board reporting, an internal audit review and updates to policies |
Classifying an incident
Reporting depends on knowing which incidents are major. DORA’s classification approach looks at several factors, and you should document how you will apply each one:
- Clients affected, including how many customers and how important they are.
- Duration and downtime of the service.
- Geographic spread, such as the number of countries affected.
- Data losses, in confidentiality, integrity or availability.
- Criticality of the services affected.
- Economic impact, such as direct costs and losses.
A written, tested method helps teams make a fast and consistent decision when the four-hour clock is running.
Contract terms to look for with ICT providers
Contracts with providers of ICT services typically need to cover the following, with stronger terms for services that support critical or important functions:
- A clear description of the services and where they are delivered and data is processed.
- Data protection, availability, integrity and confidentiality commitments.
- Access, recovery and return of data if the provider fails or the contract ends.
- Service levels with precise performance targets.
- Assistance with incidents and cooperation with supervisors.
- Termination rights and notice periods.
- For critical or important functions: audit and access rights, participation in your testing and a documented exit strategy.
Common mistakes
- Treating DORA as an IT project when the management body is responsible for ICT risk.
- Building the register of information once and not updating it as contracts change.
- Writing an incident policy without rehearsing it.
- Overlooking subcontractors in the supply chain.
- Assuming a cloud provider’s certifications satisfy your own obligations.
Frequently asked questions
Does DORA apply to fintechs outside the EU?
It applies directly to financial entities authorised in the EU. A non-EU technology provider that serves EU financial firms usually meets DORA through the contract terms those firms must require, and may face direct oversight if designated as critical.
Is DORA the same as NIS2?
No. DORA is sector-specific law for financial entities. One compliance guide notes that firms should still assess any other NIS2 obligations and national law separately.
Does every firm need threat-led penetration testing?
No. It applies to entities identified by their supervisors, generally at least every three years. Other firms still need to run regular basic testing.
Who is directly supervised among providers?
Providers designated as critical. The first 19 were named on November 18, 2025, and they face direct EU oversight.
The Funding Journal view
DORA is less about buying a new tool than about knowing your technology supply chain and proving you can respond when something breaks. Fintechs that can produce a clean register, a rehearsed incident process and test evidence on request will be easier for banks and regulators to work with, and for many, that is a sales advantage as well as a compliance duty.
Sources and further reading
- Nemko: Digital Operational Resilience Act
- Motadata: DORA compliance guide
- FortifyData: DORA explained
- CSSF: ICT and cyber risk for DORA entities
- EITT: DORA for the financial sector
This article is general information, not financial, legal or tax advice. See our disclaimer. Facts last checked October 26, 2026; rules and company details change, so confirm current terms before you act.
Published by The Funding Journal Editorial. Practical, sourced writing on fintech, crowdfunding, investment platforms, SaaS and AI, and the stories of founders who raised capital.
