Law / Frameworks / NIST CSF 2.0

NIST Cybersecurity Framework

Below are its 106 controls in the framework's own order, and under each one the laws we track that bear on it. Each mapping is our reading that a law bears on a control, never a finding that running the control meets the law.

Each requirement line of the cybersecurity laws we track was read on its own and mapped to the control it bears on most closely, and to a second or third only where the line has more than one limb.

Govern

15 of 31 controls with law

The organization's cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored

Control	What it says	Laws	Places	Not yet in force	Proposed
GV.OCOrganizational Context: The circumstances - mission, stakeholder expectations, dependencies, and legal, regulatory, and contractual requirements - surrounding the organization's cybersecurity risk management decisions are understood
GV.OC-01	The organizational mission is understood and informs cybersecurity risk management no law we track	no law we track
GV.OC-02	Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and considered no law we track	no law we track
GV.OC-03	Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed 60 laws, 5 not yet in force, 2 proposed	60	51	5	2
GV.OC-04	Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated no law we track	no law we track
GV.OC-05	Outcomes, capabilities, and services that the organization depends on are understood and communicated no law we track	no law we track
GV.RMRisk Management Strategy: The organization's priorities, constraints, risk tolerance and appetite statements, and assumptions are established, communicated, and used to support operational risk decisions
GV.RM-01	Risk management objectives are established and agreed to by organizational stakeholders no law we track	no law we track
GV.RM-02	Risk appetite and risk tolerance statements are established, communicated, and maintained no law we track	no law we track
GV.RM-03	Cybersecurity risk management activities and outcomes are included in enterprise risk management processes 1 law	1	1	0	0
GV.RM-04	Strategic direction that describes appropriate risk response options is established and communicated no law we track	no law we track
GV.RM-05	Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties 1 law	1	1	0	0
GV.RM-06	A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated 5 laws, 1 not yet in force	5	5	1	0
GV.RM-07	Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions no law we track	no law we track
GV.RRRoles, Responsibilities, and Authorities: Cybersecurity roles, responsibilities, and authorities to foster accountability, performance assessment, and continuous improvement are established and communicated
GV.RR-01	Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving 25 laws, 3 not yet in force, 2 proposed	25	25	3	2
GV.RR-02	Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced 24 laws, 1 not yet in force, 2 proposed	24	22	1	2
GV.RR-03	Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies 2 laws	2	2	0	0
GV.RR-04	Cybersecurity is included in human resources practices 2 laws, 1 not yet in force	2	2	1	0
GV.POPolicy: Organizational cybersecurity policy is established, communicated, and enforced
GV.PO-01	Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced 55 laws, 6 not yet in force, 1 proposed	55	51	6	1
GV.PO-02	Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission 2 laws	2	2	0	0
GV.OVOversight: Results of organization-wide cybersecurity risk management activities and performance are used to inform, improve, and adjust the risk management strategy
GV.OV-01	Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction no law we track	no law we track
GV.OV-02	The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risks no law we track	no law we track
GV.OV-03	Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed no law we track	no law we track
GV.SCCybersecurity Supply Chain Risk Management: Cyber supply chain risk management processes are identified, established, managed, monitored, and improved by organizational stakeholders
GV.SC-01	A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholders 2 laws, 1 not yet in force	2	2	1	0
GV.SC-02	Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externally no law we track	no law we track
GV.SC-03	Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes no law we track	no law we track
GV.SC-04	Suppliers are known and prioritized by criticality no law we track	no law we track
GV.SC-05	Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties 17 laws, 3 not yet in force, 1 proposed	17	16	3	1
GV.SC-06	Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships 7 laws	7	7	0	0
GV.SC-07	The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship 4 laws, 1 not yet in force	4	4	1	0
GV.SC-08	Relevant suppliers and other third parties are included in incident planning, response, and recovery activities no law we track	no law we track
GV.SC-09	Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle no law we track	no law we track
GV.SC-10	Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement 1 law	1	1	0	0

Identify

14 of 21 controls with law

The organization's current cybersecurity risks are understood

