DORA: explained for the people who have to keep the systems running.

Digital Operational Resilience Act

Direct answer

The Digital Operational Resilience Act (DORA), Regulation (EU) 2022/2554, is the EU law that requires financial entities to withstand, respond to, and recover from information and communication technology (ICT) disruptions. It applies from 17 January 2025 across five areas: ICT risk management, ICT-related incident reporting, digital operational resilience testing, ICT third-party risk, and information sharing. It covers most regulated financial entities in the EU and extends supervision to the critical ICT providers they rely on.

Why DORA exists

Before DORA, operational resilience for EU financial services was governed by a patchwork of national rules and sector guidance. DORA replaces that with a single, directly applicable regulation, so a bank, an insurer, and an investment firm are held to the same baseline for surviving a technology failure or a cyber attack. The shift in mindset is the important part: DORA treats ICT disruption not as an IT problem but as a threat to financial stability, and it makes the board answerable for managing it.

The five pillars

DORA is organised around five areas. Read together they describe a full lifecycle: govern the risk, detect and report what goes wrong, prove your resilience by testing it, control the third parties you depend on, and share what you learn.

DORA: five pillars
PillarWhat it requires
ICT risk managementA documented framework, owned by the management body, covering identification, protection, detection, response, and recovery.
ICT incident management and reportingClassify incidents by severity and report major ones to the competent authority within set deadlines.
Digital operational resilience testingA testing programme, including advanced threat-led penetration testing for significant entities.
ICT third-party riskA register of ICT contractual arrangements and mandatory contractual terms, with stricter rules for critical or important functions.
Information sharingOptional participation in cyber threat information-sharing arrangements between financial entities.

Who DORA applies to

DORA covers a broad range of financial entities established in the EU, and it reaches beyond them to the technology providers they depend on. Scope is wide by design, so the safer assumption for an EU financial entity is that you are in scope until you have confirmed otherwise. A separate oversight regime applies to ICT third-party providers designated as critical, who become subject to direct supervision by a lead overseer.

Proportionality applies: smaller and less complex entities meet a simplified version of the framework, but they are not exempt.
CategoryExamples
Financial entitiesCredit institutions, payment and e-money institutions, investment firms, insurers and intermediaries, crypto-asset service providers, fund managers, and more.
ICT third-party providersCloud platforms, software and data providers, and other technology suppliers, with a dedicated oversight regime for those designated critical.

The ICT third-party register

DORA requires every financial entity to keep a register of information on all its contractual arrangements for the use of ICT services. The register has to be maintained at entity and, where relevant, group level, kept current as arrangements change, and made available to the competent authority on request. In practice it is the single hardest thing to keep honest, because it only stays accurate if it is tied to the vendor relationships it describes rather than maintained as a separate document. Acuna keeps that register live against your third-party risk management vendor inventory, which is the tightest fit between DORA and the platform.

Resilience testing and TLPT

Every in-scope entity runs a digital operational resilience testing programme sized to its risk profile. Entities identified as significant go further and perform threat-led penetration testing (TLPT) at least every three years, carried out by qualified testers against live production systems, drawing on the TIBER-EU framework. TLPT is the demanding end of the testing obligation and is scoped and validated with the competent authority.

Why the board is on the hook

DORA is explicit that the management body holds final responsibility for managing ICT risk. It must approve and oversee the ICT risk management framework, and it cannot delegate the accountability away. This is the practical reason DORA cannot live only inside the security team: the people who sign off have to be able to see that the framework is real and maintained, which is exactly what a running system, rather than a set of documents, provides.

How DORA relates to NIS2 and ISO 27001

DORA does not sit alone. Much of its ICT risk management substance overlaps with NIS2 and with ISO 27001, and its third-party requirements echo the supplier controls in both. For an entity already running one of those, the efficient path is to map the shared controls once and reuse them, rather than stand up a parallel DORA programme. That reuse is the argument for treating DORA as one framework on a multi-framework core rather than a standalone project.

When it applies

DORA entered into force in January 2023 and applies from 17 January 2025. The detailed technical standards that sit beneath it, the regulatory and implementing technical standards developed by the European Supervisory Authorities, fill in the specifics of areas such as incident classification, the register, and testing. Because those standards continue to be finalised and updated, verify the current detail of any specific technical requirement against the latest published standard before you rely on it.

How do you run DORA in Acuna GRC?

Acuna GRC keeps your ICT risk management, ICT third-party oversight and resilience evidence in one workspace, mapped to DORA and to the frameworks you already run.

