cm/controlmapping
Sources
Comparison

NIS2 vs DORA

NIS2 Implementing Regulation (EU) 2024/2690  ·  DORA (Regulation (EU) 2022/2554)  ·  data 2026-10-27

Requirement-level comparison of NIS2 Implementing Regulation (EU) 2024/2690 and DORA (Regulation (EU) 2022/2554), in both directions, derived from published crosswalks and ControlMapping's curated topics.

Have NIS2 → need DORA

22 reqs 20 mapped · 1 loosely related · 1 no mapping Open in gap view →

Of 22 DORA (Regulation (EU) 2022/2554) requirements, 20 map to something in NIS2, 1 are only loosely related, and 1 have no mapping in our data.

DORA here means the articles that bind financial entities, mapped editorially at paragraph level. The technical standards that add detail, such as Delegated Regulation (EU) 2024/1774, are not mapped, so technical topics they cover show no link.

Likely new work: DORA requirements with no mapping to NIS2 (1)
DORARequirementMatchNIS2Evidence
Chapter II: ICT risk management · 1
Art.7ICT systems, protocols and toolsNo mapping in our data—No mapping to NIS2 in our data.
Check these: only loosely related (a shared CSF outcome, not a mapping) (1)
DORARequirementMatchNIS2Evidence
Chapter VI: Information sharing · 1
Art.45Information-sharing arrangements on cyber threat information and intelligenceLoosely related2.14.36.10Only shares CSF ID.RA-02, ID.RA-03, DE.AE-07: related, not a mapping
Mapped (20)
DORARequirementMatchNIS2Evidence
Chapter II: ICT risk management · 10
Art.5Governance and organisationEditorial2.17.11.2+4Same topic: Risk Management, Roles & Responsibilities (editorial pick)
Art.6ICT risk management frameworkEditorial2.17.113.1+5Same topic: Risk Management, Physical Security (editorial pick)
Art.8IdentificationEditorial12.112.42.1+2Same topic: Data Classification, Asset Management, Risk Assessment (editorial pick)
Art.9Protection and preventionEditorial3.212.212.3+12Same topic: Cont. Monitoring, Data Protection (editorial pick)
Art.10DetectionEditorial3.23.410.2+1Same topic: Intrusion Detection, Anomaly Detection, Insider Threat (editorial pick)
Art.11Response and recoveryEditorial4.14.33.1+1Same topic: Business Continuity, Incident Response (editorial pick)
Art.12Backup policies and procedures, restoration and recovery procedures and methodsEditorial4.24.1Same topic: Backup & Recovery, Disaster Recovery (editorial pick)
Art.13Learning and evolvingEditorial3.53.68.1+1Same topic: Forensics, Lessons Learned, Awareness & Training (editorial pick)
Art.14CommunicationEditorial4.3Same topic: Communication (editorial pick)
Art.16Simplified ICT risk management frameworkEditorial2.17.1Same topic: Risk Management (editorial pick)
Chapter III: ICT-related incidents · 3
Art.17ICT-related incident management processEditorial3.13.54.3Same topic: Incident Response, Communication (editorial pick)
Art.18Classification of ICT-related incidents and cyber threatsEditorial3.13.33.5Same topic: Incident Response, Reporting (editorial pick)
Art.19Reporting of major ICT-related incidents and voluntary notification of significant cyber threatsEditorial3.3Same topic: Reporting (editorial pick)
Chapter IV: Resilience testing · 4
Art.24General requirements for the performance of digital operational resilience testingEditorial2.17.1Same topic: Risk Management (editorial pick)
Art.25Testing of ICT tools and systemsEditorial6.56.10Same topic: Vulnerability Mgmt (editorial pick)
Art.26Advanced testing of ICT tools, systems and processes based on TLPTEditorial6.56.10Same topic: Vulnerability Mgmt (editorial pick)
Art.27Requirements for testers for the carrying out of TLPTEditorial6.56.10Same topic: Vulnerability Mgmt (editorial pick)
Chapter V: ICT third-party risk · 3
Art.28General principlesEditorial5.16.15.2Same topic: Supply Chain Risk, Vendor Risk Mgmt (editorial pick)
Art.29Preliminary assessment of ICT concentration risk at entity levelEditorial5.16.1Same topic: Supply Chain Risk (editorial pick)
Art.30Key contractual provisionsEditorial5.15.26.1+1Same topic: Vendor Risk Mgmt, Cloud Security (editorial pick)