Control	What it says	Laws	Places	Not yet in force	Proposed
ID.AMAsset Management: Assets (e.g., data, hardware, software, systems, facilities, services, people) that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to organizational objectives and the organization's risk strategy
ID.AM-01	Inventories of hardware managed by the organization are maintained no law we track	no law we track
ID.AM-02	Inventories of software, services, and systems managed by the organization are maintained 1 law	1	1	0	0
ID.AM-03	Representations of the organization's authorized network communication and internal and external network data flows are maintained no law we track	no law we track
ID.AM-04	Inventories of services provided by suppliers are maintained 1 law	1	1	0	0
ID.AM-05	Assets are prioritized based on classification, criticality, resources, and impact on the mission 4 laws, 1 not yet in force	4	4	1	0
ID.AM-07	Inventories of data and corresponding metadata for designated data types are maintained 1 law	1	1	0	0
ID.AM-08	Systems, hardware, software, services, and data are managed throughout their life cycles 25 laws, 3 not yet in force	25	25	3	0
ID.RARisk Assessment: The cybersecurity risk to the organization, assets, and individuals is understood by the organization
ID.RA-01	Vulnerabilities in assets are identified, validated, and recorded 1 law	1	1	0	0
ID.RA-02	Cyber threat intelligence is received from information sharing forums and sources no law we track	no law we track
ID.RA-03	Internal and external threats to the organization are identified and recorded no law we track	no law we track
ID.RA-04	Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded 1 law	1	1	0	0
ID.RA-05	Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization 19 laws, 2 not yet in force, 3 proposed	19	19	2	3
ID.RA-06	Risk responses are chosen, prioritized, planned, tracked, and communicated 34 laws, 1 not yet in force, 4 proposed	34	31	1	4
ID.RA-07	Changes and exceptions are managed, assessed for risk impact, recorded, and tracked no law we track	no law we track
ID.RA-08	Processes for receiving, analyzing, and responding to vulnerability disclosures are established 5 laws, 1 not yet in force	5	5	1	0
ID.RA-09	The authenticity and integrity of hardware and software are assessed prior to acquisition and use 1 law, 1 not yet in force	1	1	1	0
ID.RA-10	Critical suppliers are assessed prior to acquisition no law we track	no law we track
ID.IMImprovement: Improvements to organizational cybersecurity risk management processes, procedures and activities are identified across all CSF Functions
ID.IM-01	Improvements are identified from evaluations 18 laws, 3 not yet in force	18	16	3	0
ID.IM-02	Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties 1 law	1	1	0	0
ID.IM-03	Improvements are identified from execution of operational processes, procedures, and activities no law we track	no law we track
ID.IM-04	Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved 12 laws, 1 not yet in force	12	10	1	0

Protect

16 of 22 controls with law

Safeguards to manage the organization's cybersecurity risks are used

