Law / Frameworks / Crosswalk / MIT mitigations to ETSI EN 304 223

The MIT AI Risk Mitigation Taxonomy, mapped to the ETSI EN 304 223, Baseline Cyber Security Requirements for AI Models and Systems

18 of MIT mitigations' controls connect to 19 of ETSI EN 304 223's through 436 laws in 166 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
MIT AI Risk Mitigation Taxonomy, preliminary taxonomy, July 2025, MIT AI Risk Initiative
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 MIT mitigations, the other way · every pair in the crosswalk · law library as of

Download this mapping, with every law behind each connection: mit-ai-risk-mitigations--etsi-en-304-223.csv · mit-ai-risk-mitigations--etsi-en-304-223.json

MIT mitigationsETSI EN 304 223LawsJurisdictionsWhere the laws stand
1.1Board Structure & Oversight 5.1.4-1Capability for human oversight designed in and maintained. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 1.1 and 5.1.4-1

and 68 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 1.1 and 5.2.1-1

and 68 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 1.1 and 5.2.4-1

and 68 more, every one in the free file.

5.4.2-1Operators log system and user actions. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 1.1 and 5.4.2-1

and 68 more, every one in the free file.

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

and 2 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 1.1 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 1.1 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 1.1 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 1.1 and 5.3.1-2.1
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 2 1 2 in force
The 2 laws behind 1.1 and 5.1.3-1
1.2Risk Management 5.1.4-1Capability for human oversight designed in and maintained. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 1.2 and 5.1.4-1

and 68 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 1.2 and 5.2.1-1

and 68 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 1.2 and 5.2.4-1

and 68 more, every one in the free file.

5.4.2-1Operators log system and user actions. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 1.2 and 5.4.2-1

and 68 more, every one in the free file.

5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 14 11 7 in force, 2 not yet in force, 5 proposed
The 14 laws behind 1.2 and 5.1.3-1

and 4 more, every one in the free file.

5.1.2-1Business need and security risks written down and assessed before deciding to build an... 13 11 6 in force, 2 not yet in force, 5 proposed
The 13 laws behind 1.2 and 5.1.2-1

and 3 more, every one in the free file.

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

and 2 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 1.2 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 1.2 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 1.2 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 1.2 and 5.3.1-2.1
1.5Safety Decision Frameworks 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 1.5 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 1.5 and 5.1.4-5

and 133 more, every one in the free file.

1.7Societal Impact Assessment 5.1.2-1Business need and security risks written down and assessed before deciding to build an... 13 11 6 in force, 2 not yet in force, 5 proposed
The 13 laws behind 1.7 and 5.1.2-1

and 3 more, every one in the free file.

5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 13 11 6 in force, 2 not yet in force, 5 proposed
The 13 laws behind 1.7 and 5.1.3-1

and 3 more, every one in the free file.

2.1Model & Infrastructure Security 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 2.1 and 5.1.2-6

and 135 more, every one in the free file.

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 2.1 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 2.1 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 2.1 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 2.1 and 5.4.2-2
5.2.4-2.1Minimum record for training data: its source, such as a page URL, and when it was collected. 2 2 2 in force
The 2 laws behind 2.1 and 5.2.4-2.1
2.3Model Safety Engineering 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 2.3 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 2.3 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 2.3 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 2.3 and 5.4.2-2
2.4Content Safety Controls 5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 23 19 14 in force, 5 not yet in force, 4 proposed
The 23 laws behind 2.4 and 5.1.3-2

and 13 more, every one in the free file.

5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 23 19 14 in force, 5 not yet in force, 4 proposed
The 23 laws behind 2.4 and 5.3.1-1

and 13 more, every one in the free file.

5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 23 19 14 in force, 5 not yet in force, 4 proposed
The 23 laws behind 2.4 and 5.3.1-2.1

and 13 more, every one in the free file.

3.1Testing & Auditing 5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 16 11 8 in force, 3 not yet in force, 5 proposed
The 16 laws behind 3.1 and 5.1.3-1

and 6 more, every one in the free file.

5.1.2-1Business need and security risks written down and assessed before deciding to build an... 13 11 6 in force, 2 not yet in force, 5 proposed
The 13 laws behind 3.1 and 5.1.2-1

and 3 more, every one in the free file.

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 3.1 and 5.1.2-2
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 3.1 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 3.1 and 5.4.2-2
5.1.4-1Capability for human oversight designed in and maintained. 2 1 2 in force
The 2 laws behind 3.1 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 2 1 2 in force
The 2 laws behind 3.1 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 2 1 2 in force
The 2 laws behind 3.1 and 5.2.4-1
5.4.2-1Operators log system and user actions. 2 1 2 in force
The 2 laws behind 3.1 and 5.4.2-1
3.2Data Governance 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 3.2 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 3.2 and 5.2.4-2.1

