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

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

20 of ENISA NIS2 guidance's requirements connect to 35 of NIST CSF 2.0's through 276 laws in 112 jurisdictions. Two requirements 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
ENISA NIS2 Technical Implementation Guidance, version 1.0, June 2025, with mapping table version 1.2, European Union Agency for Cybersecurity (ENISA)
To
NIST Cybersecurity Framework, version 2.0, February 2024 (NIST CSWP 29), National Institute of Standards and Technology
See also
NIST CSF 2.0 to ENISA NIS2 guidance, 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

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

and 51 more, every one in the free file.

GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 60 40 56 in force, 4 not yet in force
The 60 laws behind 1.1 and GV.PO-01

and 50 more, every one in the free file.

GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and... 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind 1.1 and GV.RR-01

and 21 more, every one in the free file.

PR.AT-02Individuals in specialized roles are provided with awareness and training so that they... 24 21 23 in force, 1 proposed
The 24 laws behind 1.1 and PR.AT-02

and 14 more, every one in the free file.

GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind 1.1 and GV.RR-02

and 14 more, every one in the free file.

ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 10 10 10 in force
The 10 laws behind 1.1 and ID.AM-08
PR.PS-04Log records are generated and made available for continuous monitoring 7 6 6 in force, 1 not yet in force
The 7 laws behind 1.1 and PR.PS-04
ID.RA-05Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent... 5 5 4 in force, 1 not yet in force
The 5 laws behind 1.1 and ID.RA-05
ID.AM-02Inventories of software, services, and systems managed by the organization are maintained 4 4 4 in force
The 4 laws behind 1.1 and ID.AM-02
ID.AM-05Assets are prioritized based on classification, criticality, resources, and impact on... 3 3 2 in force, 1 not yet in force
The 3 laws behind 1.1 and ID.AM-05
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 3 3 1 in force, 2 proposed
The 3 laws behind 1.1 and ID.RA-06
ID.AM-07Inventories of data and corresponding metadata for designated data types are maintained 2 2 2 in force
The 2 laws behind 1.1 and ID.AM-07
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 1.1 and ID.IM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 2 2 in force
The 2 laws behind 1.1 and ID.IM-02
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 2 2 2 in force
The 2 laws behind 1.1 and ID.IM-04
PR.AT-01Personnel are provided with awareness and training so that they possess the knowledge... 2 2 2 in force
The 2 laws behind 1.1 and PR.AT-01
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 2 2 2 in force
The 2 laws behind 1.1 and PR.IR-03
DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 2 2 1 in force, 1 not yet in force
The 2 laws behind 1.1 and DE.CM-09
1.2Roles, responsibilities and authorities GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 61 41 55 in force, 4 not yet in force, 2 proposed
The 61 laws behind 1.2 and GV.OC-03

and 51 more, every one in the free file.

GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 60 40 56 in force, 4 not yet in force
The 60 laws behind 1.2 and GV.PO-01

and 50 more, every one in the free file.

GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and... 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind 1.2 and GV.RR-01

and 21 more, every one in the free file.

PR.AT-02Individuals in specialized roles are provided with awareness and training so that they... 24 21 23 in force, 1 proposed
The 24 laws behind 1.2 and PR.AT-02

and 14 more, every one in the free file.

GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind 1.2 and GV.RR-02

and 14 more, every one in the free file.

PR.PS-04Log records are generated and made available for continuous monitoring 6 5 5 in force, 1 not yet in force
The 6 laws behind 1.2 and PR.PS-04
ID.RA-05Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent... 5 5 4 in force, 1 not yet in force
The 5 laws behind 1.2 and ID.RA-05
ID.AM-02Inventories of software, services, and systems managed by the organization are maintained 4 4 4 in force
The 4 laws behind 1.2 and ID.AM-02
ID.AM-05Assets are prioritized based on classification, criticality, resources, and impact on... 3 3 2 in force, 1 not yet in force
The 3 laws behind 1.2 and ID.AM-05
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 3 3 1 in force, 2 proposed
The 3 laws behind 1.2 and ID.RA-06
ID.AM-07Inventories of data and corresponding metadata for designated data types are maintained 2 2 2 in force
The 2 laws behind 1.2 and ID.AM-07
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 1.2 and ID.IM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 2 2 in force
The 2 laws behind 1.2 and ID.IM-02
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 2 2 2 in force
The 2 laws behind 1.2 and ID.IM-04
PR.AT-01Personnel are provided with awareness and training so that they possess the knowledge... 2 2 2 in force
The 2 laws behind 1.2 and PR.AT-01
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 2 2 2 in force
The 2 laws behind 1.2 and PR.IR-03
DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 2 2 1 in force, 1 not yet in force
The 2 laws behind 1.2 and DE.CM-09
2.1Risk management framework PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected 40 37 39 in force, 1 not yet in force
The 40 laws behind 2.1 and PR.DS-01

