Law / Frameworks / Crosswalk / FINOS AIGF to ETSI EN 304 223

The FINOS AI Governance Framework, mapped to the ETSI EN 304 223, Baseline Cyber Security Requirements for AI Models and Systems

16 of FINOS AIGF's 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
FINOS AI Governance Framework, version 2, as maintained on , FINOS
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 FINOS AIGF, the other way · every pair in the crosswalk · law library as of

Download this mapping, with every law behind each connection: finos-ai-governance-framework--etsi-en-304-223.csv · finos-ai-governance-framework--etsi-en-304-223.json

FINOS AIGFETSI EN 304 223LawsJurisdictionsWhere the laws stand
AIR-PREV-005System Acceptance Testing 5.1.2-1Business need and security risks written down and assessed before deciding to build an... 156 94 130 in force, 17 not yet in force, 1 blocked by a court, 8 proposed
The 156 laws behind AIR-PREV-005 and 5.1.2-1

and 146 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 AIR-PREV-005 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. 78 37 50 in force, 27 not yet in force, 1 proposed
The 78 laws behind AIR-PREV-005 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 AIR-PREV-005 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 AIR-PREV-005 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 AIR-PREV-005 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 AIR-PREV-005 and 5.1.3-1

and 4 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 AIR-PREV-005 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 AIR-PREV-005 and 5.1.4-3
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 AIR-PREV-005 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 AIR-PREV-005 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 AIR-PREV-005 and 5.3.1-2.1
AIR-PREV-006Data Quality & Classification/Sensitivity 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 AIR-PREV-006 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 AIR-PREV-006 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 AIR-PREV-006 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 AIR-PREV-006 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 AIR-PREV-006 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,... 5 3 3 in force, 2 not yet in force
The 5 laws behind AIR-PREV-006 and 5.1.4-3
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 AIR-PREV-006 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 AIR-PREV-006 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 AIR-PREV-006 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 AIR-PREV-006 and 5.1.3-1
AIR-PREV-007Legal and Contractual Frameworks for AI Systems 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 AIR-PREV-007 and 5.2.4-2.1

and 8 more, every one in the free file.

5.1.2-6Access the AI system gets to other systems and data sources is minimal and risk assessed. 7 5 7 in force
The 7 laws behind AIR-PREV-007 and 5.1.2-6
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 AIR-PREV-007 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 AIR-PREV-007 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 AIR-PREV-007 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 AIR-PREV-007 and 5.4.2-2
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 AIR-PREV-007 and 5.1.2-7
5.1.4-1Capability for human oversight designed in and maintained. 2 2 2 in force
The 2 laws behind AIR-PREV-007 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 AIR-PREV-007 and 5.2.1-1
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 AIR-PREV-007 and 5.2.2-6
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 AIR-PREV-007 and 5.2.4-1
5.4.2-1Operators log system and user actions. 2 2 2 in force
The 2 laws behind AIR-PREV-007 and 5.4.2-1
AIR-PREV-008Quality of Service (QoS) and DDoS Prevention for AI Systems 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 AIR-PREV-008 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 AIR-PREV-008 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 AIR-PREV-008 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 AIR-PREV-008 and 5.4.2-2
AIR-PREV-012Role-Based Access Control for AI Data 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 AIR-PREV-012 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 AIR-PREV-012 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 AIR-PREV-012 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 AIR-PREV-012 and 5.4.2-2
AIR-PREV-014Encryption of AI Data at Rest 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 AIR-PREV-014 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 AIR-PREV-014 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 AIR-PREV-014 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 AIR-PREV-014 and 5.4.2-2
AIR-PREV-017AI Firewall Implementation and Management 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 AIR-PREV-017 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 AIR-PREV-017 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 AIR-PREV-017 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 AIR-PREV-017 and 5.4.2-2
AIR-PREV-018Agent Authority Least Privilege Framework 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 AIR-PREV-018 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. 2 2 2 in force
The 2 laws behind AIR-PREV-018 and 5.2.4-2.1
AIR-PREV-020MCP Server Security Governance 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 AIR-PREV-020 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 AIR-PREV-020 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 AIR-PREV-020 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 AIR-PREV-020 and 5.4.2-2
AIR-PREV-023Agentic System Credential Protection Framework 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 AIR-PREV-023 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. 2 2 2 in force
The 2 laws behind AIR-PREV-023 and 5.2.4-2.1
AIR-PREV-024Human-in-the-Loop Action Approval Gate 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 AIR-PREV-024 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 AIR-PREV-024 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 AIR-PREV-024 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 AIR-PREV-024 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 AIR-PREV-024 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 AIR-PREV-024 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 AIR-PREV-024 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 AIR-PREV-024 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 AIR-PREV-024 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 AIR-PREV-024 and 5.1.3-1
AIR-DET-001AI Data Leakage Prevention and Detection 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 AIR-DET-001 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 AIR-DET-001 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 AIR-DET-001 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 AIR-DET-001 and 5.4.2-2
AIR-DET-004AI System Observability 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 AIR-DET-004 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 AIR-DET-004 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 AIR-DET-004 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 AIR-DET-004 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. 27 16 19 in force, 7 not yet in force, 1 proposed
The 27 laws behind AIR-DET-004 and 5.2.2-5

and 17 more, every one in the free file.

5.1.3-2Threats developers cannot resolve are passed to operators and on to end-users. 7 5 4 in force, 3 not yet in force
The 7 laws behind AIR-DET-004 and 5.1.3-2
5.3.1-1Users told where and how their data is used, accessed and stored, with developers... 7 5 4 in force, 3 not yet in force
The 7 laws behind AIR-DET-004 and 5.3.1-1
5.3.1-2.1That guidance covers proper use, limits and likely failure modes. 7 5 4 in force, 3 not yet in force
The 7 laws behind AIR-DET-004 and 5.3.1-2.1
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 AIR-DET-004 and 5.1.4-3
5.1.3-1Threat modelling and risk management, reviewed regularly and covering AI-specific attacks. 2 1 2 in force
The 2 laws behind AIR-DET-004 and 5.1.3-1
AIR-DET-011Human Feedback Loop for AI Systems 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 AIR-DET-011 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 AIR-DET-011 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 AIR-DET-011 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 AIR-DET-011 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 AIR-DET-011 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 AIR-DET-011 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 AIR-DET-011 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 AIR-DET-011 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 AIR-DET-011 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 AIR-DET-011 and 5.1.3-1
AIR-DET-013Providing Citations and Source Traceability for AI-Generated Information 5.1.2-6Access the AI system gets to other systems and data sources is minimal and risk assessed. 5 3 5 in force
The 5 laws behind AIR-DET-013 and 5.1.2-6
AIR-DET-021Agent Decision Audit and Explainability 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 AIR-DET-021 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 AIR-DET-021 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 AIR-DET-021 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 AIR-DET-021 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 AIR-DET-021 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 AIR-DET-021 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 AIR-DET-021 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 AIR-DET-021 and 5.2.2-5

and 16 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 AIR-DET-021 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 AIR-DET-021 and 5.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 AIR-DET-021 and 5.1.3-1
Not connected to the ETSI EN 304 223: 9 of FINOS AIGF'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

FINOS AI Governance Framework, copyright 2025 FINOS, licensed under CC BY 4.0. Titles and purpose text are quoted; markdown emphasis and links were removed.

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.