Law / Frameworks / Crosswalk / NIST AI 200-2 to NIST Privacy Framework

The NIST TEVV-Athlon Framework for Evaluating AI Systems, mapped to the NIST Privacy Framework

2 of NIST AI 200-2's steps connect to 7 of NIST Privacy Framework's through 15 laws in 10 jurisdictions. Two steps 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 TEVV-Athlon Framework for Evaluating AI Systems, initial public draft, August 2026 (NIST AI 200-2 ipd), 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 200-2, the other way · every pair in the crosswalk · law library as of

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

NIST AI 200-2NIST Privacy FrameworkLawsJurisdictionsWhere the laws stand
2.3Apply & Measure CT.PO-P1Policies, processes, and procedures for authorizing data processing (e.g.,... 5 4 4 in force, 1 not yet in force
The 5 laws behind 2.3 and CT.PO-P1
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 2.3 and ID.RA-P2
GV.PO-P5Legal, regulatory, and contractual requirements regarding privacy are understood and managed. 3 3 2 in force, 1 not yet in force
The 3 laws behind 2.3 and GV.PO-P5
CT.DM-P10Stakeholder privacy preferences are included in algorithmic design objectives and... 3 3 2 in force, 1 not yet in force
The 3 laws behind 2.3 and CT.DM-P10
ID.IM-P1Systems/products/services that process data are inventoried. 3 2 2 in force, 1 not yet in force
The 3 laws behind 2.3 and ID.IM-P1
CM.AW-P1Mechanisms (e.g., notices, internal or public reports) for communicating data... 2 2 2 in force
The 2 laws behind 2.3 and CM.AW-P1
CT.DM-P8Audit/log records are determined, documented, implemented, and reviewed in accordance... 2 1 2 not yet in force
The 2 laws behind 2.3 and CT.DM-P8
4.3Composing a TEVV Toolbox CT.PO-P1Policies, processes, and procedures for authorizing data processing (e.g.,... 5 4 4 in force, 1 not yet in force
The 5 laws behind 4.3 and CT.PO-P1
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 4.3 and ID.RA-P2
GV.PO-P5Legal, regulatory, and contractual requirements regarding privacy are understood and managed. 3 3 2 in force, 1 not yet in force
The 3 laws behind 4.3 and GV.PO-P5
CT.DM-P10Stakeholder privacy preferences are included in algorithmic design objectives and... 3 3 2 in force, 1 not yet in force
The 3 laws behind 4.3 and CT.DM-P10
ID.IM-P1Systems/products/services that process data are inventoried. 3 2 2 in force, 1 not yet in force
The 3 laws behind 4.3 and ID.IM-P1
CM.AW-P1Mechanisms (e.g., notices, internal or public reports) for communicating data... 2 2 2 in force
The 2 laws behind 4.3 and CM.AW-P1
CT.DM-P8Audit/log records are determined, documented, implemented, and reviewed in accordance... 2 1 2 not yet in force
The 2 laws behind 4.3 and CT.DM-P8
Not connected to the NIST Privacy Framework: 8 of NIST AI 200-2's steps

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.

  • 2.2 Define & Construct, 3 laws

No law we track reaches these

No duty in the laws we track reaches these steps.

  • 2.1 Articulate & Organize
  • 4.1 Gathering Appropriate Expertise
  • 4.2 Checking Basic TEVV-Athlon Requirements, Resources, and Materials
  • 4.4 Applying Best Practices for Scientific Measurement
  • 4.5 Validating Measurement
  • 4.6 Beware of Goodhart’s Law

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

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 NIST AI 200-2 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 steps 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 Privacy Framework
AIsuch lines on personal data and privacy, biometrics, likeness and identity, profiling, surveillance and consent
scrapingsuch lines on interception, monitoring, personal data and privacy
news aggregationnot read

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