Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
DORA, the EU Digital Operational Resilience Act, is a regulation that has required banks, insurers, investment firms, and their critical ICT suppliers to manage, test, and report on digital resilience since January 2025.

What Is DORA?
DORA, the Digital Operational Resilience Act, is Regulation (EU) 2022/2554. It sets a single, binding rulebook for how financial entities in the European Union manage ICT risk, respond to and report incidents, test their resilience, and control the technology suppliers they depend on. It entered into force on 16 January 2023 and has applied since 17 January 2025.
Before DORA, ICT requirements for finance were scattered across guidelines from different supervisors. Because it is a regulation rather than a directive, it applies directly in every member state without national transposition, although supervisors and penalties remain national.
Article 2 lists around 20 categories of financial entity, including:
ICT third-party service providers—cloud platforms, data centres, core banking vendors, managed security providers—are affected indirectly through contracts, and the largest of them can be designated as critical ICT third-party providers (CTPPs) and overseen directly by the European Supervisory Authorities (EBA, EIOPA, and ESMA). Smaller entities benefit from a simplified ICT risk framework under the principle of proportionality.
The management body is accountable for an ICT risk management framework covering identification of assets and dependencies, protection, detection, response and recovery, backup policies, and learning from incidents. Directors must keep their ICT risk knowledge current, which makes DORA as much a governance law as a technical one.
Entities must classify ICT-related incidents against common criteria and report major ones to their competent authority. Under the supporting technical standards, the initial notification is due within four hours of classifying an incident as major, and no later than 24 hours after becoming aware of it, followed by an intermediate report within 72 hours and a final report within one month. Significant cyber threats may be reported voluntarily.
All in-scope entities need a testing programme proportionate to their size: vulnerability assessments, scenario-based tests, network security assessments, source code reviews where relevant, and penetration testing. Entities identified as significant must also carry out threat-led penetration testing (TLPT) on live production systems at least every three years, based on the TIBER-EU framework and performed by qualified external testers.
Firms must keep a register of information on all ICT contractual arrangements, assess concentration risk, and include mandatory provisions in contracts—service levels, audit and access rights, incident support, and exit strategies. Article 30 sets out what those contracts must contain, with stricter requirements where a supplier supports critical or important functions.
DORA encourages, but does not require, entities to share threat intelligence, indicators of compromise, and tactics with trusted peers through formal arrangements.
For financial entities, DORA acts as the sector-specific law that takes precedence over the overlapping cybersecurity and incident reporting obligations of the NIS2 Directive. It sits alongside GDPR rather than replacing it: a single incident may need to be reported as a major ICT incident under DORA and as a personal data breach to a data protection authority, each on its own timeline.
DORA is EU law and does not apply in the UK in its own right after Brexit. It still reaches many UK businesses:
In practice, a single control framework mapped to both regimes, and to ISO 27001, avoids duplicated effort.
Most firms begin with a gap assessment against the regulation and its technical standards, then build the register of information, update incident classification playbooks, and plan a testing programme. At Privia Security, we support DORA readiness, testing, and evidence gathering through our regulation and compliance services.
Not directly, unless part of your group is an EU-regulated financial entity. However, if you provide ICT services to EU banks, insurers, or investment firms, you will be bound by DORA requirements through your contracts. UK-regulated firms must also meet the PRA and FCA operational resilience rules, which pursue similar goals through a separate domestic regime.
TLPT is an intelligence-led Red Team exercise against live production systems that support critical functions. It simulates the tactics of real threat actors relevant to the entity and follows the TIBER-EU methodology, with a threat intelligence phase, a testing phase, and remediation. Significant financial entities must run it at least every three years, using qualified testers.
Member states set administrative penalties and remedial measures for financial entities, and national supervisors can issue orders, public statements, and fines. Critical ICT third-party providers overseen at EU level can face periodic penalty payments of up to 1% of their average daily worldwide turnover. Beyond penalties, weak resilience increases the real risk of prolonged outages and customer harm.
NIS2 is a directive covering many sectors, from energy to digital infrastructure, and must be transposed into national law. DORA is a directly applicable regulation written specifically for finance. For financial entities, DORA is treated as the sector-specific act, so its ICT risk and incident reporting rules apply in place of the overlapping NIS2 obligations.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.