Law / Frameworks / Crosswalk / NIST CSF 2.0 to ENISA NIS2 guidance

The NIST Cybersecurity Framework, mapped to the ENISA NIS2 Technical Implementation Guidance

35 of NIST CSF 2.0's controls connect to 20 of ENISA NIS2 guidance's through 276 laws in 112 jurisdictions. Two controls connect when the same duties, in at least 2 laws we track, reach both. The connections are our own reading of the law; no framework publisher has reviewed or endorsed them.

From
NIST Cybersecurity Framework, version 2.0, February 2024 (NIST CSWP 29), National Institute of Standards and Technology
To
ENISA NIS2 Technical Implementation Guidance, version 1.0, June 2025, with mapping table version 1.2, European Union Agency for Cybersecurity (ENISA)
See also
ENISA NIS2 guidance to NIST CSF 2.0, the other way · every pair in the crosswalk · law library as of

Download this mapping, with every law behind each connection: nist-csf--enisa-nis2-guidance.csv · nist-csf--enisa-nis2-guidance.json

NIST CSF 2.0ENISA NIS2 guidanceLawsJurisdictionsWhere the laws stand
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 1.1Policy on the security of network and information systems 61 41 55 in force, 4 not yet in force, 2 proposed
The 61 laws behind GV.OC-03 and 1.1

and 51 more, every one in the free file.

1.2Roles, responsibilities and authorities 61 41 55 in force, 4 not yet in force, 2 proposed
The 61 laws behind GV.OC-03 and 1.2

and 51 more, every one in the free file.

2.2Compliance monitoring 61 41 55 in force, 4 not yet in force, 2 proposed
The 61 laws behind GV.OC-03 and 2.2

and 51 more, every one in the free file.

3.2Monitoring and logging 61 41 55 in force, 4 not yet in force, 2 proposed
The 61 laws behind GV.OC-03 and 3.2

and 51 more, every one in the free file.

12.4Asset inventory 61 41 55 in force, 4 not yet in force, 2 proposed
The 61 laws behind GV.OC-03 and 12.4

and 51 more, every one in the free file.

3.1Incident handling policy 25 24 22 in force, 1 not yet in force, 2 proposed
The 25 laws behind GV.OC-03 and 3.1

and 15 more, every one in the free file.

3.4Event assessment and classification 23 22 20 in force, 1 not yet in force, 2 proposed
The 23 laws behind GV.OC-03 and 3.4

and 13 more, every one in the free file.

3.5Incident response 23 22 20 in force, 1 not yet in force, 2 proposed
The 23 laws behind GV.OC-03 and 3.5

and 13 more, every one in the free file.

3.6Post-incident reviews 23 22 20 in force, 1 not yet in force, 2 proposed
The 23 laws behind GV.OC-03 and 3.6

and 13 more, every one in the free file.

4.3Crisis management 23 22 20 in force, 1 not yet in force, 2 proposed
The 23 laws behind GV.OC-03 and 4.3

and 13 more, every one in the free file.

2.1Risk management framework 3 3 3 in force
The 3 laws behind GV.OC-03 and 2.1
4.1Business continuity and disaster recovery plan 3 3 3 in force
The 3 laws behind GV.OC-03 and 4.1
6.2Secure development life cycle 3 3 3 in force
The 3 laws behind GV.OC-03 and 6.2
6.5Security testing 3 3 3 in force
The 3 laws behind GV.OC-03 and 6.5
6.10Vulnerability handling and disclosure 3 3 3 in force
The 3 laws behind GV.OC-03 and 6.10
9.1Cryptography 3 3 3 in force
The 3 laws behind GV.OC-03 and 9.1
11.2Management of access rights 3 3 3 in force
The 3 laws behind GV.OC-03 and 11.2
GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and... 1.1Policy on the security of network and information systems 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind GV.RR-01 and 1.1

and 21 more, every one in the free file.

1.2Roles, responsibilities and authorities 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind GV.RR-01 and 1.2

and 21 more, every one in the free file.

2.2Compliance monitoring 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind GV.RR-01 and 2.2

and 21 more, every one in the free file.

3.2Monitoring and logging 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind GV.RR-01 and 3.2

and 21 more, every one in the free file.

12.4Asset inventory 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind GV.RR-01 and 12.4

and 21 more, every one in the free file.

GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 1.1Policy on the security of network and information systems 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind GV.RR-02 and 1.1

and 14 more, every one in the free file.

1.2Roles, responsibilities and authorities 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind GV.RR-02 and 1.2

and 14 more, every one in the free file.

2.2Compliance monitoring 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind GV.RR-02 and 2.2

and 14 more, every one in the free file.

3.2Monitoring and logging 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind GV.RR-02 and 3.2

and 14 more, every one in the free file.

12.4Asset inventory 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind GV.RR-02 and 12.4

and 14 more, every one in the free file.

