Overview of key updates
- Clarified 13 requirements based on audit experience, customer feedback, and input from technical contributors.
- Strengthened adversarial testing requirement to mandate independent third-party testing.
- Expanded ISO 42001 crosswalk with gap analysis and descriptive notes to support organizations comparing AIUC-1 and ISO 42001.
Detailed change log
| Date | AIUC-1 requirement and control | Category | Change notes |
|---|---|---|---|
| Q4 2025 | A001: Establish input data policy, A002: Establish output data policy | Clarification | Clarified separation of A001 vs A002: A001 labeled as input data; A002 labeled as output data. Control activity language adjusted to clarify distinction |
| Q4 2025 | A003: Limit AI agent data collection | Clarification | Requirement title clarified to emphasize focus on AI agent configuration |
| Q4 2025 | A005: Prevent cross-customer data exposure | Specification | Specified to reflect that cross-customer data safeguards should apply not just for model training purposes |
| Q4 2025 | B001: Third-party testing of adversarial robustness | Specification | Specified to require that adversarial testing of system robustness is conducted by a third-party |
| Q4 2025 | B003: Manage public release of technical details, B009: Limit output over-exposure | Clarification | Clarified separation of B001 vs B009: B001 labeled as managing public release of technical details; B009 labeled as limiting output over-exposure Requirement text clarified to highlight the distinction |
| Q4 2025 | B006: Limit AI agent system access | Clarification | Requirement title clarified to emphasize focus on AI agent configuration |
| Q4 2025 | B007: Enforce user access privileges to AI systems | Clarification | Requirement title clarified to emphasize focus on user access privileges |
| Q4 2025 | C005: Prevent customer-defined high risk outputs | Clarification | Requirement title clarified to highlight that additional risk areas are defined by customer |
| Q4 2025 | C009: Enable real-time feedback and intervention | Clarification | Requirement title updated to emphasize human intervention capability in requirement |
| Q4 2025 | C012: Third-party testing for customer-defined risk | Clarification | Requirement title clarified to highlight that additional risk areas are defined by customer |
| Q4 2025 | E013: Implement quality management system | Specification | Removed reference to “high-risk” in requirement to specify that quality management system should apply to entire AI system |
| Q4 2025 | ISO 42001 crosswalk | Expansion | Expanded AIUC-1 to ISO 42001 mapping with gap analysis and description of gaps to enable easy comparison |
| Q4 2025 | Technical testing passing criteria | Specification | Specified that companies must pass AIUC-1 technical tests with no P0 or P1 vulnerabilities identified to qualify for an AIUC-1 certificate Reflected on Certificate overview page |
Side-by-side version comparison
| AIUC-1 requirement | 2025-07-01 | 2025-10-01 |
|---|---|---|
| A001 | A001: Establish data use policy | A001: Establish input data policy |
| A002 | A002: Define output rights | A002: Establish output data policy |
| A003 | A003: Implement contextual data safeguards | A003: Limit AI agent data collection |
| A005 | Implement safeguards to prevent cross-customer data exposure when combining customer data from multiple sources for AI model training | Implement safeguards to prevent cross-customer data exposure when combining customer data from multiple sources for AI model training |
| B003 | B003: Limit technical over-disclosure | B003: Manage public release of technical details |
| B001 | B001: Test adversarial robustness | B001: Third-party testing of adversarial robustness |
| B006 | B006: Enforce contextual access controls | B006: Limit AI agent system access |
| B007 | B007: Enforce AI access privileges Establish and maintain access controls and admin privileges for AI systems in line with policy | B007: Enforce user access privileges to AI systems Establish and maintain user access controls and admin privileges for AI systems in line with policy |
| B009 | Implement output limitations and obfuscation techniques to reduce information leakage | Implement output limitations and obfuscation techniques to safeguard against information leakage |
| C005 | C005: Prevent other high risk outputs | C005: Prevent customer-defined high risk outputs |
| C009 | C009: Collect real-time feedback | C009: Enable real-time feedback and intervention |
| C012 | C012: Third-party testing for other risk | C012: Third-party testing for customer-defined risk |
| E013 | Establish a quality management system for high-risk AI systems proportionate to the size of the organization | Establish a quality management system for AI systems proportionate to the size of the organization |
37.782274° N -122.392147° WFIG. A (SITE INDEX)
Artificial Intelligence Underwriting Company
CodeStructural unita.AIUC-1 requirements for agent data, privacy, security, safety, reliability, accountability, and societal risk.b.Evidence templates for technical implementation, legal policy, operational practice, and third-party evaluation.c.Crosswalks to AI regulations, standards, and security frameworks.d.Quarterly updates shaped by enterprise adoption, risk, regulation, and community input.
I. Standard
II. Learn
III. Office
100© AIUC — ALL RIGHTS RESERVED