and 30 more, every one in the free file.

PR.PS-06Secure software development practices are integrated, and their performance is... 29 18 25 in force, 4 not yet in force
The 29 laws behind 2.1 and PR.PS-06

and 19 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 24 18 23 in force, 1 not yet in force
The 24 laws behind 2.1 and ID.IM-04

and 14 more, every one in the free file.

DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 2.1 and DE.CM-09

and 2 more, every one in the free file.

PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed,... 9 5 9 in force
The 9 laws behind 2.1 and PR.AA-05
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established 8 7 7 in force, 1 not yet in force
The 8 laws behind 2.1 and ID.RA-08
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected 8 7 8 in force
The 8 laws behind 2.1 and PR.DS-02
ID.RA-01Vulnerabilities in assets are identified, validated, and recorded 6 4 6 in force
The 6 laws behind 2.1 and ID.RA-01
GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 5 5 4 in force, 1 not yet in force
The 5 laws behind 2.1 and GV.PO-01
PR.AA-03Users, services, and hardware are authenticated 4 3 4 in force
The 4 laws behind 2.1 and PR.AA-03
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 3 3 3 in force
The 3 laws behind 2.1 and GV.OC-03
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 3 3 3 in force
The 3 laws behind 2.1 and ID.AM-08
ID.IM-01Improvements are identified from evaluations 3 3 3 in force
The 3 laws behind 2.1 and ID.IM-01
PR.DS-11Backups of data are created, protected, maintained, and tested 3 3 3 in force
The 3 laws behind 2.1 and PR.DS-11
RS.CO-02Internal and external stakeholders are notified of incidents 3 3 3 in force
The 3 laws behind 2.1 and RS.CO-02
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 2.1 and GV.RR-02
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 2 2 2 in force
The 2 laws behind 2.1 and ID.RA-06
PR.PS-01Configuration management practices are established and applied 2 2 2 in force
The 2 laws behind 2.1 and PR.PS-01
DE.CM-01Networks and network services are monitored to find potentially adverse events 2 2 2 in force
The 2 laws behind 2.1 and DE.CM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 1 2 in force
The 2 laws behind 2.1 and ID.IM-02
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 2 1 1 in force, 1 not yet in force
The 2 laws behind 2.1 and PR.PS-02
2.2Compliance monitoring GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 61 41 55 in force, 4 not yet in force, 2 proposed
The 61 laws behind 2.2 and GV.OC-03

and 51 more, every one in the free file.

GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 60 40 56 in force, 4 not yet in force
The 60 laws behind 2.2 and GV.PO-01

and 50 more, every one in the free file.

GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and... 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind 2.2 and GV.RR-01

and 21 more, every one in the free file.

PR.AT-02Individuals in specialized roles are provided with awareness and training so that they... 24 21 23 in force, 1 proposed
The 24 laws behind 2.2 and PR.AT-02

and 14 more, every one in the free file.

GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind 2.2 and GV.RR-02

and 14 more, every one in the free file.

PR.PS-04Log records are generated and made available for continuous monitoring 6 5 5 in force, 1 not yet in force
The 6 laws behind 2.2 and PR.PS-04
ID.RA-05Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent... 5 5 4 in force, 1 not yet in force
The 5 laws behind 2.2 and ID.RA-05
ID.AM-02Inventories of software, services, and systems managed by the organization are maintained 4 4 4 in force
The 4 laws behind 2.2 and ID.AM-02
ID.AM-05Assets are prioritized based on classification, criticality, resources, and impact on... 3 3 2 in force, 1 not yet in force
The 3 laws behind 2.2 and ID.AM-05
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 3 3 1 in force, 2 proposed
The 3 laws behind 2.2 and ID.RA-06
ID.AM-07Inventories of data and corresponding metadata for designated data types are maintained 2 2 2 in force
The 2 laws behind 2.2 and ID.AM-07
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 2.2 and ID.IM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 2 2 in force
The 2 laws behind 2.2 and ID.IM-02
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 2 2 2 in force
The 2 laws behind 2.2 and ID.IM-04
PR.AT-01Personnel are provided with awareness and training so that they possess the knowledge... 2 2 2 in force
The 2 laws behind 2.2 and PR.AT-01
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 2 2 2 in force
The 2 laws behind 2.2 and PR.IR-03
DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 2 2 1 in force, 1 not yet in force
The 2 laws behind 2.2 and DE.CM-09
2.3Independent review of information and network security ID.IM-01Improvements are identified from evaluations 3 3 3 in force
The 3 laws behind 2.3 and ID.IM-01
3.1Incident handling policy RS.CO-02Internal and external stakeholders are notified of incidents 100 67 91 in force, 4 not yet in force, 5 proposed
The 100 laws behind 3.1 and RS.CO-02

