EU Regulation · (EU) 2022/2554
DORA: Digital Operational Resilience Act
DORADigital Operational Resilience Act, Regulation (EU) 2022/2554, sets one set of ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. requirements for EU financial entities and the technology providers they rely on.
- 17 Jan 2025 DORADigital Operational Resilience Act applies to financial entities across the EU
- 4 hours for the first notice of a major ICT-related incidentAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. after classification
- Every 3 years threat-led penetration testingA framework that mimics the tactics, techniques and procedures of real attackers to test an organisation's live critical functions. DORA requires certain financial entities to carry out TLPT regularly. for entities designated by their supervisor
What Is DORA?
Before DORADigital Operational Resilience Act, ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. requirements for banks, insurers and investment firms were spread across sector laws and supervisory guidelines, and they did not match. A cyberattack or an outage at a shared cloud provider could hit many firms at once, and supervisors had no direct view of those providers.
DORADigital Operational Resilience Act puts one rulebook in place for the EU financial sector. A firm must be able to withstand, respond to and recover from ICTInformation and Communication Technology disruption and keep critical services running for its customers. The European Supervisory AuthoritiesEuropean Supervisory Authority also gain direct oversight of the ICTInformation and Communication Technology providers the sector depends on most.
DORA is a regulation, so it applies directly in every member state. National acts add the requirements it leaves to each country, such as the supervisory authority and the choices it allows. On 21 November 2026, 26 of the 29 countries shown had their act in force; the table below links to each national act.
- Full title
- Digital Operational Resilience Act (DORA)
- Official reference
- Regulation (EU) 2022/2554
- Type
- Regulation
- Issued by
- European Parliament and Council of the EU
- Adopted
- 14 December 2022
- In force
- 16 January 2023
- Applies from
- 17 January 2025
- Status
- In force and applicable
- Countries
- All 27 EU member states
Official text
Verified by
Ahmet Ucar
Principal Consultant (CISSPCertified Information Systems Security Professional, CISMCertified Information Security Manager, CISACertified Information Systems Auditor, CIPP/ECertified Information Privacy Professional/Europe)
Last updated 18 November 2026
Does It Apply to You?
Answer once on your sectors, size and countries. You get the result per country, with the articles behind it.
What DORA Requires
The EU baseline. Each country page shows where the national act differs.
Articles 5 to 16
ICT risk management
A framework owned by the management body to identify ICTInformation and Communication Technology assets and dependencies, protect and detect, respond and recover, and learn from incidents. It is reviewed at least once a year and audited by internal audit; microenterprisesMicroenterprise Under DORA review it periodically and need no internal audit, and Article 16 entities use a simplified framework.
Articles 17 to 23; Delegated Regulation (EU) 2025/301, Article 5
Incident management and reporting
A process to detect, classify and log ICTInformation and Communication Technology incidents. A major incident goes to the supervisor in three steps: an initial notification within 4 hours of classifying it as major (and, unless classified later, within 24 hours of becoming aware of it), an intermediate report within 72 hours of that notification and a final report within one month of the latest intermediate report.
Articles 24 to 27
Resilience testing
A risk-based testing programme with vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments, scenario tests and penetration tests; microenterprisesMicroenterprise Under DORA are outside the programme and test on a risk basis under Article 25(3). Firms selected by their supervisor run threat-led penetration testingA framework that mimics the tactics, techniques and procedures of real attackers to test an organisation's live critical functions. DORA requires certain financial entities to carry out TLPT regularly. (TLPT) at least every three years, unless the supervisor changes the frequency.
Articles 28 to 30
ICT third-party risk
A strategy for ICT third-party riskIn the Digital Operational Resilience Act context, the technology risk a financial organisation faces when it uses Information and Communication Technology services supplied by another organisation or that supplier's subcontractors. This concerns the organisation's dependence on externally provided technology, including outsourced services. Managing it involves assessing suppliers, documenting service arrangements, setting suitable contract terms, monitoring risks and planning how to leave an arrangement while keeping services running. (not required of microenterprisesMicroenterprise Under DORA or Article 16 entities), due diligence before signing, the contract clauses listed in Article 30, exit plans for services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. and a check on concentration risk.
Show All 7 Requirements
Article 28(3)
Register of information
A register of all contractual arrangements for ICTInformation and Communication Technology services, at entity, sub-consolidated and consolidated level, given to the competent authority on request, with a report at least yearly on new arrangements and timely notice of planned arrangements supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions..
Articles 31 to 44
Oversight of critical ICT providers
The ESAsEuropean Supervisory Authority designate critical ICTInformation and Communication Technology third-party providers and oversee them directly through a Lead OverseerThe European Supervisory Authority appointed under DORA to oversee a particular critical ICT third-party service provider. It is the ESA responsible for the financial entities that together hold the largest share of total assets among those using that provider, and it can request information, inspect and issue recommendations., with powers to inspect, issue recommendations and impose periodic penalty payments.
Article 45
Information-sharing arrangements
Financial entities may exchange cyber threatAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. information within trusted communities, under arrangements that protect confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. and personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity.. They must tell the competent authority when they join or leave.
More Requirements in Related Documents
- DORA ICT Risk Management RTSRTS · 6 requirements
- JC 2024 34Guidelines · 5 requirements
- DORA Third-Party Policy RTSRTS · 4 requirements
- DORA Subcontracting RTSRTS · 5 requirements
- DORA Register of Information ITSITS · 4 requirements
- DORA Incident Classification RTSRTS · 5 requirements
- DORA Incident Reporting RTSRTS · 5 requirements
- DORA Incident Reporting ITSITS · 6 requirements
- DORA TLPT RTSRTS · 7 requirements
- DORA Critical Provider CriteriaDelegated Regulation · 6 requirements
- DORA Oversight Conditions RTSRTS · 5 requirements
| Covered entities | Kind | Article | Where defined |
|---|---|---|---|
| Financial entitiesCredit institutions, Payment institutions, Electronic money institutions, Investment firms, Crypto-asset service providers, Insurance and reinsurance undertakings | Role | Article 2(2) | Collective term for the entities in Article 2(1), points (a) to (t), which carry the ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management, incident reporting, testing and third-party risk duties. |
| Credit institutionsCredit institutions | Legal status | Article 2(1)(a) | As defined in Regulation (EU) No 575/2013. |
| Payment institutionsPayment institutions | Legal status | Article 2(1)(b) | Including payment institutionsPayment Institution exempted under Directive (EU) 2015/2366; account information service providersA payment service provider offering an online service that gives consolidated information on one or more payment accounts held by the user with other payment service providers. PSD2 Article 33 applies a registration regime to providers offering only account information services; combined-service firms must assess the authorisation requirements for their other services. DORA includes account information service providers among its financial entities. are listed separately in point (c). |
| Electronic money institutionsElectronic money institutions | Legal status | Article 2(1)(d) | Including electronic money institutionsElectronic Money Institution exempted under Directive 2009/110/EC. |
| Investment firmsInvestment firms | Legal status | Article 2(1)(e) | Authorised under Directive 2014/65/EU (MiFID II); firms exempted under Articles 2 and 3 of that Directive are excluded (Article 2(3)(d)). |
| Crypto-asset service providersA legal person or other undertaking that provides one or more crypto-asset services, such as custody, exchange, trading platforms, transfers or advice, to clients on a professional basis, and is allowed to do so under MiCA. Authorised providers can passport their services across the EU and are in scope of DORA. and issuers of asset-referenced tokensCrypto-asset service providers | Legal status | Article 2(1)(f) | Crypto-asset service providersA legal person or other undertaking that provides one or more crypto-asset services, such as custody, exchange, trading platforms, transfers or advice, to clients on a professional basis, and is allowed to do so under MiCA. Authorised providers can passport their services across the EU and are in scope of DORA. authorised under MiCAMarkets in Crypto-Assets Regulation, and issuers of asset-referenced tokensA crypto-asset, other than an electronic money token, that purports to maintain a stable value by referencing another value or right or a combination, which may include one or more official currencies. Classification determines the applicable MiCA issuer requirements, including authorisation or the credit-institution procedure and reserve-of-assets duties, subject to the statutory exemptions.. |
| Insurance and reinsurance undertakingsInsurance and reinsurance undertakings | Legal status | Article 2(1)(n) | Undertakings referred to in Article 4 of Directive 2009/138/ECDirective 2009/138/EC on the Taking-Up and Pursuit of the Business of Insurance and Reinsurance (small undertakings outside Solvency IIDirective 2009/138/EC on the Taking-Up and Pursuit of the Business of Insurance and Reinsurance) are excluded (Article 2(3)(b)). |
| Central securities depositories, central counterparties, trading venues and other financial entities | Legal status | Article 2(1)(c), (g) to (m) and (o) to (t) | Also account information service providersA payment service provider offering an online service that gives consolidated information on one or more payment accounts held by the user with other payment service providers. PSD2 Article 33 applies a registration regime to providers offering only account information services; combined-service firms must assess the authorisation requirements for their other services. DORA includes account information service providers among its financial entities., trade repositories, fund managers, management companies, data reporting service providers, insurance intermediaries, IORPs, credit rating agencies, critical benchmark administrators, crowdfunding service providers and securitisation repositories. |
| ICT third-party service providersICT third-party service providers | Role | Article 2(1)(u); Article 3(19) | An undertaking providing ICTInformation and Communication Technology services to financial entities. |
| Critical ICT third-party service providersICT third-party service providers | Role | Article 3(23); Article 31 | Designated as critical by the European Supervisory AuthoritiesEuropean Supervisory Authority and subject to the Union oversight framework (Articles 31 to 44). |
Lighter requirements: Article 16 sets a simplified ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework for smaller entities such as small and non-interconnected investment firms, exempted payment and e-moneyElectronic Money institutions and small occupational pension funds.
DORA applies to 20 types of financial entity listed in Article 2, including:
- credit institutions
- payment and e-money institutions, including account information service providers
- investment firms and trading venues
- crypto-asset service providers and issuers of asset-referenced tokens
- insurance and reinsurance undertakings, and insurance intermediaries that are not micro, small or medium-sized
- fund managers (AIFMs and UCITS management companies) and occupational pension funds
- central counterparties, central securities depositories and trade repositories
- credit rating agencies, crowdfunding service providers and administrators of critical benchmarks
ICT third-party service providers are covered too. Most are reached through the contracts they sign with financial entities. Those designated as critical are supervised directly by an ESA acting as Lead Overseer.
The requirements are proportionate. Certain smaller firms use the simplified ICT risk management framework of Article 16; microenterprises follow the full framework with the reliefs in Articles 5 to 15, and only firms selected by their supervisor run threat-led penetration tests.
Every year
File your register of information with your supervisor, on the date it sets DORA Article 28(3)
31 Dec 2026
Register of information: data cut-off date ESA Decision 2024/22
4 hours
Incident notification
When: Within 4 hours of classifying it as major, and no later than 24 hours of becoming aware; if classified as major after that, within 4 hours of classifying it
Within 4 hours of classifying the incident as major, and no later than 24 hours after becoming aware of it; if it is classified as major after that, within 4 hours of classifying it.
72 hours
Intermediate report
When: Within 72 hours of the initial notification
Within 72 hours of the initial notification, and again when the status changes significantly.
1 month
Final report
When: Within one month of the latest intermediate report
Within 1 month of the latest intermediate report, with the root cause analysisA structured investigation into the underlying causes of a problem or incident, rather than only its visible effects. For an IT incident, it examines how technical failures, working practices or other conditions combined to cause the disruption. The findings help an organisation choose corrective measures that address those causes and reduce the chance of recurrence..
Notice to customers or users
Without undue delay when a major incident affects clients' financial interests (Article 19(3)).
Voluntary notification
Significant cyber threats that the entity considers relevant to the financial system, service users or clients can be notified voluntarily (Article 19(2)).
Every 3 years
Penetration testing
Threat-led penetration testingA framework that mimics the tactics, techniques and procedures of real attackers to test an organisation's live critical functions. DORA requires certain financial entities to carry out TLPT regularly. at least every 3 years for entities the competent authority designates (Article 26).
Who may do it: Internal or external testers that meet Article 27; when internal testers are used, every third test must use external testers.
Every year
Report new ICT contracts to the supervisor Article 28(3)
Every year
Review your ICT risk management framework Article 6(5)
Every year
Review ICT risk scenarios Article 8(2)
Every year
Risk assessment of legacy ICT systems Article 8(7)
Every year
Test continuity and recovery plans Article 11(6)
Every year
Senior ICT staff report to the management body Article 13(5)
Every year
Test all ICT systems that support critical functions Article 24(6)
Every year
Estimate annual costs and losses from major incidents Article 11(10)
When It Is Due: Significant incident
Major ICT-related incidentsAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports., classified with the criteria and thresholds in Commission Delegated Regulation (EU) 2024/1772 (clients affected, duration, geographical spread, data losses, critical services affected, economic impact). Significant cyber threatsA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident. may be reported voluntarily.
DORADigital Operational Resilience Act leaves most penalties to national law. Member States must give their supervisors the power to impose administrative penalties and remedial measures for breaches (Article 50). These include orders to stop the conduct, public statements naming the firm and fines. The amounts are set nationally, and some countries also provide criminal penalties.
The management body carries final responsibility for ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. (Article 5), and national law can apply penalties to its members and to other individuals responsible for a breach.
Critical ICTInformation and Communication Technology third-party providers face direct EU enforcement. The Lead OverseerThe European Supervisory Authority appointed under DORA to oversee a particular critical ICT third-party service provider. It is the ESA responsible for the financial entities that together hold the largest share of total assets among those using that provider, and it can request information, inspect and issue recommendations. can impose a periodic penalty payment of up to 1% of the provider’s average daily worldwide turnover in the previous business year, for each day of non-compliance, for up to six months (Article 35).
Who Enforces It
National competent authorities supervise financial entities, for example De Nederlandsche BankThe central bank of the Netherlands, part of the Eurosystem, which safeguards financial stability and supervises financial institutions. DNB developed the TIBER-NL framework in 2016 and oversees TIBER tests in the Dutch financial sector. and the AFMAutoriteit Financiële Markten in the Netherlands, BaFinFederal Financial Supervisory Authority in Germany and the Central Bank of Ireland. The EBAEuropean Banking Authority, EIOPAEuropean Insurance and Occupational Pensions Authority and ESMAEuropean Securities and Markets Authority act as Lead OverseersThe European Supervisory Authority appointed under DORA to oversee a particular critical ICT third-party service provider. It is the ESA responsible for the financial entities that together hold the largest share of total assets among those using that provider, and it can request information, inspect and issue recommendations. for critical ICTInformation and Communication Technology third-party providers.
-
DORA ICT Risk Management RTS: Regulatory Technical Standards on ICT Risk Management
- JC 2024 34: Major ICT Incident Costs and Losses Guidelines
-
DORA Third-Party Policy RTS: Regulatory Technical Standards on the ICT Third-Party Policy
-
DORA Subcontracting RTS: RTS on Subcontracting of ICT Services
-
DORA Register of Information ITS: Implementing Technical Standards on the Register of Information
-
DORA Incident Classification RTS: Regulatory Technical Standards on the Classification of ICT-Related Incidents
-
DORA Incident Reporting RTS: Regulatory Technical Standards on Major Incident Reports
- DORA Incident Reporting ITS: Implementing Technical Standards on Incident Reporting Forms and Templates
-
DORA TLPT RTS: Regulatory Technical Standards on Threat-Led Penetration Testing
-
DORA Critical Provider Criteria: Criteria for Designating Critical ICT Third-Party Service Providers
-
DORA Oversight Conditions RTS: Regulatory Technical Standards on the Conduct of Oversight Activities
Each mapping links requirements one by one, with how closely they match and what the other one adds. The full tables are available as spreadsheets.
DORA National Requirements by Member State
Of 29 countries: 26 in force, 1 draft published, 1 bill in parliament, 1 no draft yet, as of 21 November 2026. Pick a country for its national act.
Austria
Belgium
Bulgaria
Croatia
Cyprus · Draft published
Czechia
Denmark
Estonia
Finland
France · Bill in parliament
Germany
Greece
Hungary
Iceland
Ireland
Italy
Latvia
Liechtenstein
Luxembourg
Malta
Netherlands
Norway
Poland
Portugal
Romania
Slovakia
Slovenia
Spain · No draft yet
Sweden
Compare All 29 Countries
| Country | Status | Authorities | Obligations apply from |
|---|---|---|---|
| In force | FMA primary
| See country page | |
| In force | NBB primary | See country page | |
| In force since 8 Jul 2025 | BNB primary | See country page | |
| In force | See country page | ||
| Draft published | Not yet | ||
| In force since 15 Feb 2025 | CNB primary | Per entity | |
| In force | DFSA primary | See country page | |
| In force | FI primary | See country page | |
| In force | Fiva primary | See country page | |
| Bill in parliament | ACPR primary
| Not yet | |
| In force | BaFin primary
| See country page | |
| In force since 11 Apr 2025 | BoG primary
| See country page | |
| In force | MNB primary | Per entity | |
| In force since 1 Jan 2026 | See country page | ||
| In force | CBI primary
| See country page | |
| In force | Bank of Italy primary
| Per entity | |
| In force | Bank of Latvia primary | Per entity | |
| In force since 1 Jul 2025 | |||
| In force | CSSF primary | See country page | |
| In force since 17 Jan 2025 | MFSA primary | See country page | |
| In force | DNB primary | See country page | |
| In force | Financial Supervisory Authority of Norway primary
| See country page | |
| In force | KNF primary | Per entity | |
| In force | Bank of Portugal primary | See country page | |
| In force since 11 Mar 2026 | BNR primary
| See country page | |
| In force | NBS primary | See country page | |
| In force since 26 Apr 2025 | BS primary | See country page | |
| No draft yet | Bank of Spain primary
| See country page | |
| In force | FI primary
| See country page |
Primary competent authority first; sector authorities and CSIRTs below it. "Per entity" means the date runs from each organisation's own registration or designation: hover for the requirement, or open the country page.
Latest DORA Updates
All DORA Updates-
20 November 2026GuidanceLuxembourg
CSSF Says NGINX Remote Code Execution Is a Major ICT Incident to Notify
On 20 November 2026 the CSSF warned supervised entities about five NGINX vulnerabilities (NGINX2ROOT). Unauthenticated remote code execution through them counts as a major ICT-related incident to notify under Circular CSSF 25/893 (DORA) or Circular CSSF 24/847.
-
18 November 2026GuidanceLuxembourg
CSSF Says Java4Shell Remote Code Execution Is a Major ICT Incident to Notify
On 18 November 2026 the CSSF warned supervised entities about Java4Shell (CVE-2026-114938) in the OpenJDK Base64 decoder. Unauthenticated remote code execution through it counts as a major ICT-related incident to notify under Circular CSSF 25/893 (DORA) or Circular CSSF 24/847.
-
17 November 2026GuidancePoland
Poland’s Cybersecurity Plenipotentiary Sets Measures for Banks and Market Infrastructure
Poland's Government Plenipotentiary for Cybersecurity issued Recommendation 2026-67a-10 on 17 November 2026. It sets sector measures for banks and market infrastructure under the KSC, alongside DORA, covering ICT supply chain, DNS, DDoS, ransomware and APIs.
DORA Milestones Since 2022
- Registers of information reported againThe register is an annual duty. National supervisors set their own dates in March 2026, so check yours for the next round.
- ESAs publish the first list of critical ICT third-party providersThe list names 19 providers, among them large cloud and technology firms. They now fall under direct EU oversight, which does not replace your own third-party risk duties.
- Delegated Regulation (EU) 2025/532 on subcontracting of ICT services appliesEBA page on the joint RTS on subcontracting: in force, application date 22 July 2025.
- Deadline for the first registers of information to reach the ESAsNational supervisors collected the registers first, on dates of their own, and passed them on to the European Supervisory Authorities by this date.
- Applies to financial entitiesICT risk management, incident reporting, resilience testing and third-party risk requirements apply directly, with no national act needed.
- Entered into force; two-year transition startsFinancial entities had two years to prepare, while the European Supervisory Authorities wrote the technical standards.
- Published in the Official Journal of the EUPublished with NIS2. An accompanying directive amends existing financial services law to match.
- Adopted by the European Parliament and the CouncilRegulation (EU) 2022/2554 sets one rulebook on ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. for most EU financial entities and for the ICTInformation and Communication Technology providers that serve them.
How We Help With DORA
Start with an assessment, or have us run the work.
Work We Have Delivered on DORA
Clients are described, never named.
Questions
DORA FAQ: Common Questions Answered
When does DORA apply?
DORADigital Operational Resilience Act has applied since 17 January 2025. It entered into force on 16 January 2023, and the two years in between were the transition period. There is no further grace period: supervisors expect firms to comply now.
Does DORA apply to my firm?
It applies if you are one of the 20 types of financial entity in Article 2, such as a bank, payment or e-money institution, investment firm, insurer, crypto-asset service providerA legal person or other undertaking that provides one or more crypto-asset services, such as custody, exchange, trading platforms, transfers or advice, to clients on a professional basis, and is allowed to do so under MiCA. Authorised providers can passport their services across the EU and are in scope of DORA. or fund manager. ICTInformation and Communication Technology providers are affected through their contracts with these firms, and critical ones are supervised directly.
How does DORA relate to NIS2?
DORADigital Operational Resilience Act is the sector-specific law for financial entities. Where DORADigital Operational Resilience Act covers ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management, incident reporting and testing, financial entities follow DORADigital Operational Resilience Act instead of the matching NIS2Directive on Measures for a High Common Level of Cybersecurity Across the Union duties. NIS2Directive on Measures for a High Common Level of Cybersecurity Across the Union can still matter for other companies in the same group.
What is the register of information?
It is a structured record of every contract a financial entity has for ICTInformation and Communication Technology services, in the format set by Implementing Regulation (EU) 2024/2956. Supervisors collect it every year and use it to spot concentration risk and to identify critical providers.
What counts as a major ICT-related incident?
An incident that meets the thresholds in Delegated Regulation (EU) 2024/1772. The criteria include the number of clients affected, duration, data losses, the critical services affected and the economic impact. A major incident must be reported to the supervisor within 4 hours of classification and no later than 24 hours after detection.
Who has to run threat-led penetration testing?
Only financial entities that their supervisor selects, based on size, systemic importance and risk profile. They run a test at least every three years, following the TIBER-EU approach.
Can a smaller firm use a lighter regime?
Yes, for certain smaller firms. Entities listed in Article 16(1), such as small and non-interconnected investment firms and payment institutions exempted under PSD2Revised Payment Services Directive, use the simplified ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework in Article 16. Microenterprises follow the full framework with the reliefs in Articles 5 to 15. Incident reporting and third-party requirements still apply.
What happens if we do not comply?
National supervisors can order you to stop the conduct, publish the breach and impose fines, with amounts set in national law. The management body is responsible for ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment., and national law can extend penalties to its members.
Find Out Where You Stand on DORA
Thirty minutes with a principal consultant. You leave knowing which DORADigital Operational Resilience Act duties apply to your firm, where the gaps are and what to fix first.