3.1Incident handling policy 3 3 3 in force
The 3 laws behind GV.RR-02 and 3.1
2.1Risk management framework 2 2 2 in force
The 2 laws behind GV.RR-02 and 2.1
3.4Event assessment and classification 2 2 2 in force
The 2 laws behind GV.RR-02 and 3.4
3.5Incident response 2 2 2 in force
The 2 laws behind GV.RR-02 and 3.5
3.6Post-incident reviews 2 2 2 in force
The 2 laws behind GV.RR-02 and 3.6
4.1Business continuity and disaster recovery plan 2 2 2 in force
The 2 laws behind GV.RR-02 and 4.1
4.3Crisis management 2 2 2 in force
The 2 laws behind GV.RR-02 and 4.3
6.2Secure development life cycle 2 2 2 in force
The 2 laws behind GV.RR-02 and 6.2
6.5Security testing 2 2 2 in force
The 2 laws behind GV.RR-02 and 6.5
6.10Vulnerability handling and disclosure 2 2 2 in force
The 2 laws behind GV.RR-02 and 6.10
9.1Cryptography 2 2 2 in force
The 2 laws behind GV.RR-02 and 9.1
11.2Management of access rights 2 2 2 in force
The 2 laws behind GV.RR-02 and 11.2
GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 1.1Policy on the security of network and information systems 60 40 56 in force, 4 not yet in force
The 60 laws behind GV.PO-01 and 1.1

and 50 more, every one in the free file.

1.2Roles, responsibilities and authorities 60 40 56 in force, 4 not yet in force
The 60 laws behind GV.PO-01 and 1.2

and 50 more, every one in the free file.

2.2Compliance monitoring 60 40 56 in force, 4 not yet in force
The 60 laws behind GV.PO-01 and 2.2

and 50 more, every one in the free file.

3.2Monitoring and logging 60 40 56 in force, 4 not yet in force
The 60 laws behind GV.PO-01 and 3.2

and 50 more, every one in the free file.

12.4Asset inventory 60 40 56 in force, 4 not yet in force
The 60 laws behind GV.PO-01 and 12.4

and 50 more, every one in the free file.

