Law / Frameworks / Crosswalk / OWASP LLM Top 10 to NIST AI 200-2

The OWASP Top 10 for LLM Applications, mapped to the NIST TEVV-Athlon Framework for Evaluating AI Systems

5 of OWASP LLM Top 10's controls connect to 3 of NIST AI 200-2's through 79 laws in 37 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
OWASP Top 10 for LLM Applications, 2026 edition, August 2026, OWASP GenAI Security Project
To
NIST TEVV-Athlon Framework for Evaluating AI Systems, initial public draft, August 2026 (NIST AI 200-2 ipd), National Institute of Standards and Technology
See also
NIST AI 200-2 to OWASP LLM Top 10, 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--owasp-llm-top-10.csv · nist-ai-200-2--owasp-llm-top-10.json

OWASP LLM Top 10NIST AI 200-2LawsJurisdictionsWhere the laws stand
LLM01:2026Prompt Injection 2.2Define & Construct 3 2 2 in force, 1 not yet in force
The 3 laws behind LLM01:2026 and 2.2
4.3Composing a TEVV Toolbox 3 2 2 in force, 1 not yet in force
The 3 laws behind LLM01:2026 and 4.3
LLM02:2026Sensitive Information Disclosure 2.2Define & Construct 3 2 2 in force, 1 not yet in force
The 3 laws behind LLM02:2026 and 2.2
4.3Composing a TEVV Toolbox 3 2 2 in force, 1 not yet in force
The 3 laws behind LLM02:2026 and 4.3
LLM03:2026Excessive Agency 2.3Apply & Measure 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind LLM03:2026 and 2.3

and 68 more, every one in the free file.

4.3Composing a TEVV Toolbox 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind LLM03:2026 and 4.3

and 68 more, every one in the free file.

LLM04:2026Supply Chain 2.2Define & Construct 3 2 2 in force, 1 not yet in force
The 3 laws behind LLM04:2026 and 2.2
4.3Composing a TEVV Toolbox 3 2 2 in force, 1 not yet in force
The 3 laws behind LLM04:2026 and 4.3
LLM05:2026Data and Model Poisoning 2.2Define & Construct 3 2 2 in force, 1 not yet in force
The 3 laws behind LLM05:2026 and 2.2
4.3Composing a TEVV Toolbox 3 2 2 in force, 1 not yet in force
The 3 laws behind LLM05:2026 and 4.3
Not connected to the NIST AI 200-2: 5 of OWASP LLM Top 10's controls

No law we track reaches these

No duty in the laws we track reaches these controls.

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 either framework 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 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.

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

Sources and licenses

OWASP GenAI Security Project, OWASP Top 10 for LLM Applications 2026, licensed CC BY-SA 4.0. Excerpted: only the first paragraph of each entry's Description is reproduced, verbatim.