GoToCertifyCompliance Self-Assessment

Mapping table · free · CSV download

DORA to ISO/IEC 27001:2022 + ISO 22301:2019 mapping

This table links 70 DORA requirements, each with its legal reference, to the clauses and controls of ISO/IEC 27001:2022 + ISO 22301:2019: 75 distinct clauses and controls are involved. Use it to see what an existing management system already covers and what DORA adds on top.

Requirements checked against the official texts on 13/11/2026 · version 1.0 · reviewed by GoToCertify's Subject Matter Expert

DORA requirements and the related ISO/IEC 27001:2022 + ISO 22301:2019 clauses and controls

IdLegal referenceRequirementISO/IEC 27001:2022 + ISO 22301:2019
GOV – Governance and management body
GOV-01Art. 5(1)-(2)
Del. Reg. (EU) 2024/1774 Art. 2-3
The management body defines, approves, oversees and is accountable for all arrangements related to the ICT risk management framework.A.5.1 Policies for information security
A.5.4 Management responsibilities
Clause 5 Leadership
GOV-02Art. 5(2)(c); Art. 6(4)
Del. Reg. (EU) 2024/1774 Art. 2
Clear roles and responsibilities for all ICT-related functions are assigned, with a control function responsible for ICT risk that is independent from ICT operations and internal audit (three lines of defence).A.5.2 Information security roles and responsibilities
A.5.3 Segregation of duties
Clause 5 Leadership
GOV-03Art. 5(2)(d)-(g); Art. 6(8)The management body sets the ICT risk tolerance, approves the digital operational resilience strategy, the ICT business continuity policy and the ICT internal audit plan, and allocates appropriate budget.A.5.1 Policies for information security
Clause 6 Planning
GOV-04Art. 5(2)(h)-(i); Art. 28(2)
Del. Reg. (EU) 2024/1773
The management body approves and periodically reviews the policy on the use of ICT third-party services supporting critical or important functions and is informed about the related arrangements and risks.A.5.19 Information security in supplier relationships
Clause 5 Leadership
GOV-05Art. 5(4)
Art. 13(6)
Members of the management body actively keep up to date their knowledge of ICT risk through regular, specific training.A.6.3 Information security awareness, education and training
Clause 7 Support
GOV-06Art. 1; Art. 2; Art. 4
Del. Reg. (EU) 2024/1772, 2024/1773, 2024/1774, 2025/301, 2025/532, 2025/1190; Impl. Reg. (EU) 2024/2956, 2025/302; ESAs Q&As
Legal, regulatory and contractual requirements relevant to digital operational resilience (DORA, RTS/ITS, national implementing acts, sector rules) are identified, kept up to date and allocated to owners.A.5.31 Legal, statutory, regulatory and contractual requirements
Clause 4 Context of the organization
RMF – ICT risk management framework
RMF-01Art. 6(1)-(6)
Del. Reg. (EU) 2024/1774 Chapter I-II
A sound, comprehensive and well-documented ICT risk management framework exists (strategies, policies, procedures, ICT protocols and tools), is reviewed at least yearly and after major incidents, tests or supervisory instructions, and is subject to independent internal audit.A.5.1 Policies for information security
A.5.35 Independent review of information security
A.5.37 Documented operating procedures
Clause 4 Context of the organization
Clause 6 Planning
Clause 9 Performance evaluation
Clause 10 Improvement
RMF-02Art. 6(8)A digital operational resilience strategy sets out how the framework is implemented: risk tolerance, information security objectives, reference architecture, detection and response mechanisms, testing and communication strategy, and, where adopted, the holistic multi-vendor ICT strategy (Art. 6(9), optional).A.5.1 Policies for information security
Clause 6 Planning
RMF-03Art. 6(1); Art. 8(1)-(3), (7)
Del. Reg. (EU) 2024/1774 Art. 3
ICT risks are identified, assessed and treated through a documented methodology: ICT risk register, risk assessment at least yearly and on major changes, legacy ICT systems assessed, residual risks accepted at the appropriate level.A.5.8 Information security in project management
A.5.9 Inventory of information and other associated assets
Clause 6 Planning
Clause 8 Operation
RMF-04Art. 6(1), (3); Art. 5(2)
Del. Reg. (EU) 2024/1774 Art. 3, 27
Resources, tools and documented operating procedures for ICT risk management are in place, with reporting to the management body on ICT risk, incidents and test results at least yearly.A.5.37 Documented operating procedures
Clause 7 Support
Clause 9 Performance evaluation
RMF-05Art. 16
Del. Reg. (EU) 2024/1774 Title III (Art. 28-41)
Entities eligible for the simplified ICT risk management framework (Art. 16) apply the proportionate requirements of Del. Reg. (EU) 2024/1774 Title III: documented framework, governance, identification, protection, business continuity, backup, testing and reporting.A.5.1 Policies for information security
A.5.9 Inventory of information and other associated assets
A.8.13 Information backup
Clause 4 Context of the organization
Clause 8 Operation
RMF-06Art. 6(6)-(7)
Del. Reg. (EU) 2024/1774 Art. 27
Information security, ICT risk and compliance with internal policies are independently reviewed (internal audit, external review) and non-compliance is remediated through a formal follow-up process.A.5.35 Independent review of information security
A.5.36 Compliance with policies, rules and standards for information security
Clause 9 Performance evaluation
Clause 10 Improvement
IDP – Identification, protection and prevention
IDP-01Art. 8(1), (4)-(6)
Del. Reg. (EU) 2024/1774 Art. 4-5
All ICT-supported business functions, roles and responsibilities, information and ICT assets, configurations, interconnections and dependencies on ICT third-party providers are identified, classified and documented in an inventory updated regularly and at every major change.A.5.9 Inventory of information and other associated assets
A.5.12 Classification of information
A.8.9 Configuration management
IDP-02Art. 3(22); Art. 8(1), (3)
Del. Reg. (EU) 2024/1774 Art. 4
Critical or important functions are identified using a documented methodology and the ICT assets, third-party services and interdependencies supporting them are mapped and reviewed at least yearly.A.5.9 Inventory of information and other associated assets
B.8.2 Business impact analysis and risk assessment
IDP-03Art. 9(4)(c)-(d)
Del. Reg. (EU) 2024/1774 Art. 20-21
An information security policy is in place with policies on access control, identity and authentication management, including privileged access and strong authentication, applying least privilege and need-to-know.A.5.15 Access control
A.5.16 Identity management
A.5.17 Authentication information
A.5.18 Access rights
A.8.2 Privileged access rights
A.8.3 Information access restriction
A.8.5 Secure authentication
IDP-04Art. 9(1)-(2), (4)(a)
Del. Reg. (EU) 2024/1774 Art. 8, 11
ICT security tools, policies and procedures minimise the impact of ICT risk: protection against malware, endpoint security, acceptable use rules, and secure configuration of systems.A.5.10 Acceptable use of information and other associated assets
A.8.1 User end point devices
A.8.7 Protection against malware
A.8.9 Configuration management
IDP-05Art. 9(2)-(3), (4)(a)-(b)
Del. Reg. (EU) 2024/1774 Art. 6-7, 13-14
Networks are secured and segmented; connections with third parties are controlled; data in transit and at rest is protected with cryptographic controls under a cryptography and key management policy.A.5.14 Information transfer
A.8.20 Networks security
A.8.21 Security of network services
A.8.22 Segregation of networks
A.8.24 Use of cryptography
IDP-06Art. 9(4)(f)
Del. Reg. (EU) 2024/1774 Art. 10
Vulnerability and patch management processes are in place: scanning frequency proportionate to criticality, prioritisation, tracking of deployment, and handling of third-party and legacy components.A.8.8 Management of technical vulnerabilities
IDP-07Art. 9(4)(e)
Del. Reg. (EU) 2024/1774 Art. 17
ICT change management (including security patches and updates) is documented, risk-assessed, tested, approved and recorded; emergency changes have a controlled path; development, test and production are separated.A.8.31 Separation of development, test and production environments
A.8.32 Change management
IDP-08Art. 9(4)(a), (e); Art. 25(1)
Del. Reg. (EU) 2024/1774 Art. 16
Acquisition, development and maintenance of ICT systems follow a secure development life cycle with security requirements, security testing before deployment, source code review for critical systems and control of outsourced development.A.8.25 Secure development life cycle
A.8.27 Secure system architecture and engineering principles
A.8.29 Security testing in development and acceptance
A.8.30 Outsourced development
IDP-09Art. 9(1)-(2)
Del. Reg. (EU) 2024/1774 Art. 9, 18
Capacity and performance of ICT systems are managed and monitored to ensure availability of critical or important functions; physical and environmental protection of ICT premises is ensured.A.8.6 Capacity management
A.7.1 Physical security perimeters
A.7.4 Physical security monitoring
A.7.5 Protecting against physical and environmental threats
A.7.11 Supporting utilities
IDP-10Art. 11(1)-(2); Art. 28(8)
ISO 22301 cl. 8.3
Business continuity strategies and solutions (people, premises, technology, information, suppliers) are determined from the BIA and risk assessment and are resourced, including alternative solutions for critical ICT third-party dependencies.B.8.3 Business continuity strategies and solutions
A.8.14 Redundancy of information processing facilities
DET – Detection, response and recovery
DET-01Art. 10
Del. Reg. (EU) 2024/1774 Art. 12, 23
Mechanisms promptly detect anomalous activities, ICT network performance issues and ICT-related incidents, with multiple layers of control, alert thresholds and criteria to trigger response, and sufficient resources to monitor user activity and anomalies.A.8.15 Logging
A.8.16 Monitoring activities
A.8.17 Clock synchronization
A.5.7 Threat intelligence
DET-02Art. 11(1)-(2)
Del. Reg. (EU) 2024/1774 Art. 24; ISO 22301 cl. 8.3-8.4
A comprehensive ICT business continuity policy is in place as part of the operational business continuity policy, with documented arrangements, plans, procedures and mechanisms to ensure continuity of critical or important functions and respond to incidents.A.5.29 Information security during disruption
A.5.30 ICT readiness for business continuity
B.8.3 Business continuity strategies and solutions
B.8.4 Business continuity plans and procedures
DET-03Art. 11(2)(a), (5)
Del. Reg. (EU) 2024/1774 Art. 24-25; ISO 22301 cl. 8.2
A business impact analysis of exposures to severe business disruptions is performed, using quantitative and qualitative criteria and severe scenarios, and informs recovery objectives (RTO/RPO) for each critical or important function.B.8.2 Business impact analysis and risk assessment
A.5.30 ICT readiness for business continuity
DET-04Art. 11(3)-(6)
Del. Reg. (EU) 2024/1774 Art. 25-26; ISO 22301 cl. 8.4-8.5
ICT response and recovery plans are documented, approved and cover activation, escalation, recovery of critical functions within RTO/RPO, and dependencies on third parties; they are tested at least yearly and after substantive changes.B.8.4 Business continuity plans and procedures
B.8.5 Exercise programme
A.5.30 ICT readiness for business continuity
DET-05Art. 11(7); Art. 14
Del. Reg. (EU) 2024/1774 Art. 24, 26
A crisis management function and crisis communication procedures are established, with clear internal and external communication during activation of continuity plans.A.5.24 Information security incident management planning and preparation
A.5.29 Information security during disruption
B.8.4 Business continuity plans and procedures
DET-06Art. 11(6), (10)-(11)
ESAs Joint Guidelines on estimation of aggregated annual costs and losses (JC 2024 34); ISO 22301 cl. 8.6
Estimated aggregated annual costs and losses caused by major ICT-related incidents are recorded and reported to the competent authority on request; business continuity capability and documentation are evaluated after exercises, incidents and changes.B.8.6 Evaluation of business continuity documentation and capabilities
A.5.27 Learning from information security incidents
Clause 9 Performance evaluation
BCK – Backup, restoration and redundancy
BCK-01Art. 12(1)-(2)
Del. Reg. (EU) 2024/1774 Art. 8(2)
Backup policies and procedures specify scope and frequency of backups based on criticality of information, with restoration and recovery procedures; backups are tested periodically.A.8.13 Information backup
BCK-02Art. 12(3)-(4)
Del. Reg. (EU) 2024/1774 Art. 8(2), 26
Backup systems are physically and logically segregated from the source system and restoration does not jeopardise the security of network and information systems or data integrity; redundant ICT capacities ensure business needs.A.8.13 Information backup
A.8.14 Redundancy of information processing facilities
BCK-03Art. 12(5)-(7)
Del. Reg. (EU) 2024/1774 Art. 24(2)-(4) (CCPs and CSDs: recovery within 2 hours; trading venues: within or close to 2 hours) and Art. 26
Where a secondary processing site is required or used, it is geographically distant, equipped with resources and capability to ensure continuity of critical functions, and accessible to staff; data integrity is reconciled after recovery.A.8.14 Redundancy of information processing facilities
B.8.3 Business continuity strategies and solutions
LRN – Learning, evolving and communication
LRN-01Art. 13(1)-(3)
Del. Reg. (EU) 2024/1774 Art. 22, 27
Post-incident reviews are conducted after major ICT-related incidents, analysing causes, effectiveness of response and improvements to be implemented, and lessons from incidents and tests are incorporated into the risk framework.A.5.27 Learning from information security incidents
Clause 10 Improvement
LRN-02Art. 13(1), (5), (7)
Del. Reg. (EU) 2024/1774 Art. 10(2)
The organisation gathers information on vulnerabilities and cyber threats, monitors technological developments and reports to the management body on the findings and resulting changes.A.5.7 Threat intelligence
A.5.6 Contact with special interest groups
LRN-03Art. 13(6)
Del. Reg. (EU) 2024/1774 Art. 19
Mandatory ICT security awareness programmes and digital operational resilience training are delivered to all staff and senior management, with complexity commensurate to their remit, extended where appropriate to ICT third-party providers.A.6.3 Information security awareness, education and training
LRN-04Art. 14Crisis communication plans enable responsible disclosure of major ICT-related incidents or vulnerabilities to clients, counterparts and the public, with at least one person responsible for implementing the communication strategy and acting as spokesperson.A.5.24 Information security incident management planning and preparation
A.5.5 Contact with authorities
INC – ICT-related incident management and classification
INC-01Art. 17
Del. Reg. (EU) 2024/1774 Art. 22
An ICT-related incident management process is defined, established and implemented to detect, manage and notify incidents, with early warning indicators, logging of all incidents and significant cyber threats, escalation procedures and root-cause analysis.A.5.24 Information security incident management planning and preparation
A.5.25 Assessment and decision on information security events
A.5.26 Response to information security incidents
A.5.28 Collection of evidence
A.6.8 Information security event reporting
INC-02Art. 18(1)-(2)
Del. Reg. (EU) 2024/1772
ICT-related incidents are classified using the criteria and materiality thresholds of Del. Reg. (EU) 2024/1772 (clients, counterparts and transactions affected; reputational impact; duration and service downtime; geographical spread; data losses; criticality of services; economic impact) to determine major incidents.A.5.25 Assessment and decision on information security events
INC-03Art. 18(1)-(3)
Del. Reg. (EU) 2024/1772 (recurring incidents; classification of significant cyber threats)
Recurring incidents with the same apparent root cause occurring at least twice within 6 months are aggregated and assessed monthly against the materiality thresholds (Del. Reg. (EU) 2024/1772 Art. 8(2); not required of microenterprises and Art. 16(1) entities), and significant cyber threats are classified according to the criticality of the services at risk, the likelihood of materialisation and other criteria.A.5.25 Assessment and decision on information security events
A.5.7 Threat intelligence
INC-04Art. 17(3); Art. 30(2)(f), (3)(c)
Del. Reg. (EU) 2025/532
Where incident management or ICT services are provided by third parties, contracts oblige providers to notify incidents promptly and to assist the financial entity so that classification and reporting deadlines can be met.A.5.20 Addressing information security within supplier agreements
A.5.22 Monitoring, review and change management of supplier services
A.6.8 Information security event reporting
REP – Incident reporting to authorities
REP-01Art. 19(1), (4)
Del. Reg. (EU) 2025/301 Art. 1-5 (Art. 5: time limits); Impl. Reg. (EU) 2025/302
Major ICT-related incidents are reported to the competent authority within the time limits of Del. Reg. (EU) 2025/301: initial notification within 4 hours from classification as major and no later than 24 hours from awareness; intermediate report within 72 hours from the initial notification; final report within one month from the intermediate report (or last updated intermediate report).A.5.5 Contact with authorities
A.5.26 Response to information security incidents
REP-02Art. 20
Impl. Reg. (EU) 2025/302; ESAs operational instructions on DORA incident reporting (16/09/2026); national competent authority instructions
Reports use the standard forms, templates and procedures of Impl. Reg. (EU) 2025/302 and the submission channel of the competent authority (the channel, templates and format established at national level), with data fields completed and updated at each stage.A.5.5 Contact with authorities
A.5.33 Protection of records
REP-03Art. 19(3)Where a major ICT-related incident has an impact on clients' financial interests, clients are informed without undue delay of the incident and of mitigating measures; clients are also informed of significant cyber threats and protective measures where relevant.A.5.24 Information security incident management planning and preparation
A.5.14 Information transfer
REP-04Art. 19(2)
Del. Reg. (EU) 2025/301 Art. 6; Impl. Reg. (EU) 2025/302 Annex
Significant cyber threats may be notified to the competent authority on a voluntary basis using the ITS template, where the threat is deemed relevant to the financial system, service users or clients.A.5.7 Threat intelligence
A.5.5 Contact with authorities
REP-05Art. 19(5); Art. 1(2); Art. 23
Digital Omnibus proposal COM(2025) 837 (single entry point, pending); GDPR Art. 33
Reporting obligations under other regimes (GDPR personal data breaches, PSD2 major operational or security incidents now reported under DORA, NIS2 where relevant, national CSIRTs, payment schemes, Member State requirements) are mapped and coordinated with DORA reporting; where reporting is outsourced to an ICT third-party provider (Art. 19(5)), the entity remains fully responsible for compliance.A.5.31 Legal, statutory, regulatory and contractual requirements
A.5.5 Contact with authorities
TST – Digital operational resilience testing
TST-01Art. 24A sound and comprehensive digital operational resilience testing programme is in place as part of the ICT risk framework, risk-based, performed by independent parties (internal or external), with procedures to prioritise, classify and remediate all issues revealed.A.5.35 Independent review of information security
A.8.29 Security testing in development and acceptance
Clause 9 Performance evaluation
TST-02Art. 24(6); Art. 25(1)-(2)Appropriate tests are performed on all ICT systems and applications supporting critical or important functions at least yearly: vulnerability assessments and scans, open source analyses, network security assessments, gap analyses, physical security reviews, questionnaires and scanning software, source code reviews, scenario-based tests, compatibility, performance and end-to-end testing, penetration testing.A.8.8 Management of technical vulnerabilities
A.8.29 Security testing in development and acceptance
A.8.34 Protection of information systems during audit testing
A.7.1 Physical security perimeters
TST-03Art. 26
Del. Reg. (EU) 2025/1190; TIBER-EU framework (ECB, updated January 2025)
Financial entities identified by the competent authority carry out threat-led penetration testing (TLPT) at least every three years on live production systems supporting critical or important functions, following Del. Reg. (EU) 2025/1190 (TIBER-EU aligned), with the summary of findings, remediation plans and documentation sent to the authority, which issues the attestation (Art. 26(6)-(7)).A.8.29 Security testing in development and acceptance
A.8.34 Protection of information systems during audit testing
A.5.5 Contact with authorities
TST-04Art. 26(8); Art. 27
Del. Reg. (EU) 2025/1190 Art. 7 (selection of TLPT providers), Art. 15 (internal testers)
Testers used for TLPT meet the requirements of Art. 27 (suitability, reputation, technical and organisational capabilities, certifications, professional indemnity insurance); internal testers are used only with the approval of the TLPT authority, with an external threat intelligence provider, under an internal tester policy and with external testers contracted at least every third test.A.5.19 Information security in supplier relationships
A.5.20 Addressing information security within supplier agreements
TST-05Art. 24(5); Art. 26(6); Art. 13(3)Test results (including TLPT) feed the ICT risk framework: findings are prioritised, remediation is verified, and lessons are incorporated into the resilience strategy, detection capabilities and training.A.5.27 Learning from information security incidents
Clause 10 Improvement
TST-06Art. 11(6); Art. 25(1)
ISO 22301 cl. 8.5-8.6
An exercise programme validates business continuity and ICT response and recovery arrangements over time: scenario-based exercises, technical failover tests and crisis simulations, each with objectives, reports and post-exercise review.B.8.5 Exercise programme
B.8.6 Evaluation of business continuity documentation and capabilities
TPS – ICT third-party risk: strategy and register
TPS-01Art. 28(1)
Del. Reg. (EU) 2024/1773
ICT third-party risk is managed as an integral part of ICT risk within the framework, applying proportionality and taking into account the nature, scale, complexity and criticality of ICT dependencies; the entity remains fully responsible for compliance with DORA when using ICT third parties.A.5.19 Information security in supplier relationships
A.5.21 Managing information security in the ICT supply chain
TPS-02Art. 28(2); Art. 6(9)
Del. Reg. (EU) 2024/1773
A strategy on ICT third-party risk, including a policy on the use of ICT services supporting critical or important functions, is adopted and reviewed regularly, including a multi-vendor approach and group-level application where relevant.A.5.19 Information security in supplier relationships
A.5.23 Information security for use of cloud services
Clause 6 Planning
TPS-03Art. 28(3)
Impl. Reg. (EU) 2024/2956; ESAs data point model and validation rules
A register of information on all contractual arrangements on the use of ICT services is maintained at entity, sub-consolidated and consolidated level, distinguishing arrangements supporting critical or important functions, following the templates of Impl. Reg. (EU) 2024/2956.A.5.9 Inventory of information and other associated assets
A.5.19 Information security in supplier relationships
A.5.33 Protection of records
TPS-04Art. 28(3)
Impl. Reg. (EU) 2024/2956; competent authority instructions
The register of information is made available to the competent authority on request (Art. 28(3)) and, in practice, collected yearly within the deadlines set by the authority (2026 exercise: reference date 31/12/2025, national deadlines set by each authority ahead of 31 March 2026, when authorities forward registers to the ESAs; next exercise Q1 2027), together with the yearly information on the number of new arrangements, categories of providers, type of contracts and services, and on arrangements supporting critical or important functions.A.5.5 Contact with authorities
A.5.31 Legal, statutory, regulatory and contractual requirements
TPS-05Art. 28(3), fifth subparagraph
Competent authority notification templates
The competent authority is informed in a timely manner of any planned contractual arrangement on the use of ICT services supporting critical or important functions and when a function becomes critical or important.A.5.5 Contact with authorities
A.5.22 Monitoring, review and change management of supplier services
TPS-06Art. 28(4); Art. 29
Del. Reg. (EU) 2024/1773 Art. 5-6; Del. Reg. (EU) 2025/532 Art. 3
Before entering into an arrangement, the entity assesses whether it covers a critical or important function, the supervisory conditions, all relevant risks including concentration risk, and performs due diligence on the provider (suitability, security, financial soundness, location, subcontracting), and identifies conflicts of interest.A.5.19 Information security in supplier relationships
A.5.21 Managing information security in the ICT supply chain
A.5.23 Information security for use of cloud services
TPS-07Art. 29
Del. Reg. (EU) 2025/532
ICT concentration risk is assessed at entity and group level: dependence on non-substitutable providers, multiple arrangements with the same or closely connected providers, and the risks of long or complex subcontracting chains, with mitigation (multi-vendor, exit options) where needed.A.5.21 Managing information security in the ICT supply chain
A.5.23 Information security for use of cloud services
B.8.3 Business continuity strategies and solutions
TPS-08Art. 28(6)-(7); Art. 30(3)
Del. Reg. (EU) 2024/1773 Art. 9
ICT third-party arrangements are monitored throughout their life (performance against SLAs, security, incidents, audits, changes) with periodic reviews and risk re-assessment, and contractual termination rights allow the arrangement to be terminated where the provider breaches laws or contracts, shows weaknesses in ICT risk management, or where the authority can no longer supervise the entity effectively.A.5.22 Monitoring, review and change management of supplier services
TPC – Contracts, subcontracting and exit
TPC-01Art. 30(1)-(2)
ESAs Q&As (EBA/GL/2026/09 on third-party risk covers non-ICT services only)
All contractual arrangements include the minimum provisions of Art. 30(2): description of functions and services, locations of services and data, data protection provisions, access, recovery and return of data on insolvency or termination, service level descriptions, assistance in incidents, cooperation with authorities, termination rights, and participation in awareness programmes.A.5.20 Addressing information security within supplier agreements
TPC-02Art. 30(3)
Del. Reg. (EU) 2024/1773; Del. Reg. (EU) 2025/532
Contracts for ICT services supporting critical or important functions additionally include: full service level descriptions with quantitative and qualitative performance targets, notice periods and reporting obligations, obligations to implement and test contingency plans and security measures, participation in TLPT, unrestricted rights of access, inspection and audit for the entity and the competent authorities, cooperation in oversight, and exit strategy provisions with a mandatory transition period.A.5.20 Addressing information security within supplier agreements
A.5.22 Monitoring, review and change management of supplier services
A.8.34 Protection of information systems during audit testing
TPC-03Art. 30(2)(a), (5); Art. 28(4)(c)
Del. Reg. (EU) 2025/532 (in force 22/07/2025)
Subcontracting of ICT services supporting critical or important functions follows Del. Reg. (EU) 2025/532: risk assessment of the chain, due diligence on subcontractors, contractual conditions on which services may be subcontracted, prior notification of material changes with right to object or terminate, and monitoring of the whole chain.A.5.21 Managing information security in the ICT supply chain
A.5.20 Addressing information security within supplier agreements
A.5.22 Monitoring, review and change management of supplier services
TPC-04Art. 28(8)
Del. Reg. (EU) 2024/1773 Art. 10
Exit strategies are in place for ICT services supporting critical or important functions, with documented, tested exit plans covering transition to alternative providers or reintegration, identification of alternative solutions, and continuity during the transition without disruption or detriment to clients and compliance.A.5.30 ICT readiness for business continuity
B.8.3 Business continuity strategies and solutions
B.8.5 Exercise programme
TPC-06Art. 28; Art. 30
Del. Reg. (EU) 2024/1773 (EIOPA cloud and ICT guidelines withdrawn from 17/01/2025; ESMA cloud outsourcing guidelines no longer apply to entities subject to DORA)
Information security requirements for cloud services (shared responsibility model, data location, encryption and key management, access to logs, exit and portability) are defined in the policy and in cloud contracts, and cloud configurations are monitored.A.5.23 Information security for use of cloud services
A.8.9 Configuration management
CTP – Critical ICT third-party providers and oversight
CTP-01Art. 31; Art. 35; Art. 42
Del. Reg. (EU) 2024/1502 (criticality criteria); ESAs list of designated CTPPs (18/11/2025); ESAs Guide on DORA oversight activities (JC 2025 29, 15/07/2025)
The entity knows which of its ICT third-party providers are designated as critical ICT third-party providers (CTPPs) by the ESAs (first list of 19 providers published 18/11/2025) and monitors Lead Overseer recommendations, taking account of the risks of using a CTPP that does not address them, including possible supervisory measures (suspension or termination).A.5.21 Managing information security in the ICT supply chain
A.5.22 Monitoring, review and change management of supplier services
A.5.6 Contact with special interest groups
CTP-02Art. 31(12); Art. 30(3)(e); Art. 37-39
Del. Reg. (EU) 2025/420 (joint examination teams); Del. Reg. (EU) 2024/1505 (oversight fees)
The entity checks that any CTPP established in a third country sets up a subsidiary in the Union within 12 months of designation (Art. 31(12); for the providers on the list published on 18/11/2025 the 12 months run from each individual designation, so they end no later than 18/11/2026), since financial entities may only use such a CTPP once the subsidiary exists, and verifies that cooperation with the Lead Overseer is contractually supported (information, access, inspections).A.5.20 Addressing information security within supplier agreements
A.5.21 Managing information security in the ICT supply chain
CTP-03Art. 31(11); Art. 33; Art. 35; Art. 30
ESAs Guide on DORA oversight activities; Del. Reg. (EU) 2024/1502
ICT third-party providers serving financial entities (whether designated or not) organise themselves to support DORA compliance of their clients: mapping of financial-sector customers and critical functions supported, incident notification capability, participation in TLPT and audits, exit support, and, if designated, a governance and risk management framework suitable for Lead Overseer oversight, with the ability to apply for voluntary designation (opt-in).A.5.19 Information security in supplier relationships
A.5.24 Information security incident management planning and preparation
A.5.31 Legal, statutory, regulatory and contractual requirements
ISH – Information sharing, authorities and interplay
ISH-01Art. 45
GDPR; national FS-ISAC / CSIRT arrangements
Participation in cyber threat information and intelligence sharing arrangements (indicators of compromise, tactics, techniques, procedures, alerts, configuration tools) is assessed and, where joined, governed by agreements that protect sensitive information and comply with competition and data protection rules; the competent authority is notified of participation and withdrawal.A.5.6 Contact with special interest groups
A.5.7 Threat intelligence
ISH-02Art. 1(2); Recital 16; Directive (EU) 2022/2555 Art. 4 and Recital 28
National NIS2 transposition acts
The interplay with NIS2 is documented: for financial entities covered by DORA, DORA applies as lex specialis for ICT risk management and incident reporting, while national NIS2 registration or information duties and CSIRT cooperation are handled where applicable; ICT third-party providers that are also NIS2 essential or important entities manage both regimes.A.5.31 Legal, statutory, regulatory and contractual requirements
A.5.5 Contact with authorities
ISH-03Art. 46-54; Art. 50
Competent authority supervisory priorities (2025-2026: ICT risk management, register quality, incident reporting)
Relations with the competent authority, the TLPT authority, the Lead Overseer (for CTPPs) and national CSIRTs are structured: single points of contact, portal access, procedure to answer information requests, on-site inspections and supervisory measures, and tracking of penalties and remedial measures risk.A.5.5 Contact with authorities
Clause 4 Context of the organization
ISH-04Art. 28(3); Art. 30; Art. 3(20); Recital 63
Del. Reg. (EU) 2025/532 (group application); Del. Reg. (EU) 2024/1773 Art. 2
Where the entity is part of a group, DORA responsibilities are allocated between parent and subsidiaries (framework, register at consolidated level, intra-group ICT services treated as third-party arrangements, group-level exit and concentration analyses), and each entity remains individually responsible for compliance.A.5.2 Information security roles and responsibilities
A.5.19 Information security in supplier relationships
Clause 4 Context of the organization