2.1Risk management framework 5 5 4 in force, 1 not yet in force
The 5 laws behind GV.PO-01 and 2.1
3.1Incident handling policy 4 4 3 in force, 1 not yet in force
The 4 laws behind GV.PO-01 and 3.1
4.1Business continuity and disaster recovery plan 4 4 3 in force, 1 not yet in force
The 4 laws behind GV.PO-01 and 4.1
6.2Secure development life cycle 4 4 3 in force, 1 not yet in force
The 4 laws behind GV.PO-01 and 6.2
6.5Security testing 4 4 3 in force, 1 not yet in force
The 4 laws behind GV.PO-01 and 6.5
6.10Vulnerability handling and disclosure 4 4 3 in force, 1 not yet in force
The 4 laws behind GV.PO-01 and 6.10
9.1Cryptography 4 4 3 in force, 1 not yet in force
The 4 laws behind GV.PO-01 and 9.1
11.2Management of access rights 4 4 3 in force, 1 not yet in force
The 4 laws behind GV.PO-01 and 11.2
ID.AM-02Inventories of software, services, and systems managed by the organization are maintained 1.1Policy on the security of network and information systems 4 4 4 in force
The 4 laws behind ID.AM-02 and 1.1
1.2Roles, responsibilities and authorities 4 4 4 in force
The 4 laws behind ID.AM-02 and 1.2
2.2Compliance monitoring 4 4 4 in force
The 4 laws behind ID.AM-02 and 2.2
3.2Monitoring and logging 4 4 4 in force
The 4 laws behind ID.AM-02 and 3.2
12.4Asset inventory 4 4 4 in force
The 4 laws behind ID.AM-02 and 12.4
ID.AM-05Assets are prioritized based on classification, criticality, resources, and impact on... 1.1Policy on the security of network and information systems 3 3 2 in force, 1 not yet in force
The 3 laws behind ID.AM-05 and 1.1
1.2Roles, responsibilities and authorities 3 3 2 in force, 1 not yet in force
The 3 laws behind ID.AM-05 and 1.2
2.2Compliance monitoring 3 3 2 in force, 1 not yet in force
The 3 laws behind ID.AM-05 and 2.2
3.2Monitoring and logging 3 3 2 in force, 1 not yet in force
The 3 laws behind ID.AM-05 and 3.2
12.4Asset inventory 3 3 2 in force, 1 not yet in force
The 3 laws behind ID.AM-05 and 12.4
ID.AM-07Inventories of data and corresponding metadata for designated data types are maintained 1.1Policy on the security of network and information systems 2 2 2 in force
The 2 laws behind ID.AM-07 and 1.1
1.2Roles, responsibilities and authorities 2 2 2 in force
The 2 laws behind ID.AM-07 and 1.2
2.2Compliance monitoring 2 2 2 in force
The 2 laws behind ID.AM-07 and 2.2
3.2Monitoring and logging 2 2 2 in force
The 2 laws behind ID.AM-07 and 3.2
12.4Asset inventory 2 2 2 in force
The 2 laws behind ID.AM-07 and 12.4
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 1.1Policy on the security of network and information systems 10 10 10 in force
The 10 laws behind ID.AM-08 and 1.1
3.2Monitoring and logging 10 10 10 in force
The 10 laws behind ID.AM-08 and 3.2
4.2Backup and redundancy management 10 10 10 in force
The 10 laws behind ID.AM-08 and 4.2
12.2Handling of assets 10 10 10 in force
The 10 laws behind ID.AM-08 and 12.2
2.1Risk management framework 3 3 3 in force
The 3 laws behind ID.AM-08 and 2.1
3.1Incident handling policy 3 3 3 in force
The 3 laws behind ID.AM-08 and 3.1
4.1Business continuity and disaster recovery plan 3 3 3 in force
The 3 laws behind ID.AM-08 and 4.1
6.2Secure development life cycle 3 3 3 in force
The 3 laws behind ID.AM-08 and 6.2
6.5Security testing 3 3 3 in force
The 3 laws behind ID.AM-08 and 6.5
6.10Vulnerability handling and disclosure 3 3 3 in force
The 3 laws behind ID.AM-08 and 6.10
9.1Cryptography 3 3 3 in force
The 3 laws behind ID.AM-08 and 9.1
11.2Management of access rights 3 3 3 in force
The 3 laws behind ID.AM-08 and 11.2
ID.RA-01Vulnerabilities in assets are identified, validated, and recorded 2.1Risk management framework 6 4 6 in force
The 6 laws behind ID.RA-01 and 2.1
3.1Incident handling policy 6 4 6 in force
The 6 laws behind ID.RA-01 and 3.1
4.1Business continuity and disaster recovery plan 6 4 6 in force
The 6 laws behind ID.RA-01 and 4.1
6.2Secure development life cycle 6 4 6 in force
The 6 laws behind ID.RA-01 and 6.2
6.5Security testing 6 4 6 in force
The 6 laws behind ID.RA-01 and 6.5
6.10Vulnerability handling and disclosure 6 4 6 in force
The 6 laws behind ID.RA-01 and 6.10
9.1Cryptography 6 4 6 in force
The 6 laws behind ID.RA-01 and 9.1
11.2Management of access rights 6 4 6 in force
The 6 laws behind ID.RA-01 and 11.2
ID.RA-05Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent... 1.1Policy on the security of network and information systems 5 5 4 in force, 1 not yet in force
The 5 laws behind ID.RA-05 and 1.1
1.2Roles, responsibilities and authorities 5 5 4 in force, 1 not yet in force
The 5 laws behind ID.RA-05 and 1.2
2.2Compliance monitoring 5 5 4 in force, 1 not yet in force
The 5 laws behind ID.RA-05 and 2.2
3.2Monitoring and logging 5 5 4 in force, 1 not yet in force
The 5 laws behind ID.RA-05 and 3.2
12.4Asset inventory 5 5 4 in force, 1 not yet in force
The 5 laws behind ID.RA-05 and 12.4
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 1.1Policy on the security of network and information systems 3 3 1 in force, 2 proposed
The 3 laws behind ID.RA-06 and 1.1
1.2Roles, responsibilities and authorities 3 3 1 in force, 2 proposed
The 3 laws behind ID.RA-06 and 1.2
2.2Compliance monitoring 3 3 1 in force, 2 proposed
The 3 laws behind ID.RA-06 and 2.2
3.1Incident handling policy 3 3 3 in force
The 3 laws behind ID.RA-06 and 3.1
3.2Monitoring and logging 3 3 1 in force, 2 proposed
The 3 laws behind ID.RA-06 and 3.2
12.4Asset inventory 3 3 1 in force, 2 proposed
The 3 laws behind ID.RA-06 and 12.4
2.1Risk management framework 2 2 2 in force
The 2 laws behind ID.RA-06 and 2.1
3.4Event assessment and classification 2 2 2 in force
The 2 laws behind ID.RA-06 and 3.4
3.5Incident response 2 2 2 in force
The 2 laws behind ID.RA-06 and 3.5
3.6Post-incident reviews 2 2 2 in force
The 2 laws behind ID.RA-06 and 3.6
4.3Crisis management 2 2 2 in force
The 2 laws behind ID.RA-06 and 4.3
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established 2.1Risk management framework 8 7 7 in force, 1 not yet in force
The 8 laws behind ID.RA-08 and 2.1
3.1Incident handling policy 8 7 7 in force, 1 not yet in force
The 8 laws behind ID.RA-08 and 3.1
4.1Business continuity and disaster recovery plan 8 7 7 in force, 1 not yet in force
The 8 laws behind ID.RA-08 and 4.1
6.2Secure development life cycle 8 7 7 in force, 1 not yet in force
The 8 laws behind ID.RA-08 and 6.2
6.5Security testing 8 7 7 in force, 1 not yet in force
The 8 laws behind ID.RA-08 and 6.5
6.10Vulnerability handling and disclosure 8 7 7 in force, 1 not yet in force
The 8 laws behind ID.RA-08 and 6.10
9.1Cryptography 8 7 7 in force, 1 not yet in force
The 8 laws behind ID.RA-08 and 9.1
11.2Management of access rights 8 7 7 in force, 1 not yet in force
The 8 laws behind ID.RA-08 and 11.2
ID.IM-01Improvements are identified from evaluations 2.1Risk management framework 3 3 3 in force
The 3 laws behind ID.IM-01 and 2.1
2.3Independent review of information and network security 3 3 3 in force
The 3 laws behind ID.IM-01 and 2.3
1.1Policy on the security of network and information systems 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 1.1
1.2Roles, responsibilities and authorities 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 1.2
2.2Compliance monitoring 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 2.2
3.1Incident handling policy 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 3.1
3.2Monitoring and logging 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 3.2
3.4Event assessment and classification 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 3.4
3.5Incident response 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 3.5
3.6Post-incident reviews 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 3.6
4.3Crisis management 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 4.3
12.4Asset inventory 2 2 1 in force, 1 not yet in force
The 2 laws behind ID.IM-01 and 12.4
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 1.1Policy on the security of network and information systems 2 2 2 in force
The 2 laws behind ID.IM-02 and 1.1
1.2Roles, responsibilities and authorities 2 2 2 in force
The 2 laws behind ID.IM-02 and 1.2
2.2Compliance monitoring 2 2 2 in force
The 2 laws behind ID.IM-02 and 2.2
3.2Monitoring and logging 2 2 2 in force
The 2 laws behind ID.IM-02 and 3.2
12.4Asset inventory 2 2 2 in force
The 2 laws behind ID.IM-02 and 12.4
2.1Risk management framework 2 1 2 in force
The 2 laws behind ID.IM-02 and 2.1
3.1Incident handling policy 2 1 2 in force
The 2 laws behind ID.IM-02 and 3.1
4.1Business continuity and disaster recovery plan 2 1 2 in force
The 2 laws behind ID.IM-02 and 4.1
6.2Secure development life cycle 2 1 2 in force
The 2 laws behind ID.IM-02 and 6.2
6.5Security testing 2 1 2 in force
The 2 laws behind ID.IM-02 and 6.5
6.10Vulnerability handling and disclosure 2 1 2 in force
The 2 laws behind ID.IM-02 and 6.10
9.1Cryptography 2 1 2 in force
The 2 laws behind ID.IM-02 and 9.1
11.2Management of access rights 2 1 2 in force
The 2 laws behind ID.IM-02 and 11.2
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 2.1Risk management framework 24 18 23 in force, 1 not yet in force
The 24 laws behind ID.IM-04 and 2.1