and 90 more, every one in the free file.

RS.CO-03Information is shared with designated internal and external stakeholders 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind 3.1 and RS.CO-03

and 39 more, every one in the free file.

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

and 30 more, every one in the free file.

PR.PS-06Secure software development practices are integrated, and their performance is... 29 18 25 in force, 4 not yet in force
The 29 laws behind 3.1 and PR.PS-06

and 19 more, every one in the free file.

GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 25 24 22 in force, 1 not yet in force, 2 proposed
The 25 laws behind 3.1 and GV.OC-03

and 15 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 24 18 23 in force, 1 not yet in force
The 24 laws behind 3.1 and ID.IM-04

and 14 more, every one in the free file.

DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 3.1 and DE.CM-09

and 2 more, every one in the free file.

PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed,... 9 5 9 in force
The 9 laws behind 3.1 and PR.AA-05
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established 8 7 7 in force, 1 not yet in force
The 8 laws behind 3.1 and ID.RA-08
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected 8 7 8 in force
The 8 laws behind 3.1 and PR.DS-02
ID.RA-01Vulnerabilities in assets are identified, validated, and recorded 6 4 6 in force
The 6 laws behind 3.1 and ID.RA-01
RS.MI-01Incidents are contained 5 5 3 in force, 2 not yet in force
The 5 laws behind 3.1 and RS.MI-01
GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 4 4 3 in force, 1 not yet in force
The 4 laws behind 3.1 and GV.PO-01
PR.AA-03Users, services, and hardware are authenticated 4 3 4 in force
The 4 laws behind 3.1 and PR.AA-03
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 3 3 3 in force
The 3 laws behind 3.1 and GV.RR-02
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 3 3 3 in force
The 3 laws behind 3.1 and ID.AM-08
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 3 3 3 in force
The 3 laws behind 3.1 and ID.RA-06
PR.DS-11Backups of data are created, protected, maintained, and tested 3 3 3 in force
The 3 laws behind 3.1 and PR.DS-11
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related... 3 3 3 in force
The 3 laws behind 3.1 and RC.RP-06
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 3 2 2 in force, 1 not yet in force
The 3 laws behind 3.1 and PR.PS-02
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 3.1 and ID.IM-01
PR.PS-01Configuration management practices are established and applied 2 2 2 in force
The 2 laws behind 3.1 and PR.PS-01
PR.PS-04Log records are generated and made available for continuous monitoring 2 2 2 in force
The 2 laws behind 3.1 and PR.PS-04
DE.CM-01Networks and network services are monitored to find potentially adverse events 2 2 2 in force
The 2 laws behind 3.1 and DE.CM-01
RS.MA-03Incidents are categorized and prioritized 2 2 2 in force
The 2 laws behind 3.1 and RS.MA-03
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 1 2 in force
The 2 laws behind 3.1 and ID.IM-02
3.2Monitoring and logging GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 61 41 55 in force, 4 not yet in force, 2 proposed
The 61 laws behind 3.2 and GV.OC-03

and 51 more, every one in the free file.

GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 60 40 56 in force, 4 not yet in force
The 60 laws behind 3.2 and GV.PO-01

and 50 more, every one in the free file.

GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and... 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind 3.2 and GV.RR-01

and 21 more, every one in the free file.

PR.AT-02Individuals in specialized roles are provided with awareness and training so that they... 24 21 23 in force, 1 proposed
The 24 laws behind 3.2 and PR.AT-02

and 14 more, every one in the free file.

GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind 3.2 and GV.RR-02