Reverse table: ISO/IEC 27001:2022 + ISO 22301:2019 clauses and controls and the DORA provisions they support

Clause or controlLegal referencesRequirement ids
Clause 4 Context of the organizationArt. 1; Art. 2; Art. 4; Art. 6(1)-(6); Art. 16; Art. 46-54; Art. 50; Art. 28(3); Art. 30; Art. 3(20); Recital 63GOV-06, RMF-01, RMF-05, ISH-03, ISH-04
Clause 5 LeadershipArt. 5(1)-(2); Art. 5(2)(c); Art. 6(4); Art. 5(2)(h)-(i); Art. 28(2)GOV-01, GOV-02, GOV-04
Clause 6 PlanningArt. 5(2)(d)-(g); Art. 6(8); Art. 6(1)-(6); Art. 6(8); Art. 6(1); Art. 8(1)-(3), (7); Art. 28(2); Art. 6(9)GOV-03, RMF-01, RMF-02, RMF-03, TPS-02
Clause 7 SupportArt. 5(4); Art. 6(1), (3); Art. 5(2)GOV-05, RMF-04
Clause 8 OperationArt. 6(1); Art. 8(1)-(3), (7); Art. 16RMF-03, RMF-05
Clause 9 Performance evaluationArt. 6(1)-(6); Art. 6(1), (3); Art. 5(2); Art. 6(6)-(7); Art. 11(6), (10)-(11); Art. 24RMF-01, RMF-04, RMF-06, DET-06, TST-01
Clause 10 ImprovementArt. 6(1)-(6); Art. 6(6)-(7); Art. 13(1)-(3); Art. 24(5); Art. 26(6); Art. 13(3)RMF-01, RMF-06, LRN-01, TST-05
A.5.1 Policies for information securityArt. 5(1)-(2); Art. 5(2)(d)-(g); Art. 6(8); Art. 6(1)-(6); Art. 6(8); Art. 16GOV-01, GOV-03, RMF-01, RMF-02, RMF-05
A.5.2 Information security roles and responsibilitiesArt. 5(2)(c); Art. 6(4); Art. 28(3); Art. 30; Art. 3(20); Recital 63GOV-02, ISH-04
A.5.3 Segregation of dutiesArt. 5(2)(c); Art. 6(4)GOV-02
A.5.4 Management responsibilitiesArt. 5(1)-(2)GOV-01
A.5.5 Contact with authoritiesArt. 14; Art. 19(1), (4); Art. 20; Art. 19(2); Art. 19(5); Art. 1(2); Art. 23; Art. 26; Art. 28(3); Art. 28(3), fifth subparagraph; Art. 1(2); Recital 16; Directive (EU) 2022/2555 Art. 4 and Recital 28; Art. 46-54; Art. 50LRN-04, REP-01, REP-02, REP-04, REP-05, TST-03, TPS-04, TPS-05, ISH-02, ISH-03
A.5.6 Contact with special interest groupsArt. 13(1), (5), (7); Art. 31; Art. 35; Art. 42; Art. 45LRN-02, CTP-01, ISH-01
A.5.7 Threat intelligenceArt. 10; Art. 13(1), (5), (7); Art. 18(1)-(3); Art. 19(2); Art. 45DET-01, LRN-02, INC-03, REP-04, ISH-01
A.5.8 Information security in project managementArt. 6(1); Art. 8(1)-(3), (7)RMF-03
A.5.9 Inventory of information and other associated assetsArt. 6(1); Art. 8(1)-(3), (7); Art. 16; Art. 8(1), (4)-(6); Art. 3(22); Art. 8(1), (3); Art. 28(3)RMF-03, RMF-05, IDP-01, IDP-02, TPS-03
A.5.10 Acceptable use of information and other associated assetsArt. 9(1)-(2), (4)(a)IDP-04
A.5.12 Classification of informationArt. 8(1), (4)-(6)IDP-01
A.5.14 Information transferArt. 9(2)-(3), (4)(a)-(b); Art. 19(3)IDP-05, REP-03
A.5.15 Access controlArt. 9(4)(c)-(d)IDP-03
A.5.16 Identity managementArt. 9(4)(c)-(d)IDP-03
A.5.17 Authentication informationArt. 9(4)(c)-(d)IDP-03
A.5.18 Access rightsArt. 9(4)(c)-(d)IDP-03
A.5.19 Information security in supplier relationshipsArt. 5(2)(h)-(i); Art. 28(2); Art. 26(8); Art. 27; Art. 28(1); Art. 28(2); Art. 6(9); Art. 28(3); Art. 28(4); Art. 29; Art. 31(11); Art. 33; Art. 35; Art. 30; Art. 28(3); Art. 30; Art. 3(20); Recital 63GOV-04, TST-04, TPS-01, TPS-02, TPS-03, TPS-06, CTP-03, ISH-04
A.5.20 Addressing information security within supplier agreementsArt. 17(3); Art. 30(2)(f), (3)(c); Art. 26(8); Art. 27; Art. 30(1)-(2); Art. 30(3); Art. 30(2)(a), (5); Art. 28(4)(c); Art. 31(12); Art. 30(3)(e); Art. 37-39INC-04, TST-04, TPC-01, TPC-02, TPC-03, CTP-02
A.5.21 Managing information security in the ICT supply chainArt. 28(1); Art. 28(4); Art. 29; Art. 29; Art. 30(2)(a), (5); Art. 28(4)(c); Art. 31; Art. 35; Art. 42; Art. 31(12); Art. 30(3)(e); Art. 37-39TPS-01, TPS-06, TPS-07, TPC-03, CTP-01, CTP-02
A.5.22 Monitoring, review and change management of supplier servicesArt. 17(3); Art. 30(2)(f), (3)(c); Art. 28(3), fifth subparagraph; Art. 28(6)-(7); Art. 30(3); Art. 30(3); Art. 30(2)(a), (5); Art. 28(4)(c); Art. 31; Art. 35; Art. 42INC-04, TPS-05, TPS-08, TPC-02, TPC-03, CTP-01
A.5.23 Information security for use of cloud servicesArt. 28(2); Art. 6(9); Art. 28(4); Art. 29; Art. 29; Art. 28; Art. 30TPS-02, TPS-06, TPS-07, TPC-06
A.5.24 Information security incident management planning and preparationArt. 11(7); Art. 14; Art. 14; Art. 17; Art. 19(3); Art. 31(11); Art. 33; Art. 35; Art. 30DET-05, LRN-04, INC-01, REP-03, CTP-03
A.5.25 Assessment and decision on information security eventsArt. 17; Art. 18(1)-(2); Art. 18(1)-(3)INC-01, INC-02, INC-03
A.5.26 Response to information security incidentsArt. 17; Art. 19(1), (4)INC-01, REP-01
A.5.27 Learning from information security incidentsArt. 11(6), (10)-(11); Art. 13(1)-(3); Art. 24(5); Art. 26(6); Art. 13(3)DET-06, LRN-01, TST-05
A.5.28 Collection of evidenceArt. 17INC-01
A.5.29 Information security during disruptionArt. 11(1)-(2); Art. 11(7); Art. 14DET-02, DET-05
A.5.30 ICT readiness for business continuityArt. 11(1)-(2); Art. 11(2)(a), (5); Art. 11(3)-(6); Art. 28(8)DET-02, DET-03, DET-04, TPC-04
A.5.31 Legal, statutory, regulatory and contractual requirementsArt. 1; Art. 2; Art. 4; Art. 19(5); Art. 1(2); Art. 23; Art. 28(3); Art. 31(11); Art. 33; Art. 35; Art. 30; Art. 1(2); Recital 16; Directive (EU) 2022/2555 Art. 4 and Recital 28GOV-06, REP-05, TPS-04, CTP-03, ISH-02
A.5.33 Protection of recordsArt. 20; Art. 28(3)REP-02, TPS-03
A.5.35 Independent review of information securityArt. 6(1)-(6); Art. 6(6)-(7); Art. 24RMF-01, RMF-06, TST-01
A.5.36 Compliance with policies, rules and standards for information securityArt. 6(6)-(7)RMF-06
A.5.37 Documented operating proceduresArt. 6(1)-(6); Art. 6(1), (3); Art. 5(2)RMF-01, RMF-04
A.6.3 Information security awareness, education and trainingArt. 5(4); Art. 13(6)GOV-05, LRN-03
A.6.8 Information security event reportingArt. 17; Art. 17(3); Art. 30(2)(f), (3)(c)INC-01, INC-04
A.7.1 Physical security perimetersArt. 9(1)-(2); Art. 24(6); Art. 25(1)-(2)IDP-09, TST-02
A.7.4 Physical security monitoringArt. 9(1)-(2)IDP-09
A.7.5 Protecting against physical and environmental threatsArt. 9(1)-(2)IDP-09
A.7.11 Supporting utilitiesArt. 9(1)-(2)IDP-09
A.8.1 User end point devicesArt. 9(1)-(2), (4)(a)IDP-04
A.8.2 Privileged access rightsArt. 9(4)(c)-(d)IDP-03
A.8.3 Information access restrictionArt. 9(4)(c)-(d)IDP-03
A.8.5 Secure authenticationArt. 9(4)(c)-(d)IDP-03
A.8.6 Capacity managementArt. 9(1)-(2)IDP-09
A.8.7 Protection against malwareArt. 9(1)-(2), (4)(a)IDP-04
A.8.8 Management of technical vulnerabilitiesArt. 9(4)(f); Art. 24(6); Art. 25(1)-(2)IDP-06, TST-02
A.8.9 Configuration managementArt. 8(1), (4)-(6); Art. 9(1)-(2), (4)(a); Art. 28; Art. 30IDP-01, IDP-04, TPC-06
A.8.13 Information backupArt. 16; Art. 12(1)-(2); Art. 12(3)-(4)RMF-05, BCK-01, BCK-02
A.8.14 Redundancy of information processing facilitiesArt. 11(1)-(2); Art. 28(8); Art. 12(3)-(4); Art. 12(5)-(7)IDP-10, BCK-02, BCK-03
A.8.15 LoggingArt. 10DET-01
A.8.16 Monitoring activitiesArt. 10DET-01
A.8.17 Clock synchronizationArt. 10DET-01
A.8.20 Networks securityArt. 9(2)-(3), (4)(a)-(b)IDP-05
A.8.21 Security of network servicesArt. 9(2)-(3), (4)(a)-(b)IDP-05
A.8.22 Segregation of networksArt. 9(2)-(3), (4)(a)-(b)IDP-05
A.8.24 Use of cryptographyArt. 9(2)-(3), (4)(a)-(b)IDP-05
A.8.25 Secure development life cycleArt. 9(4)(a), (e); Art. 25(1)IDP-08
A.8.27 Secure system architecture and engineering principlesArt. 9(4)(a), (e); Art. 25(1)IDP-08
A.8.29 Security testing in development and acceptanceArt. 9(4)(a), (e); Art. 25(1); Art. 24; Art. 24(6); Art. 25(1)-(2); Art. 26IDP-08, TST-01, TST-02, TST-03
A.8.30 Outsourced developmentArt. 9(4)(a), (e); Art. 25(1)IDP-08
A.8.31 Separation of development, test and production environmentsArt. 9(4)(e)IDP-07
A.8.32 Change managementArt. 9(4)(e)IDP-07
A.8.34 Protection of information systems during audit testingArt. 24(6); Art. 25(1)-(2); Art. 26; Art. 30(3)TST-02, TST-03, TPC-02
B.8.2 Business impact analysis and risk assessmentArt. 3(22); Art. 8(1), (3); Art. 11(2)(a), (5)IDP-02, DET-03
B.8.3 Business continuity strategies and solutionsArt. 11(1)-(2); Art. 28(8); Art. 11(1)-(2); Art. 12(5)-(7); Art. 29; Art. 28(8)IDP-10, DET-02, BCK-03, TPS-07, TPC-04
B.8.4 Business continuity plans and proceduresArt. 11(1)-(2); Art. 11(3)-(6); Art. 11(7); Art. 14DET-02, DET-04, DET-05
B.8.5 Exercise programmeArt. 11(3)-(6); Art. 11(6); Art. 25(1); Art. 28(8)DET-04, TST-06, TPC-04
B.8.6 Evaluation of business continuity documentation and capabilitiesArt. 11(6), (10)-(11); Art. 11(6); Art. 25(1)DET-06, TST-06

Frequently asked questions

Does ISO/IEC 27001:2022 certification make an organisation DORA compliant?

No. The standard covers a large part of the organisational and technical measures, but DORA adds legal obligations that a management-system standard does not contain, such as notifications to authorities, legal deadlines and sector-specific duties. The table shows, requirement by requirement, which clauses and controls help and where the legal reference goes beyond them.

How was the mapping built?

The links are GoToCertify's editorial analysis of each DORA article and of the related regulatory and implementing technical standards. It is an aid for gap analysis, not an official mapping issued by ISO or by an EU institution.

Can I reuse the table?

Yes: the CSV file can be downloaded from this page and reused with a link to the source. To score your own organisation against each row, use the free DORA self-assessment.

The links are GoToCertify's editorial analysis of each DORA article and of the related regulatory and implementing technical standards. Control titles are short identifiers of the controls of the standard; the standard itself is published by ISO and must be obtained from ISO or a national standards body. Self-assessment tool for information purposes only; it does not constitute legal advice. References and dates must be verified against the official texts (EUR-Lex, ESAs, competent authorities). No data from this assessment is transmitted to GoToCertify. © 2026 GoToCertify.