and 8 more, every one in the free file.

5.1.4-1Capability for human oversight designed in and maintained. 6 3 4 in force, 2 not yet in force
The 6 laws behind 3.2 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 6 3 4 in force, 2 not yet in force
The 6 laws behind 3.2 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 6 3 4 in force, 2 not yet in force
The 6 laws behind 3.2 and 5.2.4-1
5.4.2-1Operators log system and user actions. 6 3 4 in force, 2 not yet in force
The 6 laws behind 3.2 and 5.4.2-1
5.1.4-3Where oversight is a risk control, the technical measures behind it are built,... 5 3 3 in force, 2 not yet in force
The 5 laws behind 3.2 and 5.1.4-3
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 3.2 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 3.2 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 3.2 and 5.3.1-2.1
3.3Access Management 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 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 3.3 and 5.1.4-5

and 133 more, every one in the free file.

5.1.4-3Where oversight is a risk control, the technical measures behind it are built,... 5 3 3 in force, 2 not yet in force
The 5 laws behind 3.3 and 5.1.4-3
5.1.4-1Capability for human oversight designed in and maintained. 4 2 2 in force, 2 not yet in force
The 4 laws behind 3.3 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 4 2 2 in force, 2 not yet in force
The 4 laws behind 3.3 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 4 2 2 in force, 2 not yet in force
The 4 laws behind 3.3 and 5.2.4-1
5.4.2-1Operators log system and user actions. 4 2 2 in force, 2 not yet in force
The 4 laws behind 3.3 and 5.4.2-1
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 3.3 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 3.3 and 5.2.2-6
3.5Post-deployment Monitoring 5.1.4-1Capability for human oversight designed in and maintained. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 3.5 and 5.1.4-1

and 68 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 3.5 and 5.2.1-1

and 68 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 3.5 and 5.2.4-1

and 68 more, every one in the free file.

5.4.2-1Operators log system and user actions. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 3.5 and 5.4.2-1

and 68 more, every one in the free file.

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

and 2 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 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 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 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 3.5 and 5.3.1-2.1
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 2 1 2 in force
The 2 laws behind 3.5 and 5.1.3-1
3.6Incident Response & Recovery 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 3.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 3.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 3.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 3.6 and 5.4.2-2
4.1System Documentation 5.1.4-1Capability for human oversight designed in and maintained. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 4.1 and 5.1.4-1

and 68 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 4.1 and 5.2.1-1

and 68 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 4.1 and 5.2.4-1

and 68 more, every one in the free file.

5.4.2-1Operators log system and user actions. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind 4.1 and 5.4.2-1

and 68 more, every one in the free file.

5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 70 44 42 in force, 16 not yet in force, 12 proposed
The 70 laws behind 4.1 and 5.1.3-2

and 60 more, every one in the free file.

5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 70 44 42 in force, 16 not yet in force, 12 proposed
The 70 laws behind 4.1 and 5.3.1-1

and 60 more, every one in the free file.

5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 70 44 42 in force, 16 not yet in force, 12 proposed
The 70 laws behind 4.1 and 5.3.1-2.1

and 60 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 4.1 and 5.2.4-2.1

and 8 more, every one in the free file.

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

and 7 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 4.1 and 5.1.4-3
5.1.2-1Business need and security risks written down and assessed before deciding to build an... 2 2 1 in force, 1 not yet in force
The 2 laws behind 4.1 and 5.1.2-1
5.1.2-6Access the AI system gets to other systems and data sources is minimal and risk assessed. 2 2 2 in force
The 2 laws behind 4.1 and 5.1.2-6
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 2 1 2 in force
The 2 laws behind 4.1 and 5.1.3-1
4.2Risk Disclosure 5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 70 44 42 in force, 16 not yet in force, 12 proposed
The 70 laws behind 4.2 and 5.1.3-2

and 60 more, every one in the free file.

5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 70 44 42 in force, 16 not yet in force, 12 proposed
The 70 laws behind 4.2 and 5.3.1-1

and 60 more, every one in the free file.

5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 70 44 42 in force, 16 not yet in force, 12 proposed
The 70 laws behind 4.2 and 5.3.1-2.1

and 60 more, every one in the free file.

5.2.2-5AI-specific incident management and recovery plans that are created, tested and maintained. 26 16 18 in force, 7 not yet in force, 1 proposed
The 26 laws behind 4.2 and 5.2.2-5

and 16 more, every one in the free file.

5.1.4-1Capability for human oversight designed in and maintained. 15 11 11 in force, 3 not yet in force, 1 proposed
The 15 laws behind 4.2 and 5.1.4-1