and 14 more, every one in the free file.

3.1Incident handling policy 24 18 23 in force, 1 not yet in force
The 24 laws behind ID.IM-04 and 3.1

and 14 more, every one in the free file.

4.1Business continuity and disaster recovery plan 24 18 23 in force, 1 not yet in force
The 24 laws behind ID.IM-04 and 4.1

and 14 more, every one in the free file.

6.2Secure development life cycle 24 18 23 in force, 1 not yet in force
The 24 laws behind ID.IM-04 and 6.2

and 14 more, every one in the free file.

6.5Security testing 24 18 23 in force, 1 not yet in force
The 24 laws behind ID.IM-04 and 6.5

and 14 more, every one in the free file.

6.10Vulnerability handling and disclosure 24 18 23 in force, 1 not yet in force
The 24 laws behind ID.IM-04 and 6.10

and 14 more, every one in the free file.

9.1Cryptography 24 18 23 in force, 1 not yet in force
The 24 laws behind ID.IM-04 and 9.1

and 14 more, every one in the free file.

11.2Management of access rights 24 18 23 in force, 1 not yet in force
The 24 laws behind ID.IM-04 and 11.2

and 14 more, every one in the free file.

3.4Event assessment and classification 7 6 6 in force, 1 not yet in force
The 7 laws behind ID.IM-04 and 3.4
3.5Incident response 7 6 6 in force, 1 not yet in force
The 7 laws behind ID.IM-04 and 3.5
3.6Post-incident reviews 7 6 6 in force, 1 not yet in force
The 7 laws behind ID.IM-04 and 3.6
4.3Crisis management 7 6 6 in force, 1 not yet in force
The 7 laws behind ID.IM-04 and 4.3
1.1Policy on the security of network and information systems 2 2 2 in force
The 2 laws behind ID.IM-04 and 1.1
1.2Roles, responsibilities and authorities 2 2 2 in force
The 2 laws behind ID.IM-04 and 1.2
2.2Compliance monitoring 2 2 2 in force
The 2 laws behind ID.IM-04 and 2.2
3.2Monitoring and logging 2 2 2 in force
The 2 laws behind ID.IM-04 and 3.2
12.4Asset inventory 2 2 2 in force
The 2 laws behind ID.IM-04 and 12.4
PR.AA-03Users, services, and hardware are authenticated 2.1Risk management framework 4 3 4 in force
The 4 laws behind PR.AA-03 and 2.1
3.1Incident handling policy 4 3 4 in force
The 4 laws behind PR.AA-03 and 3.1
4.1Business continuity and disaster recovery plan 4 3 4 in force
The 4 laws behind PR.AA-03 and 4.1
6.2Secure development life cycle 4 3 4 in force
The 4 laws behind PR.AA-03 and 6.2
6.5Security testing 4 3 4 in force
The 4 laws behind PR.AA-03 and 6.5
6.10Vulnerability handling and disclosure 4 3 4 in force
The 4 laws behind PR.AA-03 and 6.10
9.1Cryptography 4 3 4 in force
The 4 laws behind PR.AA-03 and 9.1
11.2Management of access rights 4 3 4 in force
The 4 laws behind PR.AA-03 and 11.2
PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed,... 2.1Risk management framework 9 5 9 in force
The 9 laws behind PR.AA-05 and 2.1
3.1Incident handling policy 9 5 9 in force
The 9 laws behind PR.AA-05 and 3.1
4.1Business continuity and disaster recovery plan 9 5 9 in force
The 9 laws behind PR.AA-05 and 4.1
6.2Secure development life cycle 9 5 9 in force
The 9 laws behind PR.AA-05 and 6.2
6.5Security testing 9 5 9 in force
The 9 laws behind PR.AA-05 and 6.5
6.10Vulnerability handling and disclosure 9 5 9 in force
The 9 laws behind PR.AA-05 and 6.10
9.1Cryptography 9 5 9 in force
The 9 laws behind PR.AA-05 and 9.1
11.2Management of access rights 9 5 9 in force
The 9 laws behind PR.AA-05 and 11.2
PR.AT-01Personnel are provided with awareness and training so that they possess the knowledge... 1.1Policy on the security of network and information systems 2 2 2 in force
The 2 laws behind PR.AT-01 and 1.1
1.2Roles, responsibilities and authorities 2 2 2 in force
The 2 laws behind PR.AT-01 and 1.2
2.2Compliance monitoring 2 2 2 in force
The 2 laws behind PR.AT-01 and 2.2
3.2Monitoring and logging 2 2 2 in force
The 2 laws behind PR.AT-01 and 3.2
12.4Asset inventory 2 2 2 in force
The 2 laws behind PR.AT-01 and 12.4
PR.AT-02Individuals in specialized roles are provided with awareness and training so that they... 1.1Policy on the security of network and information systems 24 21 23 in force, 1 proposed
The 24 laws behind PR.AT-02 and 1.1

