Law / Frameworks / Crosswalk / NIST AI RMF to ETSI EN 304 223

The NIST AI Risk Management Framework, mapped to the ETSI EN 304 223, Baseline Cyber Security Requirements for AI Models and Systems

28 of NIST AI RMF's controls connect to 19 of ETSI EN 304 223's through 435 laws in 165 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
ETSI EN 304 223, Baseline Cyber Security Requirements for AI Models and Systems, version 2.1.1, December 2025, European Telecommunications Standards Institute (ETSI)
See also
ETSI EN 304 223 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--etsi-en-304-223.csv · nist-ai-rmf--etsi-en-304-223.json

NIST AI RMFETSI EN 304 223LawsJurisdictionsWhere the laws stand
GOVERN 1.1Legal and regulatory requirements involving AI are understood, managed, and documented. 5.1.4-1Capability for human oversight designed in and maintained. 38 20 28 in force, 9 not yet in force, 1 proposed
The 38 laws behind GOVERN 1.1 and 5.1.4-1

and 28 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 38 20 28 in force, 9 not yet in force, 1 proposed
The 38 laws behind GOVERN 1.1 and 5.2.1-1

and 28 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 38 20 28 in force, 9 not yet in force, 1 proposed
The 38 laws behind GOVERN 1.1 and 5.2.4-1

and 28 more, every one in the free file.

5.4.2-1Operators log system and user actions. 38 20 28 in force, 9 not yet in force, 1 proposed
The 38 laws behind GOVERN 1.1 and 5.4.2-1

and 28 more, every one in the free file.

5.2.2-5AI-specific incident management and recovery plans that are created, tested and maintained. 15 11 12 in force, 2 not yet in force, 1 proposed
The 15 laws behind GOVERN 1.1 and 5.2.2-5

and 5 more, every one in the free file.

GOVERN 1.4The risk management process and its outcomes are established through transparent... 5.1.4-1Capability for human oversight designed in and maintained. 17 12 11 in force, 6 not yet in force
The 17 laws behind GOVERN 1.4 and 5.1.4-1

and 7 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 17 12 11 in force, 6 not yet in force
The 17 laws behind GOVERN 1.4 and 5.2.1-1

and 7 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 17 12 11 in force, 6 not yet in force
The 17 laws behind GOVERN 1.4 and 5.2.4-1

and 7 more, every one in the free file.

5.4.2-1Operators log system and user actions. 17 12 11 in force, 6 not yet in force
The 17 laws behind GOVERN 1.4 and 5.4.2-1

and 7 more, every one in the free file.