Control	What it says	Laws	Places	Not yet in force	Proposed
PR.AAIdentity Management, Authentication, and Access Control: Access to physical and logical assets is limited to authorized users, services, and hardware and managed commensurate with the assessed risk of unauthorized access
PR.AA-01	Identities and credentials for authorized users, services, and hardware are managed by the organization no law we track	no law we track
PR.AA-02	Identities are proofed and bound to credentials based on the context of interactions no law we track	no law we track
PR.AA-03	Users, services, and hardware are authenticated 4 laws	4	4	0	0
PR.AA-04	Identity assertions are protected, conveyed, and verified no law we track	no law we track
PR.AA-05	Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties 2 laws	2	2	0	0
PR.AA-06	Physical access to assets is managed, monitored, and enforced commensurate with risk 1 law	1	1	0	0
PR.ATAwareness and Training: The organization's personnel are provided with cybersecurity awareness and training so that they can perform their cybersecurity-related tasks
PR.AT-01	Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind 2 laws	2	2	0	0
PR.AT-02	Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind 20 laws, 2 not yet in force, 1 proposed	20	20	2	1
PR.DSData Security: Data are managed consistent with the organization's risk strategy to protect the confidentiality, integrity, and availability of information
PR.DS-01	The confidentiality, integrity, and availability of data-at-rest are protected 38 laws, 5 not yet in force	38	35	5	0
PR.DS-02	The confidentiality, integrity, and availability of data-in-transit are protected 5 laws, 1 not yet in force	5	5	1	0
PR.DS-10	The confidentiality, integrity, and availability of data-in-use are protected no law we track	no law we track
PR.DS-11	Backups of data are created, protected, maintained, and tested 2 laws	2	2	0	0
PR.PSPlatform Security: The hardware, software (e.g., firmware, operating systems, applications), and services of physical and virtual platforms are managed consistent with the organization's risk strategy to protect their confidentiality, integrity, and availability
PR.PS-01	Configuration management practices are established and applied 1 law	1	1	0	0
PR.PS-02	Software is maintained, replaced, and removed commensurate with risk 5 laws, 1 not yet in force	5	5	1	0
PR.PS-03	Hardware is maintained, replaced, and removed commensurate with risk 1 law	1	1	0	0
PR.PS-04	Log records are generated and made available for continuous monitoring 6 laws	6	6	0	0
PR.PS-05	Installation and execution of unauthorized software are prevented 1 law	1	1	0	0
PR.PS-06	Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle 10 laws, 1 not yet in force	10	10	1	0
PR.IRTechnology Infrastructure Resilience: Security architectures are managed with the organization's risk strategy to protect asset confidentiality, integrity, and availability, and organizational resilience
PR.IR-01	Networks and environments are protected from unauthorized logical access and usage 9 laws	9	9	0	0
PR.IR-02	The organization's technology assets are protected from environmental threats no law we track	no law we track
PR.IR-03	Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 7 laws, 1 not yet in force	7	7	1	0
PR.IR-04	Adequate resource capacity to ensure availability is maintained no law we track	no law we track

Detect

4 of 11 controls with law

Possible cybersecurity attacks and compromises are found and analyzed

Control	What it says	Laws	Places	Not yet in force	Proposed
DE.AEAdverse Event Analysis: Anomalies, indicators of compromise, and other potentially adverse events are analyzed to characterize the events and detect cybersecurity incidents
DE.AE-02	Potentially adverse events are analyzed to better understand associated activities no law we track	no law we track
DE.AE-03	Information is correlated from multiple sources no law we track	no law we track
DE.AE-04	The estimated impact and scope of adverse events are understood no law we track	no law we track
DE.AE-06	Information on adverse events is provided to authorized staff and tools 1 law	1	1	0	0
DE.AE-07	Cyber threat intelligence and other contextual information are integrated into the analysis no law we track	no law we track
DE.AE-08	Incidents are declared when adverse events meet the defined incident criteria 1 law	1	1	0	0
DE.CMContinuous Monitoring: Assets are monitored to find anomalies, indicators of compromise, and other potentially adverse events
DE.CM-01	Networks and network services are monitored to find potentially adverse events 2 laws	2	2	0	0
DE.CM-02	The physical environment is monitored to find potentially adverse events no law we track	no law we track
DE.CM-03	Personnel activity and technology usage are monitored to find potentially adverse events no law we track	no law we track
DE.CM-06	External service provider activities and services are monitored to find potentially adverse events no law we track	no law we track
DE.CM-09	Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events 9 laws, 1 not yet in force, 1 proposed	9	8	1	1

Respond

8 of 13 controls with law

Actions regarding a detected cybersecurity incident are taken

Control	What it says	Laws	Places	Not yet in force	Proposed
RS.MAIncident Management: Responses to detected cybersecurity incidents are managed
RS.MA-01	The incident response plan is executed in coordination with relevant third parties once an incident is declared 3 laws	3	3	0	0
RS.MA-02	Incident reports are triaged and validated no law we track	no law we track
RS.MA-03	Incidents are categorized and prioritized 2 laws	2	2	0	0
RS.MA-04	Incidents are escalated or elevated as needed no law we track	no law we track
RS.MA-05	The criteria for initiating incident recovery are applied no law we track	no law we track
RS.ANIncident Analysis: Investigations are conducted to ensure effective response and support forensics and recovery activities
RS.AN-03	Analysis is performed to establish what has taken place during an incident and the root cause of the incident 1 law	1	1	0	0
RS.AN-06	Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved 1 law	1	1	0	0
RS.AN-07	Incident data and metadata are collected, and their integrity and provenance are preserved 5 laws, 1 not yet in force	5	4	1	0
RS.AN-08	An incident's magnitude is estimated and validated no law we track	no law we track
RS.COIncident Response Reporting and Communication: Response activities are coordinated with internal and external stakeholders as required by laws, regulations, or policies
RS.CO-02	Internal and external stakeholders are notified of incidents 89 laws, 6 not yet in force, 4 proposed	89	71	6	4
RS.CO-03	Information is shared with designated internal and external stakeholders 36 laws, 4 not yet in force	36	34	4	0
RS.MIIncident Mitigation: Activities are performed to prevent expansion of an event and mitigate its effects
RS.MI-01	Incidents are contained 7 laws, 2 not yet in force	7	7	2	0
RS.MI-02	Incidents are eradicated no law we track	no law we track