and 14 more, every one in the free file.

1.2Roles, responsibilities and authorities 24 21 23 in force, 1 proposed
The 24 laws behind PR.AT-02 and 1.2

and 14 more, every one in the free file.

2.2Compliance monitoring 24 21 23 in force, 1 proposed
The 24 laws behind PR.AT-02 and 2.2

and 14 more, every one in the free file.

3.2Monitoring and logging 24 21 23 in force, 1 proposed
The 24 laws behind PR.AT-02 and 3.2

and 14 more, every one in the free file.

12.4Asset inventory 24 21 23 in force, 1 proposed
The 24 laws behind PR.AT-02 and 12.4

and 14 more, every one in the free file.

PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected 2.1Risk management framework 40 37 39 in force, 1 not yet in force
The 40 laws behind PR.DS-01 and 2.1

and 30 more, every one in the free file.

3.1Incident handling policy 40 37 39 in force, 1 not yet in force
The 40 laws behind PR.DS-01 and 3.1

and 30 more, every one in the free file.

4.1Business continuity and disaster recovery plan 40 37 39 in force, 1 not yet in force
The 40 laws behind PR.DS-01 and 4.1

and 30 more, every one in the free file.

6.2Secure development life cycle 40 37 39 in force, 1 not yet in force
The 40 laws behind PR.DS-01 and 6.2

and 30 more, every one in the free file.

6.5Security testing 40 37 39 in force, 1 not yet in force
The 40 laws behind PR.DS-01 and 6.5

and 30 more, every one in the free file.

6.10Vulnerability handling and disclosure 40 37 39 in force, 1 not yet in force
The 40 laws behind PR.DS-01 and 6.10

and 30 more, every one in the free file.

9.1Cryptography 40 37 39 in force, 1 not yet in force
The 40 laws behind PR.DS-01 and 9.1

and 30 more, every one in the free file.

11.2Management of access rights 40 37 39 in force, 1 not yet in force
The 40 laws behind PR.DS-01 and 11.2

and 30 more, every one in the free file.

PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected 2.1Risk management framework 8 7 8 in force
The 8 laws behind PR.DS-02 and 2.1
3.1Incident handling policy 8 7 8 in force
The 8 laws behind PR.DS-02 and 3.1
4.1Business continuity and disaster recovery plan 8 7 8 in force
The 8 laws behind PR.DS-02 and 4.1
6.2Secure development life cycle 8 7 8 in force
The 8 laws behind PR.DS-02 and 6.2
6.5Security testing 8 7 8 in force
The 8 laws behind PR.DS-02 and 6.5
6.10Vulnerability handling and disclosure 8 7 8 in force
The 8 laws behind PR.DS-02 and 6.10
9.1Cryptography 8 7 8 in force
The 8 laws behind PR.DS-02 and 9.1
11.2Management of access rights 8 7 8 in force
The 8 laws behind PR.DS-02 and 11.2
PR.DS-11Backups of data are created, protected, maintained, and tested 2.1Risk management framework 3 3 3 in force
The 3 laws behind PR.DS-11 and 2.1
3.1Incident handling policy 3 3 3 in force
The 3 laws behind PR.DS-11 and 3.1
4.1Business continuity and disaster recovery plan 3 3 3 in force
The 3 laws behind PR.DS-11 and 4.1
6.2Secure development life cycle 3 3 3 in force
The 3 laws behind PR.DS-11 and 6.2
6.5Security testing 3 3 3 in force
The 3 laws behind PR.DS-11 and 6.5
6.10Vulnerability handling and disclosure 3 3 3 in force
The 3 laws behind PR.DS-11 and 6.10
9.1Cryptography 3 3 3 in force
The 3 laws behind PR.DS-11 and 9.1
11.2Management of access rights 3 3 3 in force
The 3 laws behind PR.DS-11 and 11.2
PR.PS-01Configuration management practices are established and applied 2.1Risk management framework 2 2 2 in force
The 2 laws behind PR.PS-01 and 2.1
3.1Incident handling policy 2 2 2 in force
The 2 laws behind PR.PS-01 and 3.1
4.1Business continuity and disaster recovery plan 2 2 2 in force
The 2 laws behind PR.PS-01 and 4.1
6.2Secure development life cycle 2 2 2 in force
The 2 laws behind PR.PS-01 and 6.2
6.5Security testing 2 2 2 in force
The 2 laws behind PR.PS-01 and 6.5
6.10Vulnerability handling and disclosure 2 2 2 in force
The 2 laws behind PR.PS-01 and 6.10
9.1Cryptography 2 2 2 in force
The 2 laws behind PR.PS-01 and 9.1
11.2Management of access rights 2 2 2 in force
The 2 laws behind PR.PS-01 and 11.2
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 3.1Incident handling policy 3 2 2 in force, 1 not yet in force
The 3 laws behind PR.PS-02 and 3.1
6.10Vulnerability handling and disclosure 3 2 2 in force, 1 not yet in force
The 3 laws behind PR.PS-02 and 6.10
3.5Incident response 2 2 2 in force
The 2 laws behind PR.PS-02 and 3.5
2.1Risk management framework 2 1 1 in force, 1 not yet in force
The 2 laws behind PR.PS-02 and 2.1
4.1Business continuity and disaster recovery plan 2 1 1 in force, 1 not yet in force
The 2 laws behind PR.PS-02 and 4.1
6.2Secure development life cycle 2 1 1 in force, 1 not yet in force
The 2 laws behind PR.PS-02 and 6.2
6.5Security testing 2 1 1 in force, 1 not yet in force
The 2 laws behind PR.PS-02 and 6.5
9.1Cryptography 2 1 1 in force, 1 not yet in force
The 2 laws behind PR.PS-02 and 9.1
11.2Management of access rights 2 1 1 in force, 1 not yet in force
The 2 laws behind PR.PS-02 and 11.2
PR.PS-04Log records are generated and made available for continuous monitoring 1.1Policy on the security of network and information systems 7 6 6 in force, 1 not yet in force
The 7 laws behind PR.PS-04 and 1.1
3.2Monitoring and logging 7 6 6 in force, 1 not yet in force
The 7 laws behind PR.PS-04 and 3.2
1.2Roles, responsibilities and authorities 6 5 5 in force, 1 not yet in force
The 6 laws behind PR.PS-04 and 1.2
2.2Compliance monitoring 6 5 5 in force, 1 not yet in force
The 6 laws behind PR.PS-04 and 2.2
12.4Asset inventory 6 5 5 in force, 1 not yet in force
The 6 laws behind PR.PS-04 and 12.4
3.1Incident handling policy 2 2 2 in force
The 2 laws behind PR.PS-04 and 3.1
PR.PS-06Secure software development practices are integrated, and their performance is... 2.1Risk management framework 29 18 25 in force, 4 not yet in force
The 29 laws behind PR.PS-06 and 2.1

