The short answer
DORA (the EU Digital Operational Resilience Act) has applied since 17 January 2025. It requires EU financial entities to manage ICT risk, report major incidents within hours, test their resilience and control their technology vendors. If you are a US or Canadian fintech or software vendor selling to EU banks, insurers or payment firms, DORA reaches you through contract clauses, so you need the controls and evidence to sign them.
The five pillars of DORA
| Pillar | What it requires |
|---|---|
| ICT risk management | A board-approved framework covering identification, protection, detection, response, recovery and learning |
| Incident management and reporting | Classify ICT incidents; report major ones to regulators on fixed timelines |
| Digital operational resilience testing | Yearly testing of critical systems; threat-led penetration testing (TLPT) every 3 years for significant firms |
| ICT third-party risk | A register of all ICT contracts, due diligence, mandatory contract clauses and exit plans |
| Information sharing | Voluntary sharing of cyber threat intelligence between firms |
The deadlines that catch teams out
For a major ICT-related incident: an initial notification within 4 hours of classifying it as major (and no later than 24 hours after detection), an intermediate report within 72 hours and a final report within one month. That only works with 24/7 detection and a pre-agreed classification process.
What DORA means for vendors
EU financial entities must include specific terms in contracts with ICT providers, including:
- A clear description of services, data locations and service levels.
- Incident support and notification duties.
- Access, inspection and audit rights for the firm and its regulator.
- Participation in the firm's resilience testing, including TLPT where relevant.
- Termination rights and exit strategies with transition support.
The European Supervisory Authorities also designate critical ICT third-party providers, mostly large cloud and data providers, for direct EU oversight.
A 90-day DORA plan
Days 1–30: map and gap
- List your critical or important functions and the ICT systems and vendors behind them.
- Map your current controls (ISO 27001, SOC 2, NIST) to DORA requirements.
- Build or update the register of ICT third-party arrangements.
Days 31–60: close the urgent gaps
- Write an incident classification guide and a 4-hour reporting runbook.
- Make sure 24/7 detection covers critical systems.
- Update vendor contracts with DORA clauses, starting with critical providers.
Days 61–90: test and prove
- Run a scenario-based resilience test and a recovery test for one critical function.
- Hold a tabletop exercise for a major incident, including the regulator report.
- Report results to the management body and plan the year's testing.
For vendors: prepare a DORA pack with your security controls, incident process, audit rights, sub-outsourcing list and exit support, so EU customers can sign quickly.
How Zuroth helps
- DORA gap assessment and register of information, mapped to your existing ISO 27001 or SOC 2 controls.
- 24/7 managed detection and response, so major incidents are classified and escalated within the 4-hour window.
- Resilience and penetration testing, including support for TLPT scoping.
- Vendor DORA packs for US and Canadian fintechs selling into the EU.
See how a payments fintech met DORA while adding agentic AI KYC in our fintech case study.
Next step: book a free 30-minute call for a DORA gap review.
Related reading
- FinTech & Financial Services
- PCI DSS scope reduction: protect card data by never touching it
- PCI DSS 4.0 guide
- Managed detection & response
- ISO 27001 certification
This article explains general practice and is not legal advice. Confirm your obligations with your counsel.
Frequently asked questions
When did DORA start to apply?
The Digital Operational Resilience Act, Regulation (EU) 2022/2554, has applied since 17 January 2025. It covers banks, payment and e-money institutions, investment firms, insurers, crypto-asset service providers and other EU financial entities, plus oversight of critical ICT third-party providers.
Does DORA apply to US or Canadian technology companies?
Not directly, unless you are an EU financial entity or designated as a critical ICT third-party provider. But if you sell software or cloud services to EU financial entities, they must put DORA clauses in your contract, so you will need to meet their security, incident, audit and exit requirements.
What are DORA's incident reporting deadlines?
For major ICT-related incidents, financial entities send an initial notification within 4 hours of classifying the incident as major and no later than 24 hours after becoming aware of it, an intermediate report within 72 hours, and a final report within one month.
What is threat-led penetration testing (TLPT) under DORA?
TLPT is advanced red-team testing based on real threat intelligence, run against live production systems. Significant financial entities chosen by their regulators must perform it at least every three years, usually following the TIBER-EU framework, with ICT providers in scope taking part.
How does DORA relate to ISO 27001 and SOC 2?
ISO 27001 and SOC 2 cover much of DORA's ICT risk management, but not all of it. DORA adds strict incident classification and reporting timelines, resilience testing, a register of ICT third-party arrangements and specific contract clauses. Map your existing controls to DORA and fill the gaps.