Recover

4 of 8 controls with law

Assets and operations affected by a cybersecurity incident are restored

Control	What it says	Laws	Places	Not yet in force	Proposed
RC.RPIncident Recovery Plan Execution: Restoration activities are performed to ensure operational availability of systems and services affected by cybersecurity incidents
RC.RP-01	The recovery portion of the incident response plan is executed once initiated from the incident response process no law we track	no law we track
RC.RP-02	Recovery actions are selected, scoped, prioritized, and performed 3 laws	3	3	0	0
RC.RP-03	The integrity of backups and other restoration assets is verified before using them for restoration no law we track	no law we track
RC.RP-04	Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms no law we track	no law we track
RC.RP-05	The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed no law we track	no law we track
RC.RP-06	The end of incident recovery is declared based on criteria, and incident-related documentation is completed 3 laws	3	3	0	0
RC.COIncident Recovery Communication: Restoration activities are coordinated with internal and external parties
RC.CO-03	Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders 1 law	1	1	0	0
RC.CO-04	Public updates on incident recovery are shared using approved methods and messaging 5 laws	5	5	0	0

Cybersecurity duties with no home in NIST CSF 2.0

5 lines in 5 laws

Each line below was read against CSF 2.0 and recorded as having no control to sit under.

Sector security regimes 2

Place	Law	The duty, as read
Burundi	Loi n° 1/10, Articles 3, 4(3) and 14: security-of-service duty and diligence penalty for network operators and service providers	Maintain an operational management center for your critical infrastructure on Burundian national territory.
France	Loi n° 2022-309 du 3 mars 2022 (loi Cyberscore), Cybersecurity Audit and Disclosure Duty	Present the audit result to the consumer in a legible, clear and comprehensible form, using a colour-coded scale, in the conditions a joint ministerial order fixes.

Product security requirements 1

Place	Law	The duty, as read
China	Cybersecurity Law, Network Product and Service Security Duties	Where your product or service collects user information, disclose that collection and obtain consent, and where personal information is involved, also follow this Law's and the Personal Information Protection Law's personal-information rules, already this jurisdiction's privacy row.

Security baseline statutes 1

Place	Law	The duty, as read
India	Information Technology Act, Compensation for Failure to Protect Data, and Sensitive Personal Data or Information Rules, Reasonable Security Practices	Obtain the data provider's written consent, by letter, fax, or email, before collecting their sensitive personal data or information, let them decline or withdraw that consent, publish a privacy policy on your website, and designate a Grievance Officer who must resolve a complaint within one month.

Vulnerability and incident reporting 1

Place	Law	The duty, as read
India	CERT-In Cyber Security Directions, Incident Reporting, Logging and Time Synchronisation	If your own service is itself a data centre, a virtual private server provider, a cloud service provider, a virtual private network service, or a virtual asset (crypto) service provider, a narrower and heavier duty also applies: register and retain specified customer KYC information and financial-transaction records for five years. That narrower bound-party class is not one this profile's declared activities can identify on their own, so confirm applicability directly against the text if this describes your service.

Where the law and the framework part

45 of the 106 controls have no law we track under them.

5 requirement lines were read as having no control in this framework to sit under; they are listed above.

The framework's text

Full text of the NIST Cybersecurity Framework, public domain (a US government work).

Read it from the publisher: nvlpubs.nist.gov