Compliance guide
DORA: what the EU Digital Operational Resilience Act requires
DORA is the EU regulation on digital operational resilience for the financial sector, Regulation (EU) 2022/2554. It has applied since 17 January 2025 to banks, payment firms, investment firms, insurers and the other financial entities it lists. It sets rules for ICT risk, incident reporting, testing, third-party risk and information sharing. For those firms it takes the place of NIS2 on risk management and incident reporting.
On this page
This is a plain-language summary, not legal advice. Where this page and the law differ, the law decides. DORA is a regulation, so it applies directly in every EU country. Details such as report templates and deadlines sit in separate EU rules that this page only points to.
1. In short
- DORA is Regulation (EU) 2022/2554, the Digital Operational Resilience Act. It sets uniform rules on the security of the network and information systems that financial firms rely on (Article 1).
- It applies to the financial entities listed in Article 2: banks, payment and e-money institutions, investment firms, insurers, fund managers, crypto-asset service providers and others. ICT third-party service providers are also named in the list.
- It has applied since 17 January 2025 (Article 64).
- Its rules fall in five areas: ICT risk management, incident management and reporting, resilience testing, ICT third-party risk and information sharing.
- For financial entities it replaces the NIS2 risk-management and reporting rules. DORA calls itself "lex specialis" (a more specific law that goes first) in relation to NIS2 (DORA recital 16).
- In Sweden, Finansinspektionen (FI) says DORA applies to most firms it supervises, and that those firms report major ICT-related incidents to FI.
2. Who DORA applies to
Article 2(1) lists the entities. "ICT" means information and communication technology: the software, hardware and network services a firm runs on.
| Group | Entities named in Article 2(1) |
|---|---|
| Banking and payments | Credit institutions; payment institutions; account information service providers; electronic money institutions |
| Markets | Investment firms; central securities depositories; central counterparties; trading venues; trade repositories; data reporting service providers; securitisation repositories |
| Crypto and funding | Crypto-asset service providers and issuers of asset-referenced tokens; crowdfunding service providers |
| Funds and pensions | Managers of alternative investment funds; management companies; institutions for occupational retirement provision |
| Insurance | Insurance and reinsurance undertakings; insurance, reinsurance and ancillary insurance intermediaries |
| Ratings and benchmarks | Credit rating agencies; administrators of critical benchmarks |
| ICT suppliers | ICT third-party service providers |
Article 2(2) calls the entities in points (a) to (t) "financial entities". ICT third-party service providers, point (u), are not financial entities, but the Regulation sets requirements for the contracts they sign with financial entities (Article 1(1), point (b)).
Article 2(3) lists what DORA does not apply to. Examples are insurance intermediaries that are microenterprises or small or medium-sized enterprises, and pension institutions that run schemes with no more than 15 members in total. Article 2(4) lets a Member State exclude certain named institutions listed in Article 2(5), points (4) to (23), of Directive 2013/36/EU. The full list is in the text.
Size matters inside the rules. Article 4 says firms apply them in proportion to their size, risk profile and the nature, scale and complexity of their services. Article 16 gives a simplified ICT risk framework to small and non-interconnected investment firms, exempted payment and e-money institutions, and small pension institutions. Some duties, such as the testing programme in Article 24, exclude microenterprises.
3. When it applies
Article 64 says the Regulation "shall apply from 17 January 2025". FI says the same on its page about DORA incident reporting: from 17 January 2025 DORA applies to reporting of major ICT-related incidents.
4. The five areas
Article 1(1) lists what the Regulation covers. These map to chapters II to VI. FI describes the same four main duties on its page "Om Dora": manage ICT risk, report ICT-related incidents, test digital operational resilience and manage ICT third-party risk.
| Area | Where | What the text requires |
|---|---|---|
| ICT risk management | Ch. II, Art. 5-16 | A "sound, comprehensive and well-documented ICT risk management framework" as part of overall risk management (Article 6(1)). The management body "bear[s] the ultimate responsibility for managing the financial entity's ICT risk" (Article 5(2), point (a)). |
| Incident management and reporting | Ch. III, Art. 17-23 | Define and run an incident management process to detect, manage and notify ICT-related incidents, and record all of them (Article 17). Classify them (Article 18). Report major ones to the authority (Article 19). |
| Resilience testing | Ch. IV, Art. 24-27 | A testing programme as part of the risk framework, for firms other than microenterprises (Article 24(1)). Tests by independent parties, internal or external (Article 24(4)). Listed tests include vulnerability assessments and scans, network security assessments and penetration testing (Article 25(1)). |
| ICT third-party risk | Ch. V, Art. 28-44 | Manage the risk as part of the ICT risk framework. The firm "shall, at all times, remain fully responsible" for its obligations when it uses ICT services (Article 28(1), point (a)). Keep a register of information on all contracts for ICT services (Article 28(3)). Contract terms are set in Article 30. |
| Information sharing | Ch. VI, Art. 45 | Financial entities "may exchange amongst themselves" cyber threat information within trusted communities, under arrangements that protect sensitive information (Article 45(1)). It is permitted, not required. |
Advanced testing. Article 26 adds threat-led penetration testing (TLPT) at least every 3 years for the firms identified under that Article, with the competent authority able to raise or lower the frequency. It is not for every firm.
Third-party oversight. Article 31 lets the European Supervisory Authorities (ESAs) designate ICT third-party service providers that are critical for financial entities. Those providers fall under a separate EU oversight framework (Chapter V, Section II).
5. Major incident reporting
Financial entities "shall report major ICT-related incidents" to the relevant competent authority (Article 19(1)). A "major" incident is one with "a high adverse impact on the network and information systems that support critical or important functions" (Article 3(10)). Firms classify incidents using the criteria in Article 18, such as the number of clients affected, the duration, the geographical spread, data losses and how critical the affected services are. The thresholds for "major" are set in technical standards.
Article 19(4) requires three submissions.
- An initial notification.
- An intermediate report when the status or handling changes significantly, with updates as needed.
- A final report when the root cause analysis is done and actual impact figures replace estimates.
DORA itself leaves the exact time limits to technical standards (Article 19(4) refers to Article 20). FI states the deadlines from Article 5 of the delegated regulation (the RTS) on its page "Incidentrapportering (Dora)".
| Report | Deadline, as FI states it |
|---|---|
| Initial | As early as possible, and in any case within four hours of classifying the incident as major and no later than 24 hours after becoming aware of it. |
| Intermediate | No later than 72 hours after the initial notification, even if the status or handling of the incident has not changed. Then an updated report without undue delay, and in any case as soon as normal operations resume. |
| Final | No later than one month after the intermediate report or, where relevant, the last updated report. |
Two further duties sit in Article 19. When a major incident affects clients' financial interests, the firm must inform its clients "without undue delay as soon as they become aware of it" (Article 19(3)). Reporting significant cyber threats is voluntary (Article 19(2)). A firm may outsource the reporting task but "remains fully responsible" for it (Article 19(5)).
In Sweden, FI says firms under its supervision report through its reporting platform Fidac, and that the duty rests on Article 19 and on FI's regulation FFFS 2024:20. Compare the NIS2 pattern in NIS2 incident reporting: 24 hours, 72 hours, one month.
6. DORA and NIS2
Short answer: a financial entity that DORA covers follows DORA for ICT risk management and incident reporting, not NIS2. Both texts say so.
| Where | What it says |
|---|---|
| DORA recital 16 | DORA's ICT risk management and incident reporting requirements are "more stringent" than earlier EU financial services law, and this means increased harmonisation compared with NIS2 as well. "Consequently, this Regulation constitutes lex specialis with regard to Directive (EU) 2022/2555." |
| NIS2 recital 28 | DORA "should be considered to be a sector-specific Union legal act in relation to this Directive with regard to financial entities". Its rules on ICT risk management, incident management and reporting, testing, information sharing and ICT third-party risk "should apply instead of those provided for in this Directive". Member States "should therefore not apply" NIS2's risk-management, reporting, supervision and enforcement provisions to those entities. |
| NIS2 Article 4(1) | Where a sector-specific EU act requires cybersecurity risk-management measures or incident notification at least equivalent in effect to NIS2, the relevant NIS2 provisions, "including the provisions on supervision and enforcement", do not apply to those entities. |
| NIS2 Article 2(10) | NIS2 "does not apply to entities which Member States have exempted from the scope of Regulation (EU) 2022/2554" under DORA Article 2(4). |
The two laws still keep in touch. Recital 28 says DORA lets the ESAs and DORA authorities join the NIS2 Cooperation Group and share information, and that DORA authorities should pass details of major ICT-related incidents on to NIS2 bodies. Where an ICT provider is designated critical under DORA Article 31, NIS2 Articles 32(10) and 33(6) tell NIS2 authorities to inform the DORA Oversight Forum when they use their powers over that provider.
An ICT supplier can sit under both. A cloud or managed service provider that is itself covered by NIS2 still has NIS2 duties of its own. See Does NIS2 apply to my company?
7. In Sweden
Sweden's NIS2 law is the Cybersäkerhetslag (2025:1506), explained in Cybersäkerhetslagen: what Sweden's NIS2 law requires. It has two rules that matter for financial firms, both in chapter 1.
| Section | What it says |
|---|---|
| 1 kap. 10 § | Where a law or other regulation sets security-measure or incident-reporting requirements, those apply instead if their effect at least matches the duties in 2 kap. 3-10 §§, taking account of their scope and the supervision and sanctions linked to them. |
| 1 kap. 11 § | The law does not apply to operators exempted under DORA Article 2(4). For an operator covered by the DORA regulation, "gäller inte skyldigheterna enligt 2 kap. 3-10 §§" (the duties in 2 kap. 3-10 §§ do not apply). |
So a DORA-covered firm does not carry the Swedish security-measure and incident-reporting duties of 2 kap. 3-10 §§. Those sections include the security measures (3 §), the management's role (4 §) and incident reporting (5-8 §§). The sentence names those sections only. This page does not say how the rest of the law, such as the registration duty in 2 kap. 2 §, applies to DORA firms. For that, ask the authority.
The Swedish NIS2 ordinance (2025:1507, 7 §) names FI as the supervisory authority for banking and financial market infrastructure under the NIS2 law. FI's own pages say DORA applies to most firms under its supervision and that firms report major ICT-related incidents to FI. For which authority supervises a given firm, check FI's pages. The ordinance also tells a NIS2 supervisory authority that oversees a provider designated critical under DORA Article 31 to inform the DORA oversight forum (19 §).
FI's DORA pages are at Om Dora and Incidentrapportering (Dora). FI says the DORA regulation is complemented by technical standards that set out the requirements in more detail.
8. If you sell ICT services to financial firms
DORA does not make every software vendor a "financial entity". It works through the customer's contract and register.
- The customer keeps a register of information on all contracts for ICT services and reports at least yearly to its authority on new arrangements and the categories of providers (Article 28(3)). You will be asked for the data that fills it.
- The contract must be in writing with the rights and obligations clearly allocated, and include the service level agreements (Article 30(1)).
- The customer stays "fully responsible" for its own compliance even when a provider runs the service (Article 28(1), point (a)).
- Providers the ESAs designate as critical come under EU oversight (Article 31).
Expect questions on incident assistance, access and audit rights, subcontracting, where data is processed, and testing (Article 30(2) and (3)). Supplier questions under NIS2 look similar: NIS2 requirements for suppliers.
9. How SimpleSecurity helps
SimpleSecurity keeps records and runs checks. It does not make a firm DORA compliant, and SimpleSecurity holds no certification. DORA's own reporting to the authority is done in the authority's channel, not here.
| DORA duty | SimpleSecurity service |
|---|---|
| Log all ICT-related incidents (Art. 17) | Incident Register |
| Assess ICT suppliers and link them to your assets (Art. 28) | Vendor Risk and Asset Database |
| Find weaknesses in internet-facing systems (Art. 25) | Vulnerability Scanner and Attack-Surface Discovery |
| Policies the management body approves (Art. 5) | Policy Register |
| Risk and control records (Art. 6) | Risk Register and Compliance |
See every service or see the plans.
Related guides
10. Sources
- Regulation (EU) 2022/2554 (DORA), recital 16 and Articles 1, 2, 3(10), 4, 5, 6, 16 to 20, 24 to 26, 28, 30, 31, 45 and 64
- Directive (EU) 2022/2555 (NIS2), recital 28 and Articles 2(10), 4, 32(10) and 33(6)
- Cybersäkerhetslag (2025:1506), 1 kap. 10 and 11 §§
- Förordning (2025:1507) om cybersäkerhet, 7 and 19 §§
- Finansinspektionen, Om Dora (last reviewed 12 November 2025)
- Finansinspektionen, Incidentrapportering (Dora) (last reviewed 20 November 2026)