Digital Operational Resilience Act (EU) 2022/2554
DORA sets uniform requirements for how financial entities manage ICT risk, handle and report ICT incidents, test their resilience, and control risk from ICT third-party providers. Official text ↗
Art. 5Governance and organisation
The management body carries final responsibility for ICT risk: it approves the risk framework, policies and budget, stays informed about incidents and third-party arrangements, and keeps its own ICT knowledge current through training.
- primaryDIR-01 Governance structure and accountability— Board-level accountability and decision rights for ICT.
- primaryDIR-03 Risk appetite and risk oversight— Approval of risk tolerance for ICT risk.
- supportingDIR-04 Resource and capability oversight— Budget and resources for operational resilience.
- supportingPLN-05 People, skills and awareness— Training for management body members.
- supportingDIR-05 Stakeholder reporting and transparency— Reporting to the management body on incidents and third parties.
Art. 6ICT risk management framework
Entities maintain a sound, documented ICT risk management framework with strategies, policies, procedures and tools, reviewed at least yearly and after major incidents, and audited regularly by people with sufficient ICT knowledge.
- primaryPLN-08 Technology risk management— The documented risk framework and its review cycle.
- primaryPLN-09 Information security management— Security management system as part of the framework.
- supportingPLN-01 Technology strategy and roadmap— Digital resilience strategy linked to business strategy.
- supportingASR-04 Independent assurance and audit— Periodic independent audit of the framework.
- supportingASR-05 Lessons learned and continuous improvement— Framework improvement after audits and incidents.
Art. 7ICT systems, protocols and tools
ICT systems must be reliable, have enough capacity for peak and stressed conditions, be resilient to adverse conditions and be kept technologically current.
- primaryCHG-04 Capacity and availability planning— Capacity for normal, peak and stressed conditions.
- supportingCHG-08 Asset and configuration management— Tracking of unsupported and end-of-life components.
- supportingPLN-02 Architecture management— Architecture standards that keep systems current.
Art. 8Identification
Entities identify and document all ICT-supported business functions, information and ICT assets, their dependencies including on third parties, and the risks affecting them, and review this at least yearly.
- primaryCHG-08 Asset and configuration management— Inventory of assets mapped to business functions.
- primaryPLN-08 Technology risk management— Risk identification tied to functions and assets.
- supportingPLN-06 Third-party and supply chain risk management— Identification of third-party dependencies.
- supportingPLN-10 Data and information management— Classification of information assets.
Art. 9Protection and prevention
Entities continuously monitor ICT systems, use protective tools and policies for security, access, authentication, change management, patching and encryption, and separate environments appropriately.
- primaryOPS-05 Identity and access management— Access rights and strong authentication.
- primaryOPS-06 Network and endpoint protection— Network segmentation and endpoint protection.
- primaryOPS-07 Vulnerability and patch management— Patching and vulnerability remediation.
- primaryOPS-10 Cryptography and key management— Encryption and key management.
- primaryCHG-05 Change control— Controlled, documented change to ICT systems.
- supportingCHG-03 Secure solution design and development— Separation of environments and secure build.
- supportingOPS-01 Service operations and monitoring— Continuous monitoring of systems.
Art. 10Detection
Entities have mechanisms to promptly detect anomalous activity and ICT performance issues, with alert thresholds, multiple layers of control and enough resources to monitor user activity.
- primaryOPS-09 Logging, detection and threat monitoring— Logging, correlation and alerting on anomalies.
- primaryOPS-01 Service operations and monitoring— Performance and availability monitoring with alert thresholds.
- supportingASR-06 Threat intelligence and information sharing— Threat intelligence feeding detection.
Art. 11Response and recovery
Entities maintain an ICT business continuity policy with response and recovery plans, crisis communication, yearly testing including third-party scenarios, and a crisis management function.
- primaryOPS-04 Business continuity and disaster recovery— Continuity policy, response and recovery plans, testing.
- supportingOPS-02 Incident management and reporting— Incident response as the entry point to continuity plans.
- supportingOPS-03 Problem management and root cause analysis— Post-disruption root cause analysis.
- supportingDIR-05 Stakeholder reporting and transparency— Communication to stakeholders during crises.
Art. 12Backup policies and restoration
Entities define backup scope and frequency, keep backups in environments separated from the source, and test restoration so that data and systems can be recovered with minimal disruption.
- primaryOPS-08 Backup and restoration— Backup policy, isolated copies and restoration tests.
- supportingOPS-04 Business continuity and disaster recovery— Recovery objectives that drive backup design.
Art. 13Learning and evolving
Entities analyse threats, incidents and test results, run post-incident reviews, train all staff and management on ICT security and resilience, and monitor technological developments.
- primaryASR-05 Lessons learned and continuous improvement— Post-incident reviews and improvement backlog.
- primaryPLN-05 People, skills and awareness— Security and resilience training for staff and management.
- supportingOPS-03 Problem management and root cause analysis— Root cause analysis of incidents.
- supportingASR-06 Threat intelligence and information sharing— Threat landscape monitoring.
Art. 14Communication
Entities have crisis communication plans for clients, counterparties and the public, communication policies for staff, and designated spokespeople for ICT incidents.
- primaryOPS-04 Business continuity and disaster recovery— Crisis communication within continuity planning.
- supportingDIR-05 Stakeholder reporting and transparency— Stakeholder communication responsibilities.
Art. 16Simplified ICT risk management framework
Smaller or exempted entities may apply a lighter framework that still covers risk identification, protection, continuity, monitoring and training, proportionate to their size and risk.
- primaryPLN-08 Technology risk management— Proportionate risk management framework.
- supportingOPS-04 Business continuity and disaster recovery— Continuity and recovery for critical functions.
- supportingOPS-08 Backup and restoration— Backup and restoration.
- supportingPLN-05 People, skills and awareness— Staff awareness.
Art. 17ICT-related incident management process
Entities define and implement a process to detect, manage, log, classify and escalate ICT incidents, with roles, communication plans and root cause analysis.
- primaryOPS-02 Incident management and reporting— The incident management process itself.
- supportingOPS-03 Problem management and root cause analysis— Root cause analysis after incidents.
- supportingOPS-09 Logging, detection and threat monitoring— Detection feeding the incident process.
Art. 18Classification of ICT-related incidents and cyber threats
Incidents are classified using criteria such as clients affected, duration, geographic spread, data losses, criticality of services and economic impact, to determine whether they are major.
- primaryOPS-02 Incident management and reporting— Classification criteria embedded in the incident procedure.
Art. 19Reporting of major ICT-related incidents
Major incidents are reported to the competent authority through an initial notification, an intermediate report and a final report within the regulatory deadlines, and clients are informed where affected.
- primaryOPS-02 Incident management and reporting— Regulatory notification steps and deadlines.
- supportingDIR-05 Stakeholder reporting and transparency— Ownership of regulatory reporting.
- supportingASR-03 Regulatory and contractual compliance— Tracking of the reporting obligation.
Art. 24Digital operational resilience testing programme
Entities maintain a risk-based testing programme, run by independent parties, that tests all critical ICT systems at least yearly and tracks the remediation of findings.
- primaryCHG-06 Testing, release and acceptance— The testing programme and independent testers.
- supportingOPS-07 Vulnerability and patch management— Penetration tests and remediation tracking.
- supportingASR-05 Lessons learned and continuous improvement— Lessons from tests feeding improvement.
Art. 25Testing of ICT tools and systems
The testing programme includes vulnerability assessments, scans, open-source analysis, network security assessments, gap analyses, performance and penetration testing, among others.
- primaryOPS-07 Vulnerability and patch management— Vulnerability assessments and penetration tests.
- primaryCHG-06 Testing, release and acceptance— Performance, end-to-end and scenario tests.
- supportingCHG-03 Secure solution design and development— Source code review and secure build.
Art. 26Advanced threat-led penetration testing
Designated entities perform threat-led penetration testing of live production systems at least every three years using qualified testers, covering critical functions and relevant third-party providers.
- primaryOPS-07 Vulnerability and patch management— Advanced penetration testing of production systems.
- supportingOPS-09 Logging, detection and threat monitoring— Detection capability validated by the test.
- supportingPLN-06 Third-party and supply chain risk management— Inclusion of third-party providers in scope.
Art. 28ICT third-party risk: general principles
Entities manage third-party ICT risk as part of their framework, keep a register of information on all contractual arrangements, assess providers before contracting, and ensure exit strategies for critical services.
- primaryPLN-06 Third-party and supply chain risk management— Supplier register, due diligence and exit strategies.
- supportingPLN-08 Technology risk management— Third-party risk inside the risk framework.
- supportingDIR-05 Stakeholder reporting and transparency— Reporting of the register to authorities.
Art. 29Preliminary assessment of ICT concentration risk
Before contracting critical services, entities assess concentration risk, substitutability of the provider and risks from sub-outsourcing, including providers outside the EU.
- primaryPLN-06 Third-party and supply chain risk management— Concentration and substitutability assessment.
- supportingPLN-08 Technology risk management— Recording concentration risk in the risk register.
Art. 30Key contractual provisions
Contracts with ICT providers contain defined elements such as service descriptions, data locations, service levels, incident assistance, audit and access rights, termination rights and exit support.
- primaryPLN-06 Third-party and supply chain risk management— Contract clause checklist and contract reviews.
- supportingASR-03 Regulatory and contractual compliance— Monitoring of contractual obligations.
Art. 45Information-sharing arrangements
Entities may exchange cyber threat information and intelligence within trusted communities under arrangements that protect sensitive data and competition, and notify authorities of participation.
- primaryASR-06 Threat intelligence and information sharing— Participation in information-sharing arrangements.
Summaries are GovernanceGrid's own paraphrases for orientation and are not legal advice. National transpositions may add detail.