and 19 more, every one in the free file.

3.1Incident handling policy 29 18 25 in force, 4 not yet in force
The 29 laws behind PR.PS-06 and 3.1

and 19 more, every one in the free file.

4.1Business continuity and disaster recovery plan 29 18 25 in force, 4 not yet in force
The 29 laws behind PR.PS-06 and 4.1

and 19 more, every one in the free file.

6.2Secure development life cycle 29 18 25 in force, 4 not yet in force
The 29 laws behind PR.PS-06 and 6.2

and 19 more, every one in the free file.

6.5Security testing 29 18 25 in force, 4 not yet in force
The 29 laws behind PR.PS-06 and 6.5

and 19 more, every one in the free file.

6.10Vulnerability handling and disclosure 29 18 25 in force, 4 not yet in force
The 29 laws behind PR.PS-06 and 6.10

and 19 more, every one in the free file.

9.1Cryptography 29 18 25 in force, 4 not yet in force
The 29 laws behind PR.PS-06 and 9.1

and 19 more, every one in the free file.

11.2Management of access rights 29 18 25 in force, 4 not yet in force
The 29 laws behind PR.PS-06 and 11.2

and 19 more, every one in the free file.

PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 1.1Policy on the security of network and information systems 2 2 2 in force
The 2 laws behind PR.IR-03 and 1.1
1.2Roles, responsibilities and authorities 2 2 2 in force
The 2 laws behind PR.IR-03 and 1.2
2.2Compliance monitoring 2 2 2 in force
The 2 laws behind PR.IR-03 and 2.2
3.2Monitoring and logging 2 2 2 in force
The 2 laws behind PR.IR-03 and 3.2
12.4Asset inventory 2 2 2 in force
The 2 laws behind PR.IR-03 and 12.4
DE.CM-01Networks and network services are monitored to find potentially adverse events 2.1Risk management framework 2 2 2 in force
The 2 laws behind DE.CM-01 and 2.1
3.1Incident handling policy 2 2 2 in force
The 2 laws behind DE.CM-01 and 3.1
4.1Business continuity and disaster recovery plan 2 2 2 in force
The 2 laws behind DE.CM-01 and 4.1
6.2Secure development life cycle 2 2 2 in force
The 2 laws behind DE.CM-01 and 6.2
6.5Security testing 2 2 2 in force
The 2 laws behind DE.CM-01 and 6.5
6.10Vulnerability handling and disclosure 2 2 2 in force
The 2 laws behind DE.CM-01 and 6.10
9.1Cryptography 2 2 2 in force
The 2 laws behind DE.CM-01 and 9.1
11.2Management of access rights 2 2 2 in force
The 2 laws behind DE.CM-01 and 11.2
DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 2.1Risk management framework 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind DE.CM-09 and 2.1

and 2 more, every one in the free file.

3.1Incident handling policy 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind DE.CM-09 and 3.1

and 2 more, every one in the free file.

4.1Business continuity and disaster recovery plan 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind DE.CM-09 and 4.1

and 2 more, every one in the free file.

6.2Secure development life cycle 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind DE.CM-09 and 6.2

and 2 more, every one in the free file.

6.5Security testing 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind DE.CM-09 and 6.5

and 2 more, every one in the free file.

6.10Vulnerability handling and disclosure 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind DE.CM-09 and 6.10

and 2 more, every one in the free file.

9.1Cryptography 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind DE.CM-09 and 9.1

and 2 more, every one in the free file.

11.2Management of access rights 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind DE.CM-09 and 11.2

and 2 more, every one in the free file.