and 5 more, every one in the free file.

5.2.1-1Full inventory of assets, including their dependencies and connections. 15 11 11 in force, 3 not yet in force, 1 proposed
The 15 laws behind 4.2 and 5.2.1-1

and 5 more, every one in the free file.

5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 15 11 11 in force, 3 not yet in force, 1 proposed
The 15 laws behind 4.2 and 5.2.4-1

and 5 more, every one in the free file.

5.4.2-1Operators log system and user actions. 15 11 11 in force, 3 not yet in force, 1 proposed
The 15 laws behind 4.2 and 5.4.2-1

and 5 more, every one in the free file.

4.3Incident Reporting 5.2.2-5AI-specific incident management and recovery plans that are created, tested and maintained. 27 16 19 in force, 7 not yet in force, 1 proposed
The 27 laws behind 4.3 and 5.2.2-5

and 17 more, every one in the free file.

5.1.4-1Capability for human oversight designed in and maintained. 12 9 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 4.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 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 4.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 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 4.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 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 4.3 and 5.4.2-1

and 2 more, every one in the free file.

5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 6 4 3 in force, 3 not yet in force
The 6 laws behind 4.3 and 5.1.3-2
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 6 4 3 in force, 3 not yet in force
The 6 laws behind 4.3 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 6 4 3 in force, 3 not yet in force
The 6 laws behind 4.3 and 5.3.1-2.1
4.4Governance Disclosure 5.1.4-1Capability for human oversight designed in and maintained. 3 3 2 in force, 1 not yet in force
The 3 laws behind 4.4 and 5.1.4-1
5.2.1-1Full inventory of assets, including their dependencies and connections. 3 3 2 in force, 1 not yet in force
The 3 laws behind 4.4 and 5.2.1-1
5.2.4-1Developers keep an audit trail of system design and post-deployment maintenance plans... 3 3 2 in force, 1 not yet in force
The 3 laws behind 4.4 and 5.2.4-1
5.4.2-1Operators log system and user actions. 3 3 2 in force, 1 not yet in force
The 3 laws behind 4.4 and 5.4.2-1
4.5Third-Party System Access 5.2.2-5AI-specific incident management and recovery plans that are created, tested and maintained. 26 16 18 in force, 7 not yet in force, 1 proposed
The 26 laws behind 4.5 and 5.2.2-5

and 16 more, every one in the free file.

5.1.4-1Capability for human oversight designed in and maintained. 12 9 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 4.5 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 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 4.5 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 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 4.5 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 9 in force, 2 not yet in force, 1 proposed
The 12 laws behind 4.5 and 5.4.2-1

and 2 more, every one in the free file.

5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 6 4 3 in force, 3 not yet in force
The 6 laws behind 4.5 and 5.1.3-2
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 6 4 3 in force, 3 not yet in force
The 6 laws behind 4.5 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 6 4 3 in force, 3 not yet in force
The 6 laws behind 4.5 and 5.3.1-2.1
4.6User Rights & Recourse 5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 70 44 42 in force, 16 not yet in force, 12 proposed
The 70 laws behind 4.6 and 5.1.3-2

and 60 more, every one in the free file.

5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 70 44 42 in force, 16 not yet in force, 12 proposed
The 70 laws behind 4.6 and 5.3.1-1

and 60 more, every one in the free file.

5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 70 44 42 in force, 16 not yet in force, 12 proposed
The 70 laws behind 4.6 and 5.3.1-2.1

and 60 more, every one in the free file.

5.2.2-5AI-specific incident management and recovery plans that are created, tested and maintained. 6 4 3 in force, 3 not yet in force
The 6 laws behind 4.6 and 5.2.2-5
5.1.4-1Capability for human oversight designed in and maintained. 2 2 2 in force
The 2 laws behind 4.6 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 4.6 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 4.6 and 5.2.4-1
5.4.2-1Operators log system and user actions. 2 2 2 in force
The 2 laws behind 4.6 and 5.4.2-1
Not connected to the ETSI EN 304 223: 5 of MIT mitigations' controls

No law we track reaches these

No duty in the laws we track reaches these controls.

  • 1.3 Conflict of Interest Protections
  • 1.4 Whistleblower Reporting & Protection
  • 1.6 Environmental Impact Management
  • 2.2 Model Alignment
  • 3.4 Staged Deployment

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

MIT AI Risk Initiative (MIT FutureTech), AI Risk Mitigation Taxonomy. Data from the MIT AI Risk Initiative is licensed under CC BY 4.0. Cite as: Mapping AI Risk Mitigations: Evidence Scan & Draft Mitigation Taxonomy

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.