DORA: common questions.

Related answers

Questions practitioners ask.

What is the difference between NIS2 and DORA?

NIS2 and DORA are two EU frameworks for cybersecurity and operational resilience that came into force around the same time and overlap heavily, but they are not interchangeable. NIS2 (Directive (EU) 2022/2555) is a cross-sector cybersecurity directive covering many industries; DORA (Regulation (EU) 2022/2554) is a finance-specific regulation for digital operational resilience. Where both could apply to the same organisation, DORA generally takes precedence for ICT risk in financial services as the more specific law, the lex specialis principle. A financial entity can therefore be in scope for both, with DORA governing its ICT risk and NIS2 relevant to the extent DORA does not cover. The two differ on instrument, scope, and specificity. NIS2 is a directive, so it is transposed into each member state's national law and its details can vary by country. DORA is a regulation, so it applies directly and uniformly across the EU without transposition. NIS2 spans many sectors; DORA is confined to financial entities and their ICT providers. DORA is also more prescriptive on ICT specifics, such as the register of information and threat-led penetration testing, than NIS2's more general risk-management measures. Where a financial entity would fall under both, DORA is treated as the more specific regime for its ICT risk, and it prevails on the matters it covers. NIS2 recognises this relationship, so the two are designed to fit together rather than duplicate. In practice, a bank manages its ICT risk under DORA and does not also apply NIS2's general measures to the same ground. For a financial entity in scope for both: determine your DORA obligations for ICT risk first, since they are the more specific and prescriptive. Then confirm what, if anything, NIS2 adds beyond DORA's coverage for your organisation, which depends partly on your member state's transposition. The efficient path is to map the shared requirements once, as most of the risk-management and supply-chain substance is common, and only maintain the genuinely distinct pieces separately.

Does DORA apply to Swiss financial institutions?

Not to a Swiss institution merely because it is Swiss. DORA (Regulation (EU) 2022/2554) applies to financial entities within its scope in the EU, so a Swiss bank, insurer or asset manager falls under FINMA, not DORA. It applies to an EU subsidiary that is itself a DORA financial entity and, in the European Commission’s view, to EU branches of third-country banks and insurers. It reaches Swiss ICT providers indirectly, through the contracts their EU financial clients must sign. Acuna GRC runs DORA and FINMA in one programme, with one business impact analysis and one provider register serving both.

How does DORA compare to FINMA Circular 2023/1?

DORA is a directly applicable EU regulation with detailed rules and technical standards for financial entities in the EU. FINMA Circular 2023/1 sets principles-based expectations for Swiss banks and securities firms, applied in proportion to their size. Both cover ICT risk, incident reporting, third-party risk, testing and the resilience of critical functions, but they differ on deadlines, the provider register and testing. In Acuna GRC both run in one programme, so a shared measure counts once for each.

What is third-party risk management (TPRM)?

Third-party risk management (TPRM) is how an organisation finds, assesses and monitors the risks that come from its suppliers, service providers and their own subcontractors: security, data protection, continuity and compliance risks. It covers the whole relationship, from due diligence before signing to periodic reassessment and exit. DORA, NIS2, the GDPR and ISO 27001 all require it in some form. In Acuna GRC, TPRM keeps one supplier register with exposure scoring, questionnaires, ratings and daily security grades.

What goes in a vendor risk assessment questionnaire?

A vendor risk assessment questionnaire asks a supplier how it protects the service, the data and the systems it touches: governance and certifications, access control, data protection and location, incident response, business continuity, its own subcontractors and its contract terms. Each question should ask for evidence where the answer matters, and the depth should follow the supplier’s risk tier. In Acuna GRC you send ready-made or your own questionnaires in English, German, French or Spanish and rate each answer.

DORA is the first time a regulator has told financial firms, in plain terms, that keeping the lights on is a board responsibility, not an IT chore.

Acuna practitioner team

The register of information is where DORA programmes quietly fall apart. It is accurate the day you build it and wrong the week a contract changes, unless it lives with the vendor relationships it describes.

Acuna practitioner team

Most of DORA is not new work if you already run ISO 27001 or NIS2. The mistake is treating it as a separate project instead of one more framework on the same controls.

Acuna practitioner team

GO DEEPER

See how DORA runs as one system.

The ICT register, controls, testing, and evidence in one place, tied to owners and reused across your other frameworks.

Built for:CISOsCompliance LeadersMSSPs