and 14 more, every one in the free file.

ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 10 10 10 in force
The 10 laws behind 3.2 and ID.AM-08
PR.PS-04Log records are generated and made available for continuous monitoring 7 6 6 in force, 1 not yet in force
The 7 laws behind 3.2 and PR.PS-04
ID.RA-05Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent... 5 5 4 in force, 1 not yet in force
The 5 laws behind 3.2 and ID.RA-05
ID.AM-02Inventories of software, services, and systems managed by the organization are maintained 4 4 4 in force
The 4 laws behind 3.2 and ID.AM-02
ID.AM-05Assets are prioritized based on classification, criticality, resources, and impact on... 3 3 2 in force, 1 not yet in force
The 3 laws behind 3.2 and ID.AM-05
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 3 3 1 in force, 2 proposed
The 3 laws behind 3.2 and ID.RA-06
ID.AM-07Inventories of data and corresponding metadata for designated data types are maintained 2 2 2 in force
The 2 laws behind 3.2 and ID.AM-07
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 3.2 and ID.IM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 2 2 in force
The 2 laws behind 3.2 and ID.IM-02
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 2 2 2 in force
The 2 laws behind 3.2 and ID.IM-04
PR.AT-01Personnel are provided with awareness and training so that they possess the knowledge... 2 2 2 in force
The 2 laws behind 3.2 and PR.AT-01
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 2 2 2 in force
The 2 laws behind 3.2 and PR.IR-03
DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 2 2 1 in force, 1 not yet in force
The 2 laws behind 3.2 and DE.CM-09
3.4Event assessment and classification RS.CO-02Internal and external stakeholders are notified of incidents 98 67 89 in force, 4 not yet in force, 5 proposed
The 98 laws behind 3.4 and RS.CO-02

and 88 more, every one in the free file.

RS.CO-03Information is shared with designated internal and external stakeholders 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind 3.4 and RS.CO-03

and 39 more, every one in the free file.

GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 23 22 20 in force, 1 not yet in force, 2 proposed
The 23 laws behind 3.4 and GV.OC-03

and 13 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 7 6 6 in force, 1 not yet in force
The 7 laws behind 3.4 and ID.IM-04
RS.MI-01Incidents are contained 5 5 3 in force, 2 not yet in force
The 5 laws behind 3.4 and RS.MI-01
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related... 3 3 3 in force
The 3 laws behind 3.4 and RC.RP-06
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 3.4 and GV.RR-02
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 2 2 2 in force
The 2 laws behind 3.4 and ID.RA-06
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 3.4 and ID.IM-01
RS.MA-03Incidents are categorized and prioritized 2 2 2 in force
The 2 laws behind 3.4 and RS.MA-03
3.5Incident response RS.CO-02Internal and external stakeholders are notified of incidents 101 69 92 in force, 4 not yet in force, 5 proposed
The 101 laws behind 3.5 and RS.CO-02

and 91 more, every one in the free file.

RS.CO-03Information is shared with designated internal and external stakeholders 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind 3.5 and RS.CO-03

and 39 more, every one in the free file.

GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 23 22 20 in force, 1 not yet in force, 2 proposed
The 23 laws behind 3.5 and GV.OC-03

and 13 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 7 6 6 in force, 1 not yet in force
The 7 laws behind 3.5 and ID.IM-04
RS.MI-01Incidents are contained 5 5 3 in force, 2 not yet in force
The 5 laws behind 3.5 and RS.MI-01
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related... 3 3 3 in force
The 3 laws behind 3.5 and RC.RP-06
RC.CO-04Public updates on incident recovery are shared using approved methods and messaging 3 3 3 in force
The 3 laws behind 3.5 and RC.CO-04
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 3.5 and GV.RR-02
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 2 2 2 in force
The 2 laws behind 3.5 and ID.RA-06
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 3.5 and ID.IM-01
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 2 2 2 in force
The 2 laws behind 3.5 and PR.PS-02
RS.MA-03Incidents are categorized and prioritized 2 2 2 in force
The 2 laws behind 3.5 and RS.MA-03
3.6Post-incident reviews RS.CO-02Internal and external stakeholders are notified of incidents 97 66 88 in force, 4 not yet in force, 5 proposed
The 97 laws behind 3.6 and RS.CO-02

and 87 more, every one in the free file.

RS.CO-03Information is shared with designated internal and external stakeholders 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind 3.6 and RS.CO-03

and 39 more, every one in the free file.

GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 23 22 20 in force, 1 not yet in force, 2 proposed
The 23 laws behind 3.6 and GV.OC-03

and 13 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 7 6 6 in force, 1 not yet in force
The 7 laws behind 3.6 and ID.IM-04
RS.MI-01Incidents are contained 5 5 3 in force, 2 not yet in force
The 5 laws behind 3.6 and RS.MI-01
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related... 3 3 3 in force
The 3 laws behind 3.6 and RC.RP-06
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 3.6 and GV.RR-02
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 2 2 2 in force
The 2 laws behind 3.6 and ID.RA-06
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 3.6 and ID.IM-01
RS.MA-03Incidents are categorized and prioritized 2 2 2 in force
The 2 laws behind 3.6 and RS.MA-03
4.1Business continuity and disaster recovery plan PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected 40 37 39 in force, 1 not yet in force
The 40 laws behind 4.1 and PR.DS-01

and 30 more, every one in the free file.

PR.PS-06Secure software development practices are integrated, and their performance is... 29 18 25 in force, 4 not yet in force
The 29 laws behind 4.1 and PR.PS-06