1.1Policy on the security of network and information systems 2 2 1 in force, 1 not yet in force
The 2 laws behind DE.CM-09 and 1.1
1.2Roles, responsibilities and authorities 2 2 1 in force, 1 not yet in force
The 2 laws behind DE.CM-09 and 1.2
2.2Compliance monitoring 2 2 1 in force, 1 not yet in force
The 2 laws behind DE.CM-09 and 2.2
3.2Monitoring and logging 2 2 1 in force, 1 not yet in force
The 2 laws behind DE.CM-09 and 3.2
12.4Asset inventory 2 2 1 in force, 1 not yet in force
The 2 laws behind DE.CM-09 and 12.4
RS.MA-03Incidents are categorized and prioritized 3.1Incident handling policy 2 2 2 in force
The 2 laws behind RS.MA-03 and 3.1
3.4Event assessment and classification 2 2 2 in force
The 2 laws behind RS.MA-03 and 3.4
3.5Incident response 2 2 2 in force
The 2 laws behind RS.MA-03 and 3.5
3.6Post-incident reviews 2 2 2 in force
The 2 laws behind RS.MA-03 and 3.6
4.3Crisis management 2 2 2 in force
The 2 laws behind RS.MA-03 and 4.3
RS.CO-02Internal and external stakeholders are notified of incidents 3.5Incident response 101 69 92 in force, 4 not yet in force, 5 proposed
The 101 laws behind RS.CO-02 and 3.5

and 91 more, every one in the free file.

3.1Incident handling policy 100 67 91 in force, 4 not yet in force, 5 proposed
The 100 laws behind RS.CO-02 and 3.1

and 90 more, every one in the free file.

3.4Event assessment and classification 98 67 89 in force, 4 not yet in force, 5 proposed
The 98 laws behind RS.CO-02 and 3.4

and 88 more, every one in the free file.

3.6Post-incident reviews 97 66 88 in force, 4 not yet in force, 5 proposed
The 97 laws behind RS.CO-02 and 3.6

and 87 more, every one in the free file.

4.3Crisis management 97 66 88 in force, 4 not yet in force, 5 proposed
The 97 laws behind RS.CO-02 and 4.3

and 87 more, every one in the free file.

6.10Vulnerability handling and disclosure 9 8 9 in force
The 9 laws behind RS.CO-02 and 6.10
2.1Risk management framework 3 3 3 in force
The 3 laws behind RS.CO-02 and 2.1
4.1Business continuity and disaster recovery plan 3 3 3 in force
The 3 laws behind RS.CO-02 and 4.1
6.2Secure development life cycle 3 3 3 in force
The 3 laws behind RS.CO-02 and 6.2
6.5Security testing 3 3 3 in force
The 3 laws behind RS.CO-02 and 6.5
9.1Cryptography 3 3 3 in force
The 3 laws behind RS.CO-02 and 9.1
11.2Management of access rights 3 3 3 in force
The 3 laws behind RS.CO-02 and 11.2
RS.CO-03Information is shared with designated internal and external stakeholders 3.1Incident handling policy 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind RS.CO-03 and 3.1

and 39 more, every one in the free file.

3.4Event assessment and classification 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind RS.CO-03 and 3.4

and 39 more, every one in the free file.

3.5Incident response 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind RS.CO-03 and 3.5

and 39 more, every one in the free file.

3.6Post-incident reviews 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind RS.CO-03 and 3.6

and 39 more, every one in the free file.

4.3Crisis management 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind RS.CO-03 and 4.3

and 39 more, every one in the free file.

RS.MI-01Incidents are contained 3.1Incident handling policy 5 5 3 in force, 2 not yet in force
The 5 laws behind RS.MI-01 and 3.1
3.4Event assessment and classification 5 5 3 in force, 2 not yet in force
The 5 laws behind RS.MI-01 and 3.4
3.5Incident response 5 5 3 in force, 2 not yet in force
The 5 laws behind RS.MI-01 and 3.5
3.6Post-incident reviews 5 5 3 in force, 2 not yet in force
The 5 laws behind RS.MI-01 and 3.6
4.3Crisis management 5 5 3 in force, 2 not yet in force
The 5 laws behind RS.MI-01 and 4.3
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related... 3.1Incident handling policy 3 3 3 in force
The 3 laws behind RC.RP-06 and 3.1
3.4Event assessment and classification 3 3 3 in force
The 3 laws behind RC.RP-06 and 3.4
3.5Incident response 3 3 3 in force
The 3 laws behind RC.RP-06 and 3.5
3.6Post-incident reviews 3 3 3 in force
The 3 laws behind RC.RP-06 and 3.6
4.3Crisis management 3 3 3 in force
The 3 laws behind RC.RP-06 and 4.3
RC.CO-04Public updates on incident recovery are shared using approved methods and messaging 3.5Incident response 3 3 3 in force
The 3 laws behind RC.CO-04 and 3.5
6.10Vulnerability handling and disclosure 3 3 3 in force
The 3 laws behind RC.CO-04 and 6.10
Not connected to the ENISA NIS2 guidance: 71 of NIST CSF 2.0's controls

Short of 2 laws

The same duties reach these and a ENISA NIS2 guidance requirement, in fewer than 2 of the laws we track.

No ENISA NIS2 guidance requirement on the same duties

