Law / Frameworks / Crosswalk / NIST CSF 2.0 to NIST AI RMF

The NIST Cybersecurity Framework, mapped to the NIST AI Risk Management Framework

2 of NIST CSF 2.0's controls connect to 2 of NIST AI RMF's through 10 laws in 4 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: NIST AI Risk Management Framework, version 1.0, January 2023 (NIST AI 100-1), National Institute of Standards and Technology
See also: NIST AI RMF to NIST CSF 2.0, the other way · every pair in the crosswalk · law library as of 19 Oct 2026

Download this mapping, with every law behind each connection: nist-ai-rmf--nist-csf.csv · nist-ai-rmf--nist-csf.json

NIST CSF 2.0	NIST AI RMF	Laws	Jurisdictions	Where the laws stand
PR.PS-04Log records are generated and made available for continuous monitoring	MEASURE 2.4The functionality and behavior of the AI system and its components – as identified in...	8	4	4 in force, 4 not yet in force
	The 8 laws behind PR.PS-04 and MEASURE 2.4 AI Act, Article 12 (record-keeping), European Union from 2 Dec 2027, in 13 months AI Act, Article 19 (automatically generated logs), European Union from 2 Dec 2027, in 13 months AI Act, Article 26(6) (deployer log-keeping), European Union from 2 Dec 2027, in 13 months AI Act, Article 6(2) and Annex III, point 5(b) (creditworthiness and credit-scoring systems: provider duties), European Union from 2 Dec 2027, in 13 months Decreto Legislativo 160/2026, After-the-Fact Facial Recognition Integrated in Video Surveillance (Art. 10), Italy Decreto Legislativo 160/2026, Police Biometric AI: Dataset Labelling and Real-Time Remote Identification (Artt. 7-9, 13), Italy Central Bank of Jordan Artificial Intelligence Framework for the Banking Sector, Version 1.0, Jordan Digital Code, Chapter 23: AI system design and risk-management obligations, Kyrgyzstan
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations	MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP...	2	1	1 in force, 1 not yet in force
	The 2 laws behind PR.IR-03 and MEASURE 2.6 AI Act, Article 15 (accuracy, robustness and cybersecurity), European Union from 2 Dec 2027, in 13 months MiFID II Algorithmic Trading Controls: Resilient Systems, Testing, Kill Functionality, Records and Notification (Article 17 and RTS 6), European Union

Not connected to the NIST AI RMF: 104 of NIST CSF 2.0's controls

Short of 2 laws

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

GV.SC-06 Planning and due diligence are performed to reduce risks before entering into formal...: with GOVERN 6.1 through Guidance Note on the Consumer Protection and Responsible Adoption and Use of Artificial Intelligence and Machine Learning by Licensed Financial Institutions in the U.A.E., United Arab Emirates
ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked: with MEASURE 2.3 and MEASURE 2.7 through OSFI Guideline E-23, Model Risk Management (2027), Canada
PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed,...: with MEASURE 2.4 and MEASURE 2.7 through Decreto Legislativo 160/2026, After-the-Fact Facial Recognition Integrated in Video Surveillance (Art. 10), Italy
PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected: with MEASURE 2.7 through Superintendencia Circular on AI and Personal Data, Colombia
PR.PS-06 Secure software development practices are integrated, and their performance is...: with MEASURE 2.5 and MEASURE 2.7 through AI Act, Article 15 (accuracy, robustness and cybersecurity), European Union
DE.CM-09 Computing hardware and software, runtime environments, and their data are monitored to...: with MEASURE 2.7 through AI Act, Article 15 (accuracy, robustness and cybersecurity), European Union
RS.CO-02 Internal and external stakeholders are notified of incidents: with MANAGE 4.3 through Artificial Intelligence Risk Management and Security Act of 2026, United States

No NIST AI RMF control on the same duties

Laws reach these, but no duty that reaches one of them also reaches a NIST AI RMF control.

GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including..., 108 laws
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-01 Organizational leadership is responsible and accountable for cybersecurity risk and..., 35 laws
GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are..., 35 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.PO-01 Policy for managing cybersecurity risks is established based on organizational..., 80 laws
GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and..., 5 laws
GV.OV-02 The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage..., 1 law
GV.OV-03 Organizational cybersecurity risk management performance is evaluated and reviewed for..., 4 laws
GV.SC-01 A cybersecurity supply chain risk management program, strategy, objectives, policies,..., 7 laws
GV.SC-05 Requirements to address cybersecurity risks in supply chains are established,..., 58 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-01 Inventories of hardware managed by the organization are maintained, 1 law
ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained, 10 laws
ID.AM-04 Inventories of services provided by suppliers are maintained, 2 laws
ID.AM-05 Assets are prioritized based on classification, criticality, resources, and impact on..., 7 laws
ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained, 7 laws
ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles, 55 laws
ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded, 7 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.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent..., 30 laws
ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated, 45 laws
ID.RA-08 Processes for receiving, analyzing, and responding to vulnerability disclosures are established, 9 laws
ID.RA-09 The authenticity and integrity of hardware and software are assessed prior to..., 4 laws
ID.IM-01 Improvements are identified from evaluations, 26 laws
ID.IM-02 Improvements are identified from security tests and exercises, including those done in..., 10 laws
ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities, 3 laws
ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are..., 27 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-03 Users, services, and hardware are authenticated, 10 laws
PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk, 1 law
PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge..., 9 laws
PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they..., 30 laws
PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected, 9 laws
PR.DS-11 Backups of data are created, protected, maintained, and tested, 8 laws
PR.PS-01 Configuration management practices are established and applied, 6 laws
PR.PS-02 Software is maintained, replaced, and removed commensurate with risk, 17 laws
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-01 Networks and network services are monitored to find potentially adverse events, 7 laws
DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events, 4 laws
DE.CM-06 External service provider activities and services are monitored to find potentially..., 2 laws
RS.MA-01 The incident response plan is executed in coordination with relevant third parties..., 4 laws
RS.MA-02 Incident reports are triaged and validated, 2 laws
RS.MA-03 Incidents are categorized and prioritized, 10 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-06 Actions performed during an investigation are recorded, and the records' integrity and..., 31 laws
RS.AN-07 Incident data and metadata are collected, and their integrity and provenance are preserved, 6 laws
RS.AN-08 An incident's magnitude is estimated and validated, 3 laws
RS.CO-03 Information is shared with designated internal and external stakeholders, 60 laws
RS.MI-01 Incidents are contained, 8 laws
RC.RP-02 Recovery actions are selected, scoped, prioritized, and performed, 3 laws
RC.RP-06 The end of incident recovery is declared based on criteria, and incident-related..., 3 laws
RC.CO-03 Recovery activities and progress in restoring operational capabilities are..., 2 laws
RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging, 4 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...

Lines of the scraping and news aggregation laws we track were not read against the NIST CSF 2.0, so none of them connects the two here (how each subject's lines were read).

Lines of the age assurance and cybersecurity laws we track were not read against the NIST AI RMF, so none of them connects the two here (how each subject's lines were read).

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. Both are read line by line, so a line connects them only where it was read against both and placed on each. 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.

A line placed on a control in the framework for its own subject, whose law carries a kind of duty that reaches another of the three frameworks read line by line, is read against that one as well: every such line, or only those whose wording reaches into it. For these two:

Laws on	Read against the NIST CSF 2.0	Read against the NIST AI RMF
AI	such lines on security, robustness, resilience, vulnerabilities and logs	every line (their own framework)
scraping	not read	every line (their own framework)
news aggregation	not read	every line (their own framework)
privacy	such lines on breaches and incidents, security measures, encryption and pseudonymization, retention and disposal, and processor contracts	such lines on automated decisions, profiling and AI
age assurance	every such line	not read
cybersecurity	every line (their own framework)	not read

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