Digital Operational Resilience Act (DORA)
The EU regulation on digital operational resilience for financial entities: ICT risk management, incident reporting, resilience testing and third-party risk.
What it is
Regulation (EU) 2022/2554, the Digital Operational Resilience Act, sets uniform requirements for how financial entities manage ICT risk so they can withstand, respond to and recover from ICT disruptions and cyber attacks. It brings ICT risk management, incident reporting, resilience testing and the management of ICT third-party providers into one regulation, and creates an EU oversight regime for critical ICT providers to the financial sector.
Who it applies to
- Banking and payments: credit institutions, payment institutions, account information service providers and electronic money institutions
- Investment and markets: investment firms, crypto-asset service providers and issuers of asset-referenced tokens, central securities depositories, central counterparties, trading venues, trade repositories, data reporting service providers, securitisation repositories and administrators of critical benchmarks
- Asset management: managers of alternative investment funds and UCITS management companies
- Insurance and pensions: insurance and reinsurance undertakings, insurance and reinsurance intermediaries (including ancillary intermediaries) and institutions for occupational retirement provision
- Other financial entities: credit rating agencies and crowdfunding service providers; microenterprises and some smaller entities benefit from proportionality or a simplified ICT risk management framework
- ICT third-party service providers: indirectly through their financial entity customers' contracts, and directly when designated as critical ICT third-party service providers and overseen by the European Supervisory Authorities
- Status
- Binding EU regulation, directly applicable in every member state. Adopted on 14 December 2022, in force since 16 January 2023 and applicable from 17 January 2025, supplemented by a set of regulatory and implementing technical standards. For financial entities it takes precedence over NIS2 on ICT risk management and incident reporting.
- Enforcement
- National competent authorities for each type of financial entity supervise compliance and member states set administrative penalties and remedial measures. Critical ICT third-party service providers are overseen by a Lead Overseer (EBA, EIOPA or ESMA), which can impose periodic penalty payments of up to 1 % of the provider's average daily worldwide turnover.
Key points
- ICT risk management framework: the management body has ultimate responsibility for ICT risk (Article 5) and the entity must maintain a documented framework covering identification, protection and prevention, detection, response and recovery, backup and restoration, learning and communication, reviewed at least yearly
- Major ICT-related incident reporting: incidents are classified using harmonised criteria, and major ones are reported to the competent authority through an initial notification, an intermediate report and a final report on deadlines set in the technical standards; significant cyber threats may be reported voluntarily
- Digital operational resilience testing: a risk-based testing programme, with tests of systems supporting critical or important functions at least yearly, and threat-led penetration testing (TLPT) on live production systems at least every three years for entities identified by their authorities
- ICT third-party risk and the register of information: entities need a third-party risk strategy and must keep a register of all contractual arrangements for ICT services, which they report to their competent authority, and must assess concentration risk before contracting
- Contract terms: Article 30 lists mandatory contract provisions, such as service descriptions and locations, data protection, access and audit rights, termination rights and, for critical or important functions, service levels, participation in testing and exit support
- Exit strategies: for ICT services supporting critical or important functions, entities must have documented, tested exit strategies and transition plans so they can leave a provider without disrupting their business or breaching regulation
- Oversight of critical ICT third-party service providers: the ESAs designate critical providers, which are then subject to direct oversight, inspections and recommendations by a Lead Overseer
Where to start
- 1Confirm your entity type and whether the simplified framework or proportionality applies, then identify your critical or important functions
- 2Assess your ICT risk management framework against Chapter II and Delegated Regulation (EU) 2024/1774, and get the management body to approve it
- 3Build and maintain the register of information for all ICT third-party arrangements, review contracts against Article 30, and write exit plans for providers supporting critical or important functions
- 4Align incident classification and reporting with the DORA criteria and deadlines, and plan a testing programme including any TLPT your authority requires
How it is structured
| Chapter I (Articles 1 to 4) | Subject matter, the list of entities in scope, definitions and proportionality |
|---|---|
| Chapter II (Articles 5 to 16) | ICT risk management: governance, the ICT risk management framework, identification, protection, detection, response and recovery, backups, learning, communication and the simplified framework |
| Chapter III (Articles 17 to 23) | ICT-related incident management, classification and reporting of major incidents, voluntary notification of significant cyber threats |
| Chapter IV (Articles 24 to 27) | Digital operational resilience testing, including threat-led penetration testing (TLPT) and requirements for testers |
| Chapter V, Section I (Articles 28 to 30) | Managing ICT third-party risk: strategy, register of information, pre-contract assessment, concentration risk, exit strategies and key contractual provisions |
| Chapter V, Section II (Articles 31 to 44) | Oversight framework for critical ICT third-party service providers: designation, Lead Overseer, powers, recommendations and penalty payments |
| Chapter VI (Article 45) | Information-sharing arrangements on cyber threat intelligence |
| Chapters VII to IX (Articles 46 to 64) | Competent authorities, penalties, delegated acts, review and final provisions |
A plain-language overview to help you learn, written by ThreatNoir. The official source prevails; this is not legal advice.
Items explained (27)
In the order of the framework itself.
- Article 2ScopeNot cited in our lessons yet
- Article 3DefinitionsNot cited in our lessons yet
- Article 5Governance and organisationCited once in our lessons
- Article 6ICT risk management frameworkNot cited in our lessons yet
- Article 7ICT systems, protocols and toolsNot cited in our lessons yet
- Article 8IdentificationNot cited in our lessons yet
- Article 9Protection and preventionCited once in our lessons
- Article 10DetectionNot cited in our lessons yet
- Article 11Response and recoveryNot cited in our lessons yet
- Article 12Backup policies and procedures, restoration and recovery procedures and methodsNot cited in our lessons yet
- Article 13(6)Learning and evolvingNot cited in our lessons yet
- Article 14CommunicationNot cited in our lessons yet
- Article 15Further harmonisation of ICT risk management tools, methods, processes and policiesNot cited in our lessons yet
- Article 16Simplified ICT risk management frameworkNot cited in our lessons yet
- Article 17ICT-related incident management processNot cited in our lessons yet
- Article 18Classification of ICT-related incidents and cyber threatsNot cited in our lessons yet
- Article 19Reporting of major ICT-related incidents and voluntary notification of significant cyber threatsNot cited in our lessons yet
- Article 24General requirements for the performance of digital operational resilience testingNot cited in our lessons yet
- Article 25Testing of ICT tools and systemsNot cited in our lessons yet
- Article 26Advanced testing of ICT tools, systems and processes based on TLPTCited once in our lessons
- Article 27Requirements for testers for the carrying out of TLPTNot cited in our lessons yet
- Article 28General principles on ICT third-party riskNot cited in our lessons yet
- Article 29Preliminary assessment of ICT concentration risk at entity levelNot cited in our lessons yet
- Article 30Key contractual provisionsNot cited in our lessons yet
- Article 31Designation of critical ICT third-party service providersNot cited in our lessons yet
- Article 45Information-sharing arrangements on cyber threat information and intelligenceNot cited in our lessons yet
- Article 50Administrative penalties and remedial measuresNot cited in our lessons yet