Laws reach these, but no duty that reaches one of them also reaches a ENISA NIS2 guidance requirement.

  • GV.OC-04 Critical objectives, capabilities, and services that external stakeholders depend on..., 1 law
  • GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders, 1 law
  • GV.RM-02 Risk appetite and risk tolerance statements are established, communicated, and maintained, 3 laws
  • GV.RM-03 Cybersecurity risk management activities and outcomes are included in enterprise risk..., 1 law
  • GV.RM-05 Lines of communication across the organization are established for cybersecurity..., 1 law
  • GV.RM-06 A standardized method for calculating, documenting, categorizing, and prioritizing..., 7 laws
  • GV.RR-03 Adequate resources are allocated commensurate with the cybersecurity risk strategy,..., 2 laws
  • GV.RR-04 Cybersecurity is included in human resources practices, 7 laws
  • GV.OV-02 The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage..., 1 law
  • GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies,..., 7 laws
  • GV.SC-07 The risks posed by a supplier, their products and services, and other third parties..., 16 laws
  • GV.SC-08 Relevant suppliers and other third parties are included in incident planning,..., 1 law
  • GV.SC-10 Cybersecurity supply chain risk management plans include provisions for activities..., 1 law
  • ID.AM-04 Inventories of services provided by suppliers are maintained, 2 laws
  • ID.RA-03 Internal and external threats to the organization are identified and recorded, 4 laws
  • ID.RA-04 Potential impacts and likelihoods of threats exploiting vulnerabilities are identified..., 4 laws
  • ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities, 3 laws
  • PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by..., 2 laws
  • PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions, 1 law
  • PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk, 1 law
  • PR.PS-03 Hardware is maintained, replaced, and removed commensurate with risk, 1 law
  • PR.PS-05 Installation and execution of unauthorized software are prevented, 3 laws
  • PR.IR-01 Networks and environments are protected from unauthorized logical access and usage, 14 laws
  • PR.IR-04 Adequate resource capacity to ensure availability is maintained, 2 laws
  • DE.AE-02 Potentially adverse events are analyzed to better understand associated activities, 1 law
  • DE.AE-06 Information on adverse events is provided to authorized staff and tools, 1 law
  • DE.AE-07 Cyber threat intelligence and other contextual information are integrated into the analysis, 1 law
  • DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria, 1 law
  • DE.CM-06 External service provider activities and services are monitored to find potentially..., 2 laws
  • RS.MA-02 Incident reports are triaged and validated, 2 laws
  • RS.MA-04 Incidents are escalated or elevated as needed, 1 law
  • RS.AN-03 Analysis is performed to establish what has taken place during an incident and the..., 3 laws
  • RS.AN-08 An incident's magnitude is estimated and validated, 3 laws
  • RC.RP-02 Recovery actions are selected, scoped, prioritized, and performed, 3 laws
  • RC.CO-03 Recovery activities and progress in restoring operational capabilities are..., 2 laws

No law we track reaches these

No duty in the laws we track reaches these controls.

  • GV.OC-01 The organizational mission is understood and informs cybersecurity risk management
  • GV.OC-02 Internal and external stakeholders are understood, and their needs and expectations...
  • GV.OC-05 Outcomes, capabilities, and services that the organization depends on are understood...
  • GV.RM-04 Strategic direction that describes appropriate risk response options is established...
  • GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in...
  • GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust...
  • GV.SC-02 Cybersecurity roles and responsibilities for suppliers, customers, and partners are...
  • GV.SC-03 Cybersecurity supply chain risk management is integrated into cybersecurity and...
  • GV.SC-04 Suppliers are known and prioritized by criticality
  • GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk...
  • ID.AM-03 Representations of the organization's authorized network communication and internal...
  • ID.RA-02 Cyber threat intelligence is received from information sharing forums and sources
  • ID.RA-10 Critical suppliers are assessed prior to acquisition
  • PR.AA-04 Identity assertions are protected, conveyed, and verified
  • PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected
  • PR.IR-02 The organization's technology assets are protected from environmental threats
  • DE.AE-03 Information is correlated from multiple sources
  • DE.AE-04 The estimated impact and scope of adverse events are understood
  • DE.CM-02 The physical environment is monitored to find potentially adverse events
  • RS.MA-05 The criteria for initiating incident recovery are applied
  • RS.MI-02 Incidents are eradicated
  • RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the...
  • RC.RP-03 The integrity of backups and other restoration assets is verified before using them...
  • RC.RP-04 Critical mission functions and cybersecurity risk management are considered to...
  • RC.RP-05 The integrity of restored assets is verified, systems and services are restored, and...

How these connections are drawn

Each requirement line in the laws we track is read against the framework for its subject (the AI, scraping and news aggregation laws against the NIST AI RMF, the privacy, communications and age assurance laws against the NIST Privacy Framework, the cybersecurity laws against the NIST CSF 2.0); laws on liability and content moderation are not read against any framework yet. A line reaches the ENISA NIS2 guidance through a kind of duty its law carries, and only where that kind of duty also reaches, on that same line, the NIST framework for the line's own subject. Two controls connect when lines in at least 2 laws reach both. That says the same duties reach both; it does not say the two are alike, or that running either one does what a law asks.

Every duty line in the cybersecurity laws we track has been read against the framework for its subject.

Sources and licenses

ENISA Technical Implementation Guidance on Commission Implementing Regulation (EU) 2024/2690, version 1.0 (June 2025), © European Union Agency for Cybersecurity (ENISA), 2025, licensed under CC BY 4.0. The section titles and requirement text are the Annex to Implementing Regulation (EU) 2024/2690 as ENISA prints it (© European Union); each section carries its first point as its text, and ENISA's guidance, examples of evidence and tips are not reproduced.