Have DORA → need NIS2

49 reqs 44 mapped · 5 loosely related · 0 no mapping Open in gap view →

Of 49 NIS2 Implementing Regulation (EU) 2024/2690 requirements, 44 map to something in DORA, 5 are only loosely related, and 0 have no mapping in our data.

NIS2 here is the technical measures of Implementing Regulation (EU) 2024/2690, which applies directly to digital-infrastructure and ICT-service providers; other NIS2 entities follow their country's transposition of Article 21. Incident reporting deadlines (Article 23) are not in scope. ENISA's mapping is non-binding.

Check these: only loosely related (a shared CSF outcome, not a mapping) (5)
NIS2RequirementMatchDORAEvidence
6. Security in acquisition, development and maintenance · 3
6.2Secure development life cycleLoosely relatedArt.8(1)Art.8(4)Art.8(6)Only shares CSF ID.AM-08: related, not a mapping
6.3Configuration managementLoosely relatedArt.28(8)Art.30(2)Only shares CSF PR.PS-01: related, not a mapping
6.9Protection against malicious and unauthorised softwareLoosely relatedArt.9(1)Art.10(1)Art.10(3)+1Only shares CSF DE.CM-01, DE.CM-09: related, not a mapping
10. Human resources security · 2
10.1Human resources securityLoosely relatedArt.5(4)Art.10(3)Art.13(6)Only shares CSF PR.AT-02, GV.RR-04: related, not a mapping
10.3Termination or change of employment proceduresLoosely relatedArt.10(3)Only shares CSF GV.RR-04: related, not a mapping
Mapped (44)
NIS2RequirementMatchDORAEvidence
1. Policy on the security of network and information systems · 2
1.1Policy on the security of network and information systemsEditorialArt.5(2)(b)Art.6(5)Art.9(4)(a)Same topic: Governance Policy (editorial pick)
1.2Roles, responsibilities and authoritiesEditorialArt.5(2)(c)Art.5(3)Art.6(4)Same topic: Roles & Responsibilities (editorial pick)
2. Risk management policy · 3
2.1Risk management frameworkEditorialArt.5(2)(a)Art.6(1)Art.6(8)+5Same topic: Risk Management (editorial pick)
2.2Compliance monitoringEditorialArt.5(2)(f)Art.6(6)Art.6(7)Same topic: Compliance (editorial pick)
2.3Independent review of information and network securityEditorialArt.5(2)(f)Art.6(6)Art.6(7)Same topic: Compliance (editorial pick)
3. Incident handling · 6
3.1Incident handling policyEditorialArt.11(2)(b)Art.17(1)Art.17(3)+1Same topic: Incident Response (editorial pick)
3.2Monitoring and loggingEditorialArt.9(1)Art.10(1)Art.10(2)+1Same topic: Cont. Monitoring, Intrusion Detection, SIEM / SOC (editorial pick)
3.3Event reportingEditorialArt.18(1)Art.19(1)Art.19(3)+1Same topic: Reporting (editorial pick)
3.4Event assessment and classificationEditorialArt.10(1)Art.10(2)Art.10(3)Same topic: Anomaly Detection, SIEM / SOC (editorial pick)
3.5Incident responseEditorialArt.11(2)(b)Art.11(2)(c)Art.13(2)+5Same topic: Incident Response, Mitigation, Forensics (editorial pick)
3.6Post-incident reviewsEditorialArt.13(2)Art.13(3)Same topic: Lessons Learned (editorial pick)
4. Business continuity and crisis management · 3
4.1Business continuity and disaster recovery planEditorialArt.11(1)Art.11(3)Art.11(4)+3Same topic: Business Continuity, Recovery Planning (editorial pick)
4.2Backup managementEditorialArt.11(6)Art.12(1)Art.12(2)+2Same topic: Disaster Recovery, Backup & Recovery (editorial pick)
4.3Crisis managementEditorialArt.11(1)Art.11(2)(e)Art.11(4)+5Same topic: Business Continuity, Comms & Restore (editorial pick)
5. Supply chain security · 2
5.1Supply chain security policyEditorialArt.28(2)Art.28(3)Art.28(4)+6Same topic: Supply Chain Risk, Vendor Risk Mgmt (editorial pick)
5.2Directory of suppliers and service providersEditorialArt.28(3)Art.28(4)Art.28(5)+3Same topic: Vendor Risk Mgmt (editorial pick)
6. Security in acquisition, development and maintenance · 7
6.1Security in acquisition of ICT services, ICT systems or ICT productsEditorialArt.28(2)Art.28(3)Art.28(4)+6Same topic: Supply Chain Risk, Vendor Risk Mgmt (editorial pick)
6.4Change management, repairs and maintenanceEditorialArt.9(4)(e)ControlMapping editorial: All three require documented, risk-based change management in which changes are recorded, tested, approved and verified.
6.5Security testingEditorialArt.8(2)Art.25(1)Art.26(1)+1Same topic: Vulnerability Mgmt (editorial pick)
6.6Security patch managementEditorialArt.9(4)(f)Same topic: Patch Management (editorial pick)
6.7Network securityEditorialArt.9(4)(b)Same topic: Firewall / Net Seg (editorial pick)
6.8Network segmentationEditorialArt.9(4)(b)Same topic: Firewall / Net Seg (editorial pick)
6.10Vulnerability handling and disclosureEditorialArt.8(2)Art.25(1)Art.26(1)+1Same topic: Vulnerability Mgmt (editorial pick)
7. Assessing the effectiveness of cybersecurity risk-management measures · 1
7.1Policies and procedures to assess the effectiveness of cybersecurity risk-management measuresEditorialArt.5(2)(a)Art.6(1)Art.6(8)+2Same topic: Risk Management (editorial pick)
8. Basic cyber hygiene practices and security training · 2
8.1Awareness raising and basic cyber hygiene practicesEditorialArt.5(4)Art.13(6)Same topic: Awareness & Training (editorial pick)
8.2Security trainingEditorialArt.5(4)Art.13(6)Same topic: Awareness & Training (editorial pick)
9. Cryptography · 1
9.1CryptographyEditorialArt.9(3)(a)Art.9(4)(d)Same topic: Encryption (editorial pick)
10. Human resources security · 2
10.2Verification of BackgroundEditorialArt.10(3)Same topic: Insider Threat (editorial pick)
10.4Disciplinary processEditorialArt.10(3)Same topic: Insider Threat (editorial pick)
11. Access control · 7
11.1Access control policyEditorialArt.9(4)(c)Same topic: Access Control (editorial pick)
11.2Management of access rightsEditorialArt.9(4)(c)Same topic: Access Control (editorial pick)
11.3Privileged accounts and system administration accountsEditorialArt.9(4)(c)Same topic: Privileged Access (editorial pick)
11.4Administration systemsEditorialArt.9(4)(c)Same topic: Privileged Access (editorial pick)
11.5IdentificationEditorialArt.9(4)(c)Same topic: Access Control (editorial pick)
11.6AuthenticationEditorialArt.9(4)(d)Same topic: Multi-Factor Auth (editorial pick)
11.7Multi-factor authenticationEditorialArt.9(4)(d)Same topic: Multi-Factor Auth (editorial pick)
12. Asset management · 5
12.1Asset classificationEditorialArt.8(1)Same topic: Data Classification (editorial pick)
12.2Handling of assetsEditorialArt.9(2)Art.9(3)(c)Art.9(3)(d)Same topic: Data Protection (editorial pick)
12.3Removable media policyEditorialArt.9(2)Art.9(3)(c)Art.9(3)(d)Same topic: Data Protection (editorial pick)
12.4Asset inventoryEditorialArt.8(1)Art.8(4)Art.8(6)Same topic: Asset Management (editorial pick)
12.5Deposit, return or deletion of assets upon termination of employmentEditorialArt.30(2)(d)ControlMapping editorial: Access to, return and deletion of data and assets when a contract or relationship ends.
13. Environmental and physical security · 3
13.1Supporting utilitiesEditorialArt.6(2)Art.9(4)(c)Same topic: Physical Security (editorial pick)
13.2Protection against physical and environmental threatsEditorialArt.6(2)Art.9(4)(c)Same topic: Physical Security (editorial pick)
13.3Perimeter and physical access controlEditorialArt.6(2)Art.9(4)(c)Same topic: Physical Security (editorial pick)

By topic

Both cover (37):

Only NIS2 (6):

Only DORA (2):

Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · Loosely related only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. Mapped = curated together in a ControlMapping topic, or linked directly. Crosswalks don't prove compliance. Methodology · Download the data · Report a mistake.