and 19 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 24 18 23 in force, 1 not yet in force
The 24 laws behind 4.1 and ID.IM-04

and 14 more, every one in the free file.

DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 4.1 and DE.CM-09

and 2 more, every one in the free file.

PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed,... 9 5 9 in force
The 9 laws behind 4.1 and PR.AA-05
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established 8 7 7 in force, 1 not yet in force
The 8 laws behind 4.1 and ID.RA-08
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected 8 7 8 in force
The 8 laws behind 4.1 and PR.DS-02
ID.RA-01Vulnerabilities in assets are identified, validated, and recorded 6 4 6 in force
The 6 laws behind 4.1 and ID.RA-01
GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 4 4 3 in force, 1 not yet in force
The 4 laws behind 4.1 and GV.PO-01
PR.AA-03Users, services, and hardware are authenticated 4 3 4 in force
The 4 laws behind 4.1 and PR.AA-03
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 3 3 3 in force
The 3 laws behind 4.1 and GV.OC-03
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 3 3 3 in force
The 3 laws behind 4.1 and ID.AM-08
PR.DS-11Backups of data are created, protected, maintained, and tested 3 3 3 in force
The 3 laws behind 4.1 and PR.DS-11
RS.CO-02Internal and external stakeholders are notified of incidents 3 3 3 in force
The 3 laws behind 4.1 and RS.CO-02
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 4.1 and GV.RR-02
PR.PS-01Configuration management practices are established and applied 2 2 2 in force
The 2 laws behind 4.1 and PR.PS-01
DE.CM-01Networks and network services are monitored to find potentially adverse events 2 2 2 in force
The 2 laws behind 4.1 and DE.CM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 1 2 in force
The 2 laws behind 4.1 and ID.IM-02
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 2 1 1 in force, 1 not yet in force
The 2 laws behind 4.1 and PR.PS-02
4.2Backup and redundancy management ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 10 10 10 in force
The 10 laws behind 4.2 and ID.AM-08
4.3Crisis management RS.CO-02Internal and external stakeholders are notified of incidents 97 66 88 in force, 4 not yet in force, 5 proposed
The 97 laws behind 4.3 and RS.CO-02

and 87 more, every one in the free file.

RS.CO-03Information is shared with designated internal and external stakeholders 49 37 45 in force, 2 not yet in force, 2 proposed
The 49 laws behind 4.3 and RS.CO-03

and 39 more, every one in the free file.

GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 23 22 20 in force, 1 not yet in force, 2 proposed
The 23 laws behind 4.3 and GV.OC-03

and 13 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 7 6 6 in force, 1 not yet in force
The 7 laws behind 4.3 and ID.IM-04
RS.MI-01Incidents are contained 5 5 3 in force, 2 not yet in force
The 5 laws behind 4.3 and RS.MI-01
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related... 3 3 3 in force
The 3 laws behind 4.3 and RC.RP-06
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 4.3 and GV.RR-02
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 2 2 2 in force
The 2 laws behind 4.3 and ID.RA-06
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 4.3 and ID.IM-01
RS.MA-03Incidents are categorized and prioritized 2 2 2 in force
The 2 laws behind 4.3 and RS.MA-03
6.2Secure development life cycle PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected 40 37 39 in force, 1 not yet in force
The 40 laws behind 6.2 and PR.DS-01

and 30 more, every one in the free file.

PR.PS-06Secure software development practices are integrated, and their performance is... 29 18 25 in force, 4 not yet in force
The 29 laws behind 6.2 and PR.PS-06

and 19 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 24 18 23 in force, 1 not yet in force
The 24 laws behind 6.2 and ID.IM-04

and 14 more, every one in the free file.

DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 6.2 and DE.CM-09

and 2 more, every one in the free file.

PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed,... 9 5 9 in force
The 9 laws behind 6.2 and PR.AA-05
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established 8 7 7 in force, 1 not yet in force
The 8 laws behind 6.2 and ID.RA-08
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected 8 7 8 in force
The 8 laws behind 6.2 and PR.DS-02
ID.RA-01Vulnerabilities in assets are identified, validated, and recorded 6 4 6 in force
The 6 laws behind 6.2 and ID.RA-01
GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 4 4 3 in force, 1 not yet in force
The 4 laws behind 6.2 and GV.PO-01
PR.AA-03Users, services, and hardware are authenticated 4 3 4 in force
The 4 laws behind 6.2 and PR.AA-03
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 3 3 3 in force
The 3 laws behind 6.2 and GV.OC-03
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 3 3 3 in force
The 3 laws behind 6.2 and ID.AM-08
PR.DS-11Backups of data are created, protected, maintained, and tested 3 3 3 in force
The 3 laws behind 6.2 and PR.DS-11
RS.CO-02Internal and external stakeholders are notified of incidents 3 3 3 in force
The 3 laws behind 6.2 and RS.CO-02
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 6.2 and GV.RR-02
PR.PS-01Configuration management practices are established and applied 2 2 2 in force
The 2 laws behind 6.2 and PR.PS-01
DE.CM-01Networks and network services are monitored to find potentially adverse events 2 2 2 in force
The 2 laws behind 6.2 and DE.CM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 1 2 in force
The 2 laws behind 6.2 and ID.IM-02
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 2 1 1 in force, 1 not yet in force
The 2 laws behind 6.2 and PR.PS-02
6.5Security testing PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected 40 37 39 in force, 1 not yet in force
The 40 laws behind 6.5 and PR.DS-01