GOVERN 1.6Mechanisms are in place to inventory AI systems and are resourced according to... 5.1.4-1Capability for human oversight designed in and maintained. 7 6 6 in force, 1 not yet in force
The 7 laws behind GOVERN 1.6 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 7 6 6 in force, 1 not yet in force
The 7 laws behind GOVERN 1.6 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 7 6 6 in force, 1 not yet in force
The 7 laws behind GOVERN 1.6 and 5.2.4-1
5.4.2-1Operators log system and user actions. 7 6 6 in force, 1 not yet in force
The 7 laws behind GOVERN 1.6 and 5.4.2-1
GOVERN 2.1Roles and responsibilities and lines of communication related to mapping, measuring,... 5.1.4-1Capability for human oversight designed in and maintained. 7 6 7 in force
The 7 laws behind GOVERN 2.1 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 7 6 7 in force
The 7 laws behind GOVERN 2.1 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 7 6 7 in force
The 7 laws behind GOVERN 2.1 and 5.2.4-1
5.4.2-1Operators log system and user actions. 7 6 7 in force
The 7 laws behind GOVERN 2.1 and 5.4.2-1
GOVERN 2.3Executive leadership of the organization takes responsibility for decisions about... 5.1.4-1Capability for human oversight designed in and maintained. 4 4 4 in force
The 4 laws behind GOVERN 2.3 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 4 4 4 in force
The 4 laws behind GOVERN 2.3 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 4 4 4 in force
The 4 laws behind GOVERN 2.3 and 5.2.4-1
5.4.2-1Operators log system and user actions. 4 4 4 in force
The 4 laws behind GOVERN 2.3 and 5.4.2-1
GOVERN 4.2Organizational teams document the risks and potential impacts of the AI technology... 5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 8 6 4 in force, 3 not yet in force, 1 proposed
The 8 laws behind GOVERN 4.2 and 5.1.3-2
5.2.2-5AI-specific incident management and recovery plans that are created, tested and maintained. 8 6 5 in force, 3 not yet in force
The 8 laws behind GOVERN 4.2 and 5.2.2-5
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 8 6 4 in force, 3 not yet in force, 1 proposed
The 8 laws behind GOVERN 4.2 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 8 6 4 in force, 3 not yet in force, 1 proposed
The 8 laws behind GOVERN 4.2 and 5.3.1-2.1
GOVERN 4.3Organizational practices are in place to enable AI testing, identification of... 5.2.2-5AI-specific incident management and recovery plans that are created, tested and maintained. 2 2 1 in force, 1 not yet in force
The 2 laws behind GOVERN 4.3 and 5.2.2-5
GOVERN 6.1Policies and procedures are in place that address AI risks associated with third-party... 5.1.2-7Due diligence on external providers, including whether they follow this standard. 2 2 1 in force, 1 not yet in force
The 2 laws behind GOVERN 6.1 and 5.1.2-7
5.2.2-6Contracts with cloud providers that back the requirements above. 2 2 1 in force, 1 not yet in force
The 2 laws behind GOVERN 6.1 and 5.2.2-6
MAP 1.6System requirements (e.g., “the system shall respect the privacy of its users”) are... 5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 3 3 2 in force, 1 not yet in force
The 3 laws behind MAP 1.6 and 5.1.3-2
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 3 3 2 in force, 1 not yet in force
The 3 laws behind MAP 1.6 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 3 3 2 in force, 1 not yet in force
The 3 laws behind MAP 1.6 and 5.3.1-2.1
MAP 2.2Information about the AI system’s knowledge limits and how system output may be... 5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 4 3 1 in force, 3 not yet in force
The 4 laws behind MAP 2.2 and 5.1.3-2
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 4 3 1 in force, 3 not yet in force
The 4 laws behind MAP 2.2 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 4 3 1 in force, 3 not yet in force
The 4 laws behind MAP 2.2 and 5.3.1-2.1
MAP 2.3Scientific integrity and TEVV considerations are identified and documented, including... 5.1.4-1Capability for human oversight designed in and maintained. 12 9 8 in force, 4 not yet in force
The 12 laws behind MAP 2.3 and 5.1.4-1

and 2 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 12 9 8 in force, 4 not yet in force
The 12 laws behind MAP 2.3 and 5.2.1-1

and 2 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 12 9 8 in force, 4 not yet in force
The 12 laws behind MAP 2.3 and 5.2.4-1

and 2 more, every one in the free file.

5.4.2-1Operators log system and user actions. 12 9 8 in force, 4 not yet in force
The 12 laws behind MAP 2.3 and 5.4.2-1

and 2 more, every one in the free file.

MAP 3.3Targeted application scope is specified and documented based on the system’s... 5.1.2-1Business need and security risks written down and assessed before deciding to build an... 143 86 124 in force, 15 not yet in force, 1 blocked by a court, 3 proposed
The 143 laws behind MAP 3.3 and 5.1.2-1

and 133 more, every one in the free file.

5.1.4-5End-users told which uses of the system are prohibited. 143 86 124 in force, 15 not yet in force, 1 blocked by a court, 3 proposed
The 143 laws behind MAP 3.3 and 5.1.4-5

and 133 more, every one in the free file.

5.1.4-1Capability for human oversight designed in and maintained. 3 2 3 in force
The 3 laws behind MAP 3.3 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 3 2 3 in force
The 3 laws behind MAP 3.3 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 3 2 3 in force
The 3 laws behind MAP 3.3 and 5.2.4-1
5.4.2-1Operators log system and user actions. 3 2 3 in force
The 3 laws behind MAP 3.3 and 5.4.2-1
5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 2 2 1 in force, 1 not yet in force
The 2 laws behind MAP 3.3 and 5.1.3-2
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 2 2 1 in force, 1 not yet in force
The 2 laws behind MAP 3.3 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 2 2 1 in force, 1 not yet in force
The 2 laws behind MAP 3.3 and 5.3.1-2.1
5.1.4-3Where oversight is a risk control, the technical measures behind it are built,... 2 1 2 in force
The 2 laws behind MAP 3.3 and 5.1.4-3
MAP 3.5Processes for human oversight are defined, assessed, and documented in accordance with... 5.1.4-1Capability for human oversight designed in and maintained. 25 18 17 in force, 8 not yet in force
The 25 laws behind MAP 3.5 and 5.1.4-1

