GovernanceGrid

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.

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.

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.

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.

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.

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.

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.

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.

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.

Art. 14Communication

Entities have crisis communication plans for clients, counterparties and the public, communication policies for staff, and designated spokespeople for ICT incidents.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Summaries are GovernanceGrid's own paraphrases for orientation and are not legal advice. National transpositions may add detail.