Law / Frameworks / Crosswalk / NIST AI RMF to NIST Privacy Framework

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

15 of NIST AI RMF's controls connect to 12 of NIST Privacy Framework's through 177 laws in 117 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 AI Risk Management Framework, version 1.0, January 2023 (NIST AI 100-1), National Institute of Standards and Technology
To
NIST Privacy Framework, version 1.0, January 2020, National Institute of Standards and Technology
See also
NIST Privacy Framework to NIST AI RMF, the other way · every pair in the crosswalk · law library as of

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

NIST AI RMFNIST Privacy FrameworkLawsJurisdictionsWhere the laws stand
GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. GV.PO-P5Legal, regulatory, and contractual requirements regarding privacy are understood and managed. 4 3 3 in force, 1 not yet in force
The 4 laws behind GOVERN 1.1 and GV.PO-P5
CT.PO-P1Policies, processes, and procedures for authorizing data processing (e.g.,... 3 2 2 in force, 1 not yet in force
The 3 laws behind GOVERN 1.1 and CT.PO-P1
GOVERN 1.6Mechanisms are in place to inventory AI systems and are resourced according to... ID.IM-P1Systems/products/services that process data are inventoried. 3 2 2 in force, 1 not yet in force
The 3 laws behind GOVERN 1.6 and ID.IM-P1
MAP 1.6System requirements (e.g., “the system shall respect the privacy of its users”) are... CT.PO-P1Policies, processes, and procedures for authorizing data processing (e.g.,... 6 5 5 in force, 1 not yet in force
The 6 laws behind MAP 1.6 and CT.PO-P1
CT.PO-P3Policies, processes, and procedures for enabling individuals’ data processing... 4 4 1 in force, 3 not yet in force
The 4 laws behind MAP 1.6 and CT.PO-P3
CM.AW-P1Mechanisms (e.g., notices, internal or public reports) for communicating data... 4 3 4 in force
The 4 laws behind MAP 1.6 and CM.AW-P1
MAP 2.3Scientific integrity and TEVV considerations are identified and documented, including... ID.RA-P2Data analytic inputs and outputs are identified and evaluated for bias. 3 3 2 in force, 1 not yet in force
The 3 laws behind MAP 2.3 and ID.RA-P2
MAP 3.3Targeted application scope is specified and documented based on the system’s... CT.PO-P1Policies, processes, and procedures for authorizing data processing (e.g.,... 53 38 45 in force, 6 not yet in force, 2 proposed
The 53 laws behind MAP 3.3 and CT.PO-P1

and 43 more, every one in the free file.

MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... CT.DM-P10Stakeholder privacy preferences are included in algorithmic design objectives and... 54 52 46 in force, 5 not yet in force, 3 proposed
The 54 laws behind MAP 3.5 and CT.DM-P10

and 44 more, every one in the free file.

CT.PO-P1Policies, processes, and procedures for authorizing data processing (e.g.,... 8 7 7 in force, 1 proposed
The 8 laws behind MAP 3.5 and CT.PO-P1
CT.PO-P3Policies, processes, and procedures for enabling individuals’ data processing... 3 3 3 in force
The 3 laws behind MAP 3.5 and CT.PO-P3
CM.AW-P1Mechanisms (e.g., notices, internal or public reports) for communicating data... 2 2 2 in force
The 2 laws behind MAP 3.5 and CM.AW-P1
MAP 4.1Approaches for mapping AI technology and legal risks of its components – including the... CT.PO-P1Policies, processes, and procedures for authorizing data processing (e.g.,... 29 27 28 in force, 1 not yet in force
The 29 laws behind MAP 4.1 and CT.PO-P1

and 19 more, every one in the free file.

MAP 5.1Likelihood and magnitude of each identified impact (both potentially beneficial and... ID.RA-P4Problematic data actions, likelihoods, and impacts are used to determine and prioritize risk. 3 3 3 in force
The 3 laws behind MAP 5.1 and ID.RA-P4
MEASURE 2.4The functionality and behavior of the AI system and its components – as identified in... CT.DM-P8Audit/log records are determined, documented, implemented, and reviewed in accordance... 2 1 2 not yet in force
The 2 laws behind MEASURE 2.4 and CT.DM-P8
MEASURE 2.8Risks associated with transparency and accountability – as identified in the MAP... CM.AW-P1Mechanisms (e.g., notices, internal or public reports) for communicating data... 8 5 4 in force, 4 not yet in force
The 8 laws behind MEASURE 2.8 and CM.AW-P1
MEASURE 2.9The AI model is explained, validated, and documented, and AI system output is... CM.AW-P1Mechanisms (e.g., notices, internal or public reports) for communicating data... 10 8 5 in force, 4 not yet in force, 1 proposed
The 10 laws behind MEASURE 2.9 and CM.AW-P1
CT.DM-P10Stakeholder privacy preferences are included in algorithmic design objectives and... 5 5 4 in force, 1 not yet in force
The 5 laws behind MEASURE 2.9 and CT.DM-P10
CM.AW-P3System/product/service design enables data processing visibility. 5 5 5 in force
The 5 laws behind MEASURE 2.9 and CM.AW-P3
CT.PO-P3Policies, processes, and procedures for enabling individuals’ data processing... 2 2 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.9 and CT.PO-P3
MEASURE 2.10Privacy risk of the AI system – as identified in the MAP function – is examined and documented. ID.RA-P4Problematic data actions, likelihoods, and impacts are used to determine and prioritize risk. 2 2 2 in force
The 2 laws behind MEASURE 2.10 and ID.RA-P4
CT.PO-P1Policies, processes, and procedures for authorizing data processing (e.g.,... 2 2 2 in force
The 2 laws behind MEASURE 2.10 and CT.PO-P1
MEASURE 2.11Fairness and bias – as identified in the MAP function – are evaluated and results are... ID.RA-P2Data analytic inputs and outputs are identified and evaluated for bias. 4 4 2 in force, 2 not yet in force
The 4 laws behind MEASURE 2.11 and ID.RA-P2
MEASURE 3.3Feedback processes for end users and impacted communities to report problems and... CT.DM-P10Stakeholder privacy preferences are included in algorithmic design objectives and... 16 16 15 in force, 1 not yet in force
The 16 laws behind MEASURE 3.3 and CT.DM-P10

and 6 more, every one in the free file.

CT.PO-P3Policies, processes, and procedures for enabling individuals’ data processing... 9 9 7 in force, 1 not yet in force, 1 proposed
The 9 laws behind MEASURE 3.3 and CT.PO-P3
CM.AW-P1Mechanisms (e.g., notices, internal or public reports) for communicating data... 5 5 1 in force, 4 not yet in force
The 5 laws behind MEASURE 3.3 and CM.AW-P1
CM.AW-P8Individuals are provided with mitigation mechanisms (e.g., credit monitoring, consent... 2 2 2 not yet in force
The 2 laws behind MEASURE 3.3 and CM.AW-P8
MANAGE 2.4Mechanisms are in place and applied, and responsibilities are assigned and understood,... CT.DM-P5Data are destroyed according to policy. 3 2 2 in force, 1 not yet in force
The 3 laws behind MANAGE 2.4 and CT.DM-P5
Not connected to the NIST Privacy Framework: 57 of NIST AI RMF's controls

Short of 2 laws

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

No NIST Privacy Framework control on the same duties

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

  • GOVERN 1.3 Processes, procedures, and practices are in place to determine the needed level of..., 6 laws
  • GOVERN 1.5 Ongoing monitoring and periodic review of the risk management process and its outcomes..., 7 laws
  • GOVERN 1.7 Processes and procedures are in place for decommissioning and phasing out AI systems..., 1 law
  • GOVERN 2.1 Roles and responsibilities and lines of communication related to mapping, measuring,..., 9 laws
  • GOVERN 2.2 The organization’s personnel and partners receive AI risk management training to..., 3 laws
  • GOVERN 2.3 Executive leadership of the organization takes responsibility for decisions about..., 9 laws
  • GOVERN 4.1 Organizational policies and practices are in place to foster a critical thinking and..., 3 laws
  • GOVERN 4.2 Organizational teams document the risks and potential impacts of the AI technology..., 19 laws
  • GOVERN 4.3 Organizational practices are in place to enable AI testing, identification of..., 3 laws
  • GOVERN 5.1 Organizational policies and practices are in place to collect, consider, prioritize,..., 1 law
  • GOVERN 6.2 Contingency processes are in place to handle failures or incidents in third-party data..., 1 law
  • MAP 1.1 Intended purposes, potentially beneficial uses, context-specific laws, norms and..., 3 laws
  • MAP 1.5 Organizational risk tolerances are determined and documented., 1 law
  • MAP 2.2 Information about the AI system’s knowledge limits and how system output may be..., 12 laws
  • MAP 3.4 Processes for operator and practitioner proficiency with AI system performance and..., 3 laws
  • MEASURE 1.3 Internal experts who did not serve as front-line developers for the system and/or..., 10 laws
  • MEASURE 2.1 Test sets, metrics, and details about the tools used during TEVV are documented., 1 law
  • MEASURE 2.3 AI system performance or assurance criteria are measured qualitatively or..., 6 laws
  • MEASURE 2.5 The AI system to be deployed is demonstrated to be valid and reliable. Limitations of..., 7 laws
  • MEASURE 2.6 The AI system is evaluated regularly for safety risks – as identified in the MAP..., 23 laws
  • MANAGE 1.1 A determination is made as to whether the AI system achieves its intended purposes and..., 6 laws
  • MANAGE 2.1 Resources required to manage AI risks are taken into account – along with viable..., 1 law
  • MANAGE 2.3 Procedures are followed to respond to and recover from a previously unknown risk when..., 1 law
  • MANAGE 3.1 AI risks and benefits from third-party resources are regularly monitored, and risk..., 3 laws
  • MANAGE 4.3 Incidents and errors are communicated to relevant AI actors, including affected..., 17 laws

No law we track reaches these

No duty in the laws we track reaches these controls.

  • GOVERN 3.1 Decision-making related to mapping, measuring, and managing AI risks throughout the...
  • GOVERN 5.2 Mechanisms are established to enable the team that developed or deployed AI systems to...
  • MAP 1.2 Interdisciplinary AI actors, competencies, skills, and capacities for establishing...
  • MAP 1.3 The organization’s mission and relevant goals for AI technology are understood and documented.
  • MAP 1.4 The business value or context of business use has been clearly defined or – in the...
  • MAP 2.1 The specific tasks and methods used to implement the tasks that the AI system will...
  • MAP 3.1 Potential benefits of intended AI system functionality and performance are examined...
  • MAP 3.2 Potential costs, including non-monetary costs, which result from expected or realized...
  • MAP 4.2 Internal risk controls for components of the AI system, including third-party AI...
  • MAP 5.2 Practices and personnel for supporting regular engagement with relevant AI actors and...
  • MEASURE 1.1 Approaches and metrics for measurement of AI risks enumerated during the MAP function...
  • MEASURE 2.12 Environmental impact and sustainability of AI model training and management activities...
  • MEASURE 2.13 Effectiveness of the employed TEVV metrics and processes in the MEASURE function are...
  • MEASURE 3.2 Risk tracking approaches are considered for settings where AI risks are difficult to...
  • MEASURE 4.1 Measurement approaches for identifying AI risks are connected to deployment context(s)...
  • MEASURE 4.2 Measurement results regarding AI system trustworthiness in deployment context(s) and...
  • MEASURE 4.3 Measurable performance improvements or declines based on consultations with relevant...
  • MANAGE 1.2 Treatment of documented AI risks is prioritized based on impact, likelihood, and...
  • MANAGE 1.4 Negative residual risks (defined as the sum of all unmitigated risks) to both...
  • MANAGE 2.2 Mechanisms are in place and applied to sustain the value of deployed AI systems.
  • MANAGE 3.2 Pre-trained models which are used for development are monitored as part of AI system...
  • MANAGE 4.2 Measurable activities for continual improvements are integrated into AI system updates...

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

Lines of the communications, 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 onRead against the NIST AI RMFRead against the NIST Privacy Framework
AIevery line (their own framework)such lines on personal data and privacy, biometrics, likeness and identity, profiling, surveillance and consent
scrapingevery line (their own framework)such lines on interception, monitoring, personal data and privacy
news aggregationevery line (their own framework)not read
privacysuch lines on automated decisions, profiling and AIevery line (their own framework)
communicationsnot readevery line (their own framework)
age assurancenot readevery line (their own framework)
cybersecuritynot readevery such line

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