and 30 more, every one in the free file.

PR.PS-06Secure software development practices are integrated, and their performance is... 29 18 25 in force, 4 not yet in force
The 29 laws behind 6.5 and PR.PS-06

and 19 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 24 18 23 in force, 1 not yet in force
The 24 laws behind 6.5 and ID.IM-04

and 14 more, every one in the free file.

DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 6.5 and DE.CM-09

and 2 more, every one in the free file.

PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed,... 9 5 9 in force
The 9 laws behind 6.5 and PR.AA-05
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established 8 7 7 in force, 1 not yet in force
The 8 laws behind 6.5 and ID.RA-08
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected 8 7 8 in force
The 8 laws behind 6.5 and PR.DS-02
ID.RA-01Vulnerabilities in assets are identified, validated, and recorded 6 4 6 in force
The 6 laws behind 6.5 and ID.RA-01
GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 4 4 3 in force, 1 not yet in force
The 4 laws behind 6.5 and GV.PO-01
PR.AA-03Users, services, and hardware are authenticated 4 3 4 in force
The 4 laws behind 6.5 and PR.AA-03
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 3 3 3 in force
The 3 laws behind 6.5 and GV.OC-03
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 3 3 3 in force
The 3 laws behind 6.5 and ID.AM-08
PR.DS-11Backups of data are created, protected, maintained, and tested 3 3 3 in force
The 3 laws behind 6.5 and PR.DS-11
RS.CO-02Internal and external stakeholders are notified of incidents 3 3 3 in force
The 3 laws behind 6.5 and RS.CO-02
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 6.5 and GV.RR-02
PR.PS-01Configuration management practices are established and applied 2 2 2 in force
The 2 laws behind 6.5 and PR.PS-01
DE.CM-01Networks and network services are monitored to find potentially adverse events 2 2 2 in force
The 2 laws behind 6.5 and DE.CM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 1 2 in force
The 2 laws behind 6.5 and ID.IM-02
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 2 1 1 in force, 1 not yet in force
The 2 laws behind 6.5 and PR.PS-02
6.10Vulnerability handling and disclosure PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected 40 37 39 in force, 1 not yet in force
The 40 laws behind 6.10 and PR.DS-01

and 30 more, every one in the free file.

PR.PS-06Secure software development practices are integrated, and their performance is... 29 18 25 in force, 4 not yet in force
The 29 laws behind 6.10 and PR.PS-06

and 19 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 24 18 23 in force, 1 not yet in force
The 24 laws behind 6.10 and ID.IM-04

and 14 more, every one in the free file.

DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 6.10 and DE.CM-09

and 2 more, every one in the free file.

RS.CO-02Internal and external stakeholders are notified of incidents 9 8 9 in force
The 9 laws behind 6.10 and RS.CO-02
PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed,... 9 5 9 in force
The 9 laws behind 6.10 and PR.AA-05
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established 8 7 7 in force, 1 not yet in force
The 8 laws behind 6.10 and ID.RA-08
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected 8 7 8 in force
The 8 laws behind 6.10 and PR.DS-02
ID.RA-01Vulnerabilities in assets are identified, validated, and recorded 6 4 6 in force
The 6 laws behind 6.10 and ID.RA-01
GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 4 4 3 in force, 1 not yet in force
The 4 laws behind 6.10 and GV.PO-01
PR.AA-03Users, services, and hardware are authenticated 4 3 4 in force
The 4 laws behind 6.10 and PR.AA-03
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 3 3 3 in force
The 3 laws behind 6.10 and GV.OC-03
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 3 3 3 in force
The 3 laws behind 6.10 and ID.AM-08
PR.DS-11Backups of data are created, protected, maintained, and tested 3 3 3 in force
The 3 laws behind 6.10 and PR.DS-11
RC.CO-04Public updates on incident recovery are shared using approved methods and messaging 3 3 3 in force
The 3 laws behind 6.10 and RC.CO-04
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 3 2 2 in force, 1 not yet in force
The 3 laws behind 6.10 and PR.PS-02
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 6.10 and GV.RR-02
PR.PS-01Configuration management practices are established and applied 2 2 2 in force
The 2 laws behind 6.10 and PR.PS-01
DE.CM-01Networks and network services are monitored to find potentially adverse events 2 2 2 in force
The 2 laws behind 6.10 and DE.CM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 1 2 in force
The 2 laws behind 6.10 and ID.IM-02
9.1Cryptography PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected 40 37 39 in force, 1 not yet in force
The 40 laws behind 9.1 and PR.DS-01

