DORA (Regulation (EU) 2022/2554)
The register cites 12 of its 26 clauses, on 24 policy types. Rendered when the buyer ticks "DORA".
Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim. Open the standard on the compliance platform. What it expects of a policy set: the DORA regime page.
Clauses cited
12 of 26DORA Art. 5 Governance and organisationThe management body defines, approves and oversees the ICT risk management framework and carries final accountability for ICT risk: it sets ICT roles and governance, approves the digital operational resilience strategy and ICT risk tolerance, approves and reviews the continuity and response plans, the ICT internal audit plans and the ICT third-party policy, allocates budget for resilience, awareness and skills, and receives reporting on third-party arrangements and major incidents. Its members keep their own ICT risk knowledge current through regular training. Entities other than microenterprises must also set up a role to monitor ICT third-party arrangements, or name a senior manager accountable for that exposure (Art. 5(3)). Applied in proportion to size, risk profile and complexity under Article 4(1). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
Common gap: Board approves the framework once and never revisits plans, audit plans or the third-party policy
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 6 ICT risk management frameworkFinancial entities keep a sound, comprehensive and documented ICT risk management framework within their overall risk management system, covering the strategies, policies, procedures, protocols and tools that protect information and ICT assets and physical infrastructure, and including a digital operational resilience strategy (risk tolerance, security objectives, reference architecture, detection, testing and incident communication). The framework is reviewed yearly as a minimum (a microenterprise may instead set its own periodic cycle), and also after major ICT-related incidents and after supervisory instructions or test and audit conclusions, with a review report available to the competent authority on request (Art. 6(5)). Entities other than microenterprises assign ICT risk to an independent control function (Art. 6(4)) and subject the framework to regular internal audit by auditors with ICT expertise and independence, followed by a formal process to remediate critical findings (Art. 6(6) and (7)); microenterprises are outside the internal-audit duty. Applied in proportion to size, risk profile and complexity under Article 4(1). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
Common gap: Framework reviewed only on the calendar cycle, not after a major ICT-related incident
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 9 Protection and preventionFinancial entities keep the security and operation of ICT systems and tools under continuous monitoring and control and limit ICT risk with security policies, procedures, protocols and tooling designed to keep ICT systems (above all those supporting critical or important functions) resilient and available, and protect data at rest, in use and in transit. The chosen solutions must be appropriate under Article 4 and cover secure data transfer, data loss and corruption, unauthorised access and data management risk. Within the ICT risk management framework they keep an information security policy (covering customer data where applicable), a risk-based network and infrastructure management structure that can cut or segment connections at once, least-privilege access controls, strong authentication and cryptographic key protection, a risk-based ICT change management process approved by management, and documented patch and update policies. Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
Common gap: Network cannot be segmented quickly to contain an attack
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 10 DetectionFinancial entities have mechanisms, aligned with the Article 17 incident process, that promptly detect anomalous activity, network performance problems and ICT-related incidents and flag possible material single points of failure; the mechanisms provide multiple control layers, alert thresholds and criteria that start incident response, automatic alerts to response staff, and are tested regularly under Article 25. Sufficient resources monitor user activity, anomalies and cyber-attacks. Data reporting service providers, where the entity is one, additionally check trade reports for completeness, omissions and obvious errors and ask for re-transmission (Art. 10(4)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
Common gap: Alert thresholds set once and never tuned or tested
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 11 Response and recoveryFinancial entities adopt an ICT business continuity policy within their overall continuity policy and implement it through documented arrangements that keep critical or important functions running, contain and resolve incidents, estimate preliminary impacts, and drive crisis communication and reporting under Articles 14 and 19; they run a business impact analysis, keep ICT response and recovery plans, test, at least once a year and after substantive changes, the continuity and response plans for the systems behind every function, test crisis communication plans, and keep records of activity during disruptions. Entities other than microenterprises additionally have the response and recovery plans reviewed by independent internal audit (Art. 11(3)), include cyber-attack and switchover scenarios in testing (Art. 11(6)), run a crisis management function (Art. 11(7)), and estimate aggregated annual costs and losses of major incidents when the authority asks (Art. 11(10)). Central securities depositories also send continuity test results to the authority (Art. 11(9)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
Common gap: Plans tested only for critical systems, not for systems supporting all functions
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 12 Backup policies and procedures, restoration and recoveryFinancial entities document backup policies (scope of data and minimum backup frequency set by criticality or confidentiality) and restoration and recovery procedures, set up backup systems whose activation does not weaken security, and test backup and restoration periodically. When restoring with their own systems they restore onto ICT systems kept separate, both physically and logically, from the source system. Recovery time and recovery point objectives are set per function, and integrity checks and reconciliations follow any recovery. Entities other than microenterprises keep redundant ICT capacity; microenterprises decide on redundancy from their risk profile (Art. 12(4)). Further duties apply only to specific entity types: central counterparties must be able to recover every transaction in progress when the disruption hit, data reporting service providers keep backup and restoration facilities, and central securities depositories keep a geographically distant secondary processing site (Art. 12(3) and (5)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
Common gap: Backups never restored in a test
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 14 CommunicationWithin their ICT risk management framework, entities keep crisis communication plans to disclose responsibly, at a minimum, major ICT-related incidents and any vulnerabilities to clients, counterparts and, where appropriate, the public; they set communication policies for internal staff and external stakeholders that separate staff involved in response and recovery from staff who only need to be informed, and name at least one person to carry out the incident communication strategy and handle public and media contact. Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.
Common gap: No named spokesperson for ICT incidents
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 17 ICT-related incident management processFinancial entities shall define, establish and implement an ICT-related incident management process to detect, manage and notify ICT-related incidents, including early warning indicators, procedures to identify/track/log/categorise incidents by priority and severity, roles and responsibilities, and communication plans.
Common gap: No structured incident management process
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 24 General requirements for the performance of digital operational resilience testingFinancial entities other than microenterprises set up, keep and periodically review a robust, comprehensive programme of digital operational resilience testing within the ICT risk management framework, applied proportionately under Article 4(2), to assess incident preparedness, find weaknesses and fix them promptly. For those entities the programme follows a risk-based approach reflecting the evolving ICT risk landscape, specific risks and the criticality of assets and services; tests are run by independent internal or external parties (internal testers need sufficient resources and no conflicts of interest); issues found are prioritised, classified and remedied with internal validation that they are closed; and appropriate tests are run at least yearly on every ICT system and application that supports a critical or important function (Art. 24(3) to (6)). Microenterprises are outside these paragraphs and test under Article 25(3), balancing testing resources and time against urgency, risk type and criticality. Entities identified by their competent authority must add TLPT under Article 26.
Common gap: Testing done by the team that built or runs the system
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 25 Testing of ICT tools and systemsThe testing programme provides, proportionately under Article 4(2), for appropriate tests such as penetration and end-to-end tests, performance and compatibility testing, scenario-based tests, review of source code where feasible, scans and vulnerability assessments, analysis of open-source components, gap analyses, assessments of network security, reviews of physical security, and questionnaires with scanning software. Central securities depositories and central counterparties also run vulnerability assessments before deploying or redeploying applications or infrastructure components, and ICT services behind critical or important functions (Art. 25(2)). Microenterprises plan their tests by pairing a risk-based approach with strategic planning, weighing the resources and time spent against urgency, risk type, criticality and their capacity to take calculated risks (Art. 25(3)). The at least yearly testing of systems supporting critical or important functions is an Article 24(6) duty on entities other than microenterprises.
Common gap: Only one test type used for every system
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 28 ICT third-party risk: general principlesFinancial entities manage ICT third-party risk as part of ICT risk inside the ICT risk management framework, remain fully responsible for their obligations when they use ICT services, and apply proportionality according to the nature and importance of ICT dependencies and the criticality of each service. They keep a register of information on all ICT service arrangements at entity, sub-consolidated and consolidated level, distinguishing those supporting critical or important functions; report at least yearly to the authority on new arrangements, provider categories, contract types and services; provide the full register or sections of it on request; and inform the authority in time of planned arrangements for critical or important functions. Before contracting they assess criticality, supervisory conditions, risks including concentration, due diligence and conflicts of interest; they use only providers meeting appropriate security standards, set risk-based audit frequencies, ensure contracts can be terminated in the listed cases, and keep tested exit strategies for services supporting critical or important functions. The ICT third-party risk strategy with its policy on critical or important functions (Art. 28(2)) is required only of entities other than Article 16(1) entities and microenterprises.
Common gap: Register omits intra-group or low-value ICT arrangements
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 30 Key contractual provisionsContracts set out the rights and obligations of both parties in one written document, available on paper or another durable, downloadable format, including the service levels. Every ICT services contract covers at least: the functions and services and whether and how subcontracting is permitted; service and data processing locations, with advance notice of changes; data protection provisions; access, recovery and return of data on insolvency, resolution, discontinuation or termination; service level descriptions; incident assistance at no cost or a cost fixed in advance; cooperation with competent and resolution authorities; termination rights and minimum notice periods; and participation in security awareness training. Contracts for services supporting critical or important functions add: full service levels with quantitative and qualitative targets, notice and reporting duties, provider contingency testing and security measures, participation in the entity's TLPT, unrestricted access, inspection and audit rights for the entity and the authority, and exit strategies with a mandatory transition period (Art. 30(3)). A microenterprise may agree with the provider that its access, inspection and audit rights are handed to an independent party that the provider appoints, from which it can request information and assurance at any time (Art. 30(3), final subparagraph). Standard contractual clauses from public authorities should be considered.
Common gap: Contract silent on data location changes or data return on termination
Source: DORA (Regulation (EU) 2022/2554)
See which clauses your list answers
Paste the list and every document names the clauses behind it, filtered to the regimes that apply to you. Eight documents free, no account.
Build a register