and 15 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 25 18 17 in force, 8 not yet in force
The 25 laws behind MAP 3.5 and 5.2.1-1

and 15 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 25 18 17 in force, 8 not yet in force
The 25 laws behind MAP 3.5 and 5.2.4-1

and 15 more, every one in the free file.

5.4.2-1Operators log system and user actions. 25 18 17 in force, 8 not yet in force
The 25 laws behind MAP 3.5 and 5.4.2-1

and 15 more, every one in the free file.

5.1.4-3Where oversight is a risk control, the technical measures behind it are built,... 4 2 2 in force, 2 not yet in force
The 4 laws behind MAP 3.5 and 5.1.4-3
5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 2 2 2 in force
The 2 laws behind MAP 3.5 and 5.1.3-2
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 2 2 2 in force
The 2 laws behind MAP 3.5 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 2 2 2 in force
The 2 laws behind MAP 3.5 and 5.3.1-2.1
MAP 4.1Approaches for mapping AI technology and legal risks of its components – including the... 5.1.2-6Access the AI system gets to other systems and data sources is minimal and risk assessed. 145 107 142 in force, 3 not yet in force
The 145 laws behind MAP 4.1 and 5.1.2-6

and 135 more, every one in the free file.

5.2.4-2.1Minimum record for training data: its source, such as a page URL, and when it was collected. 18 16 17 in force, 1 not yet in force
The 18 laws behind MAP 4.1 and 5.2.4-2.1

and 8 more, every one in the free file.