and 30 more, every one in the free file.

PR.PS-06Secure software development practices are integrated, and their performance is... 29 18 25 in force, 4 not yet in force
The 29 laws behind 9.1 and PR.PS-06

and 19 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 24 18 23 in force, 1 not yet in force
The 24 laws behind 9.1 and ID.IM-04

and 14 more, every one in the free file.

DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 9.1 and DE.CM-09

and 2 more, every one in the free file.

PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed,... 9 5 9 in force
The 9 laws behind 9.1 and PR.AA-05
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established 8 7 7 in force, 1 not yet in force
The 8 laws behind 9.1 and ID.RA-08
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected 8 7 8 in force
The 8 laws behind 9.1 and PR.DS-02
ID.RA-01Vulnerabilities in assets are identified, validated, and recorded 6 4 6 in force
The 6 laws behind 9.1 and ID.RA-01
GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 4 4 3 in force, 1 not yet in force
The 4 laws behind 9.1 and GV.PO-01
PR.AA-03Users, services, and hardware are authenticated 4 3 4 in force
The 4 laws behind 9.1 and PR.AA-03
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 3 3 3 in force
The 3 laws behind 9.1 and GV.OC-03
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 3 3 3 in force
The 3 laws behind 9.1 and ID.AM-08
PR.DS-11Backups of data are created, protected, maintained, and tested 3 3 3 in force
The 3 laws behind 9.1 and PR.DS-11
RS.CO-02Internal and external stakeholders are notified of incidents 3 3 3 in force
The 3 laws behind 9.1 and RS.CO-02
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 9.1 and GV.RR-02
PR.PS-01Configuration management practices are established and applied 2 2 2 in force
The 2 laws behind 9.1 and PR.PS-01
DE.CM-01Networks and network services are monitored to find potentially adverse events 2 2 2 in force
The 2 laws behind 9.1 and DE.CM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 1 2 in force
The 2 laws behind 9.1 and ID.IM-02
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 2 1 1 in force, 1 not yet in force
The 2 laws behind 9.1 and PR.PS-02
11.2Management of access rights PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protected 40 37 39 in force, 1 not yet in force
The 40 laws behind 11.2 and PR.DS-01

and 30 more, every one in the free file.

PR.PS-06Secure software development practices are integrated, and their performance is... 29 18 25 in force, 4 not yet in force
The 29 laws behind 11.2 and PR.PS-06

and 19 more, every one in the free file.

ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 24 18 23 in force, 1 not yet in force
The 24 laws behind 11.2 and ID.IM-04

and 14 more, every one in the free file.

DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 12 11 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 11.2 and DE.CM-09

and 2 more, every one in the free file.

PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed,... 9 5 9 in force
The 9 laws behind 11.2 and PR.AA-05
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are established 8 7 7 in force, 1 not yet in force
The 8 laws behind 11.2 and ID.RA-08
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected 8 7 8 in force
The 8 laws behind 11.2 and PR.DS-02
ID.RA-01Vulnerabilities in assets are identified, validated, and recorded 6 4 6 in force
The 6 laws behind 11.2 and ID.RA-01
GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 4 4 3 in force, 1 not yet in force
The 4 laws behind 11.2 and GV.PO-01
PR.AA-03Users, services, and hardware are authenticated 4 3 4 in force
The 4 laws behind 11.2 and PR.AA-03
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 3 3 3 in force
The 3 laws behind 11.2 and GV.OC-03
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 3 3 3 in force
The 3 laws behind 11.2 and ID.AM-08
PR.DS-11Backups of data are created, protected, maintained, and tested 3 3 3 in force
The 3 laws behind 11.2 and PR.DS-11
RS.CO-02Internal and external stakeholders are notified of incidents 3 3 3 in force
The 3 laws behind 11.2 and RS.CO-02
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 2 2 2 in force
The 2 laws behind 11.2 and GV.RR-02
PR.PS-01Configuration management practices are established and applied 2 2 2 in force
The 2 laws behind 11.2 and PR.PS-01
DE.CM-01Networks and network services are monitored to find potentially adverse events 2 2 2 in force
The 2 laws behind 11.2 and DE.CM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 1 2 in force
The 2 laws behind 11.2 and ID.IM-02
PR.PS-02Software is maintained, replaced, and removed commensurate with risk 2 1 1 in force, 1 not yet in force
The 2 laws behind 11.2 and PR.PS-02
12.2Handling of assets ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cycles 10 10 10 in force
The 10 laws behind 12.2 and ID.AM-08
12.4Asset inventory GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including... 61 41 55 in force, 4 not yet in force, 2 proposed
The 61 laws behind 12.4 and GV.OC-03

