AIUC-1 changelog

Added new mandatory requirement for code-generating agents covering detection and prevention of secrets leakage in AI system inputs, outputs, logs, and credential storage, with five new controls (A008.1-A008.5)

Added new mandatory requirement for code-generating agents to promote secure patterns and prevent known vulnerabilities in generated code, with six new controls (B010.1-B010.6)

Retired the supplemental control on alerting for auth failures; agent identity management and agent access and permissions management renumbered to A003.2 and A003.3

Clarified the control to cover data access rather than data collection

Recategorized the evidence from Technical Implementation to Operational Practices

Broadened the requirement to cover cross-customer data exposure generally, not only when combining customer data from multiple sources

Generalized typical evidence to logical isolation appropriate to the architecture rather than specific app-ID patterns

Retired the core control requiring authentication and authorization for PII access; DLP system integration renumbered to A006.2 as a supplemental control

Retagged capability scoping from generation modalities to externally facing agents

Extended sandboxed execution safeguards to cover agent-executed code alongside first-party MCP servers

Retired the core control on model access controls; remaining controls renumbered B008.1-B008.5 with agentic interface data integrity retagged as supplemental

Extended capability scoping to cover image generation alongside text and voice generation

Renamed from customer-defined to agent-specific high-risk outputs to reflect that the risk taxonomy is defined per agent

Relabelled from warning labels to content handling and labelling for untrusted content

Renumbered from C008.4 to C008.3 to close a numbering gap

Retagged capability scoping from generation modalities to externally facing agents

Retagged capability scoping from generation modalities to externally facing agents

Refocused the control on customer communication protocols and immediate mitigation steps with designated staff responsibilities

Simplified the control to focus on documenting data storage security practices such as cloud vs. on-premises assessments

Expanded the requirement to cover monitoring and logging of third-party API connections, sessions, and data access

Added new supplemental control for alerting on anomalous third-party access

Restructured controls: transparency documentation is now the core control E017.1, transparency report sharing policy retagged supplemental as E017.2, and a new supplemental control E017.3 added covering platform and deployer security responsibilities