Law / Frameworks / Crosswalk / NIST AI 200-2 to NIST CSF 2.0

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

3 of NIST AI 200-2's steps connect to 2 of NIST CSF 2.0's through 10 laws in 4 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 Cybersecurity Framework, version 2.0, February 2024 (NIST CSWP 29), National Institute of Standards and Technology
See also
NIST CSF 2.0 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-csf.csv · nist-ai-200-2--nist-csf.json

NIST AI 200-2NIST CSF 2.0LawsJurisdictionsWhere the laws stand
2.2Define & Construct PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 2 1 1 in force, 1 not yet in force
The 2 laws behind 2.2 and PR.IR-03
2.3Apply & Measure PR.PS-04Log records are generated and made available for continuous monitoring 8 4 4 in force, 4 not yet in force
The 8 laws behind 2.3 and PR.PS-04
4.3Composing a TEVV Toolbox PR.PS-04Log records are generated and made available for continuous monitoring 8 4 4 in force, 4 not yet in force
The 8 laws behind 4.3 and PR.PS-04
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations 2 1 1 in force, 1 not yet in force
The 2 laws behind 4.3 and PR.IR-03
Not connected to the NIST CSF 2.0: 7 of NIST AI 200-2's steps

No NIST CSF 2.0 control on the same duties

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

  • 2.4 Synthesize & Interrogate, 13 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 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).

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 CSF 2.0
AIsuch lines on security, robustness, resilience, vulnerabilities and logs
scrapingnot read
news aggregationnot read

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