and 51 more, every one in the free file.

GV.PO-01Policy for managing cybersecurity risks is established based on organizational... 60 40 56 in force, 4 not yet in force
The 60 laws behind 12.4 and GV.PO-01

and 50 more, every one in the free file.

GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and... 31 26 28 in force, 1 not yet in force, 2 proposed
The 31 laws behind 12.4 and GV.RR-01

and 21 more, every one in the free file.

PR.AT-02Individuals in specialized roles are provided with awareness and training so that they... 24 21 23 in force, 1 proposed
The 24 laws behind 12.4 and PR.AT-02

and 14 more, every one in the free file.

GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are... 24 18 22 in force, 1 not yet in force, 1 proposed
The 24 laws behind 12.4 and GV.RR-02

and 14 more, every one in the free file.

PR.PS-04Log records are generated and made available for continuous monitoring 6 5 5 in force, 1 not yet in force
The 6 laws behind 12.4 and PR.PS-04
ID.RA-05Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent... 5 5 4 in force, 1 not yet in force
The 5 laws behind 12.4 and ID.RA-05
ID.AM-02Inventories of software, services, and systems managed by the organization are maintained 4 4 4 in force
The 4 laws behind 12.4 and ID.AM-02
ID.AM-05Assets are prioritized based on classification, criticality, resources, and impact on... 3 3 2 in force, 1 not yet in force
The 3 laws behind 12.4 and ID.AM-05
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicated 3 3 1 in force, 2 proposed
The 3 laws behind 12.4 and ID.RA-06
ID.AM-07Inventories of data and corresponding metadata for designated data types are maintained 2 2 2 in force
The 2 laws behind 12.4 and ID.AM-07
ID.IM-01Improvements are identified from evaluations 2 2 1 in force, 1 not yet in force
The 2 laws behind 12.4 and ID.IM-01
ID.IM-02Improvements are identified from security tests and exercises, including those done in... 2 2 2 in force
The 2 laws behind 12.4 and ID.IM-02
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are... 2 2 2 in force
The 2 laws behind 12.4 and ID.IM-04
PR.AT-01Personnel are provided with awareness and training so that they possess the knowledge... 2 2 2 in force
The 2 laws behind 12.4 and PR.AT-01
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 2 2 2 in force
The 2 laws behind 12.4 and PR.IR-03
DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to... 2 2 1 in force, 1 not yet in force
The 2 laws behind 12.4 and DE.CM-09
Not connected to the NIST CSF 2.0: 29 of ENISA NIS2 guidance's requirements

Short of 2 laws

The same duties reach these and a NIST CSF 2.0 control, in fewer than 2 of the laws we track.

No law we track reaches these

No duty in the laws we track reaches these requirements.

  • 3.3 Event reporting
  • 5.2 Directory of suppliers and service providers
  • 6.1 Security in acquisition of ICT services or ICT products
  • 6.3 Configuration management
  • 6.4 Change management, repairs and maintenance
  • 6.6 Security patch management
  • 6.7 Network security
  • 6.8 Network segmentation
  • 6.9 Protection against malicious and unauthorised software
  • 7.1 Policies and procedures to assess the effectiveness of cybersecurity risk-management measures
  • 8.1 Awareness raising and basic cyber hygiene practices
  • 8.2 Security training
  • 10.1 Human resources security
  • 10.2 Verification of background
  • 10.3 Termination or change of employment procedures
  • 10.4 Disciplinary process
  • 11.1 Access control policy
  • 11.3 Privileged accounts and system administration accounts
  • 11.4 Administration systems
  • 11.5 Identification
  • 11.6 Authentication
  • 11.7 Multi-factor authentication
  • 12.1 Asset classification
  • 12.3 Removable media policy
  • 12.5 Deposit, return or deletion of assets upon termination of employment
  • 13.1 Supporting utilities
  • 13.2 Protection against physical and environmental threats
  • 13.3 Perimeter and physical access control

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 requirements 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.