October 15, 2026 release
This update focused on governing open-weight model deployments, expanding third-party testing requirements, and providing guidance around agent developers and deployers. This quarter’s refresh led to 5 new requirements, 5 new controls and 3 retired requirements.Overview of key updates
- Open-weight model deployments: New controls governing the verification, testing and evaluation of open-weight models before deployment.
- Expanded third-party testing: New comprehensive third-party testing requirements per AIUC-1 principle, paired with the release of a public incident database, and a risk and attack taxonomy informing the scope of third-party testing conducted.
- Developer and deployer responsibilities: Guidance on how AIUC-1 controls are typically met by the developer and deployer of the agent platform, developed by working group with Consortium members from ElevenLabs, McKinsey, PwC, Noma Security, Datavant, Commerzbank, Veeam Software and more.
Detailed changelog
Detailed side-by-side comparison
Detailed comparisons of current and previous AIUC-1 standards are available on GitHub.Standard history
Tenets that guide the standard update
- Customer-focused. We prioritize requirements that enterprise customers demand and vendors can pragmatically meet, increasing confidence without adding unnecessary compliance.
- AI-focused. We do not cover non-AI risks that are addressed in frameworks or regulations like SOC 2, ISO 27001, or GDPR.
- Insurance-enabling. We prioritize risks that lead to direct harms and financial losses.
- Adapts to regulation. We update AIUC-1 to make it easier to comply with new regulations.
- Adapts to AI progress. We update AIUC-1 to keep up with new capabilities, like reasoning capabilities and new modalities.
- Adapts to the threat landscape. We update AIUC-1 in response to real-world incidents.
- Continuous improvement. We regularly update the standard based on real-world deployment experience and stakeholder feedback.
- Predictability. We review the standard and push updates quarterly, on January 15, April 15, July 15, and October 15 of each year.
- Transparency. We keep a public changelog and share our lessons.
- Backward compatibility. Existing certifications remain valid during transition periods.