MAP 5.1Likelihood and magnitude of each identified impact (both potentially beneficial and... 5.1.2-1Business need and security risks written down and assessed before deciding to build an... 9 8 3 in force, 1 not yet in force, 5 proposed
The 9 laws behind MAP 5.1 and 5.1.2-1
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 9 8 3 in force, 1 not yet in force, 5 proposed
The 9 laws behind MAP 5.1 and 5.1.3-1
5.1.4-1Capability for human oversight designed in and maintained. 3 3 3 in force
The 3 laws behind MAP 5.1 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 3 3 3 in force
The 3 laws behind MAP 5.1 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 3 3 3 in force
The 3 laws behind MAP 5.1 and 5.2.4-1
5.4.2-1Operators log system and user actions. 3 3 3 in force
The 3 laws behind MAP 5.1 and 5.4.2-1
MEASURE 2.4The functionality and behavior of the AI system and its components – as identified in... 5.1.4-1Capability for human oversight designed in and maintained. 22 11 12 in force, 10 not yet in force
The 22 laws behind MEASURE 2.4 and 5.1.4-1

and 12 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 22 11 12 in force, 10 not yet in force
The 22 laws behind MEASURE 2.4 and 5.2.1-1

and 12 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 22 11 12 in force, 10 not yet in force
The 22 laws behind MEASURE 2.4 and 5.2.4-1

and 12 more, every one in the free file.

5.4.2-1Operators log system and user actions. 22 11 12 in force, 10 not yet in force
The 22 laws behind MEASURE 2.4 and 5.4.2-1

and 12 more, every one in the free file.

MEASURE 2.5The AI system to be deployed is demonstrated to be valid and reliable. Limitations of... 5.1.2-2System built to hold up against adversarial attacks, unexpected inputs and failures. 2 1 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.5 and 5.1.2-2
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 2 1 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.5 and 5.1.3-1
5.2.1-4Sensitive data such as training and test sets protected from unauthorised access. 2 1 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.5 and 5.2.1-4
5.4.2-2Logs analysed for anomalies, breaches and effects of drift or poisoning. 2 1 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.5 and 5.4.2-2
MEASURE 2.6The AI system is evaluated regularly for safety risks – as identified in the MAP... 5.1.2-2System built to hold up against adversarial attacks, unexpected inputs and failures. 3 2 2 in force, 1 not yet in force
The 3 laws behind MEASURE 2.6 and 5.1.2-2
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 3 2 2 in force, 1 not yet in force
The 3 laws behind MEASURE 2.6 and 5.1.3-1
5.2.1-4Sensitive data such as training and test sets protected from unauthorised access. 3 2 2 in force, 1 not yet in force
The 3 laws behind MEASURE 2.6 and 5.2.1-4
5.4.2-2Logs analysed for anomalies, breaches and effects of drift or poisoning. 3 2 2 in force, 1 not yet in force
The 3 laws behind MEASURE 2.6 and 5.4.2-2
5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 2 2 1 not yet in force, 1 proposed
The 2 laws behind MEASURE 2.6 and 5.1.3-2
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 2 2 1 not yet in force, 1 proposed
The 2 laws behind MEASURE 2.6 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 2 2 1 not yet in force, 1 proposed
The 2 laws behind MEASURE 2.6 and 5.3.1-2.1
MEASURE 2.7AI system security and resilience – as identified in the MAP function – are evaluated... 5.1.4-1Capability for human oversight designed in and maintained. 2 2 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.7 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 2 2 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.7 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 2 2 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.7 and 5.2.4-1
5.4.2-1Operators log system and user actions. 2 2 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.7 and 5.4.2-1
5.1.2-2System built to hold up against adversarial attacks, unexpected inputs and failures. 2 1 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.7 and 5.1.2-2
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 2 1 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.7 and 5.1.3-1
5.2.1-4Sensitive data such as training and test sets protected from unauthorised access. 2 1 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.7 and 5.2.1-4
5.4.2-2Logs analysed for anomalies, breaches and effects of drift or poisoning. 2 1 1 in force, 1 not yet in force
The 2 laws behind MEASURE 2.7 and 5.4.2-2
MEASURE 2.8Risks associated with transparency and accountability – as identified in the MAP... 5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 64 43 40 in force, 12 not yet in force, 12 proposed
The 64 laws behind MEASURE 2.8 and 5.1.3-2

and 54 more, every one in the free file.

5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 64 43 40 in force, 12 not yet in force, 12 proposed
The 64 laws behind MEASURE 2.8 and 5.3.1-1

and 54 more, every one in the free file.

5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 64 43 40 in force, 12 not yet in force, 12 proposed
The 64 laws behind MEASURE 2.8 and 5.3.1-2.1

and 54 more, every one in the free file.

MEASURE 2.9The AI model is explained, validated, and documented, and AI system output is... 5.1.4-1Capability for human oversight designed in and maintained. 4 4 4 in force
The 4 laws behind MEASURE 2.9 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 4 4 4 in force
The 4 laws behind MEASURE 2.9 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 4 4 4 in force
The 4 laws behind MEASURE 2.9 and 5.2.4-1
5.4.2-1Operators log system and user actions. 4 4 4 in force
The 4 laws behind MEASURE 2.9 and 5.4.2-1
MEASURE 2.10Privacy risk of the AI system – as identified in the MAP function – is examined and documented. 5.1.2-1Business need and security risks written down and assessed before deciding to build an... 4 4 3 in force, 1 not yet in force
The 4 laws behind MEASURE 2.10 and 5.1.2-1
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 4 4 3 in force, 1 not yet in force
The 4 laws behind MEASURE 2.10 and 5.1.3-1
MEASURE 2.11Fairness and bias – as identified in the MAP function – are evaluated and results are... 5.1.4-1Capability for human oversight designed in and maintained. 6 5 4 in force, 2 not yet in force
The 6 laws behind MEASURE 2.11 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 6 5 4 in force, 2 not yet in force
The 6 laws behind MEASURE 2.11 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 6 5 4 in force, 2 not yet in force
The 6 laws behind MEASURE 2.11 and 5.2.4-1
5.4.2-1Operators log system and user actions. 6 5 4 in force, 2 not yet in force
The 6 laws behind MEASURE 2.11 and 5.4.2-1
MEASURE 3.3Feedback processes for end users and impacted communities to report problems and... 5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 9 9 2 in force, 1 not yet in force, 6 proposed
The 9 laws behind MEASURE 3.3 and 5.1.3-2
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 9 9 2 in force, 1 not yet in force, 6 proposed
The 9 laws behind MEASURE 3.3 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 9 9 2 in force, 1 not yet in force, 6 proposed
The 9 laws behind MEASURE 3.3 and 5.3.1-2.1
5.1.4-1Capability for human oversight designed in and maintained. 2 2 2 in force
The 2 laws behind MEASURE 3.3 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 2 2 2 in force
The 2 laws behind MEASURE 3.3 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 2 2 2 in force
The 2 laws behind MEASURE 3.3 and 5.2.4-1
5.4.2-1Operators log system and user actions. 2 2 2 in force
The 2 laws behind MEASURE 3.3 and 5.4.2-1
MANAGE 1.3Responses to the AI risks deemed high priority, as identified by the MAP function, are... 5.1.2-1Business need and security risks written down and assessed before deciding to build an... 6 6 1 in force, 5 proposed
The 6 laws behind MANAGE 1.3 and 5.1.2-1
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 5 5 5 proposed
The 5 laws behind MANAGE 1.3 and 5.1.3-1
MANAGE 2.4Mechanisms are in place and applied, and responsibilities are assigned and understood,... 5.1.4-1Capability for human oversight designed in and maintained. 4 3 4 in force
The 4 laws behind MANAGE 2.4 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 4 3 4 in force
The 4 laws behind MANAGE 2.4 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 4 3 4 in force
The 4 laws behind MANAGE 2.4 and 5.2.4-1
5.4.2-1Operators log system and user actions. 4 3 4 in force
The 4 laws behind MANAGE 2.4 and 5.4.2-1
MANAGE 4.1Post-deployment AI system monitoring plans are implemented, including mechanisms for... 5.2.2-5AI-specific incident management and recovery plans that are created, tested and maintained. 6 6 6 in force
The 6 laws behind MANAGE 4.1 and 5.2.2-5
MANAGE 4.3Incidents and errors are communicated to relevant AI actors, including affected... 5.2.2-5AI-specific incident management and recovery plans that are created, tested and maintained. 9 7 5 in force, 3 not yet in force, 1 proposed
The 9 laws behind MANAGE 4.3 and 5.2.2-5
Not connected to the ETSI EN 304 223: 44 of NIST AI RMF's controls

Short of 2 laws

The same duties reach these and a ETSI EN 304 223 provision, in fewer than 2 of the laws we track.

No ETSI EN 304 223 provision on the same duties

Laws reach these, but no duty that reaches one of them also reaches a ETSI EN 304 223 provision.

  • GOVERN 1.2 The characteristics of trustworthy AI are integrated into organizational policies,..., 6 laws
  • GOVERN 1.7 Processes and procedures are in place for decommissioning and phasing out AI systems..., 1 law
  • GOVERN 2.2 The organization’s personnel and partners receive AI risk management training to..., 3 laws
  • GOVERN 3.2 Policies and procedures are in place to define and differentiate roles and..., 5 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.5 Organizational risk tolerances are determined and documented., 1 law
  • MEASURE 1.2 Appropriateness of AI metrics and effectiveness of existing controls are regularly..., 1 law
  • MEASURE 1.3 Internal experts who did not serve as front-line developers for the system and/or..., 10 laws
  • MEASURE 2.2 Evaluations involving human subjects meet applicable requirements (including human..., 1 law
  • MEASURE 2.3 AI system performance or assurance criteria are measured qualitatively or..., 6 laws
  • MEASURE 3.1 Approaches, personnel, and documentation are in place to regularly identify and track..., 2 laws
  • MANAGE 2.1 Resources required to manage AI risks are taken into account – along with viable..., 1 law
  • MANAGE 3.1 AI risks and benefits from third-party resources are regularly monitored, and risk..., 3 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...

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 ETSI EN 304 223 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

Identifiers refer to ETSI EN 304 223 V2.1.1 (2025-12), © ETSI 2025, all rights reserved. ETSI owns the standard; no ETSI text (titles or sentences) is reproduced here. The standard is free to download from ETSI.