AIUC-1 changelog
AIUC-1 is updated formally each quarter to ensure that the standard evolves as technology, risk, and regulation evolves.
You are viewing the version of AIUC-1 that was released on April 15, 2026.
The most recent version of AIUC-1 was released on July 15, 2026.
The next version of AIUC-1 will be released on October 15, 2026.
July 15, 2026 release
For this update, focus has been on expanding coding agent requirements, developing public facing guidance for auditors and organizations pursuing AIUC-1, and further clarifications to existing requirements. This quarter’s refresh updates 8 requirements and 41 controls.
Overview of key updates
AIUC-1 for coding agents: Secrets management, secure defaults in code, execution-level safeguards broadened to coding agents
Technical guidance for auditors: Public documentation on AIUC-1 audit scoping and annual re-certification
Clarifications to existing requirements: Clearer rules for which controls apply to which agent types, and removal of duplicative controls
Detailed changelog
Detailed side-by-side comparison
Detailed comparison of previous standards (January 15, 2026 and April 15, 2026) and current standard (July 15, 2026) is available on Github here
Standard history
April 15, 2026
January 15, 2026
October 1, 2025
July 22, 2025
First launch of the standard
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.
Provide input on AIUC-1
We welcome feedback, ideas, suggestions, and criticism— provide input on AIUC-1.