Four of today's five signals point at the same seam, and they arrived in the same week. IBM shipped a unified control layer for agents running across Bedrock, Foundry, and Gemini, with least-privilege access and real-time credential revocation (Yahoo Finance). Salesforce detailed a runtime kill switch and Agent Evals for Agent Fabric, with GA set for January 2027 (VentureBeat). Immersive Labs mapped the agent attack surface and named agent-to-agent propagation as the vector risk teams are underweighting (Immersive Labs). And Anthropic lost a verified publisher identity for twelve hours, backdooring a VS Code extension distributed through Cursor (Ars Technica).
Read together, these are one story. Agent identity governance moved from a configuration task to a platform-level competition. The two largest vendors in the cluster are now selling the Identity Control Surface as a product, and they are selling it cross-platform. That tells you where the buyers already are: managing agents that span three hyperscaler runtimes with no single policy envelope to govern them.
The index frames the gap. Governance & Ethics sits at 79, the highest organization dimension, and it ticked down a point this week. Governance maturity on paper is running ahead of governance in production. The IBM and Salesforce releases are the production answer, and the Anthropic incident is the cost of not having one. Verified-account status is not an access control. A trusted publisher identity was the attacker's entry point, and the blast radius reached every developer who updated during the window.
Here is the argument for a principal deciding this morning. The same control primitive shows up in every signal: a non-human identity holding permissions it should not retain, revocable too slowly, with no blast-radius map for what it touches downstream. IBM and Salesforce are shipping least-privilege and revocation. Immersive Labs is telling you the permission-abuse path they close is the same path attackers walk in. Microsoft's synthetic-data evaluation work (Microsoft Research) is the quieter version of the same discipline: you cannot govern what you cannot evaluate, and you cannot evaluate on data you are not permitted to touch.
The move this week is not a vendor selection. It is an inventory. Build the agent identity registry before procurement forces you to retrofit one under a January GA deadline. Every agent in production, the credentials it holds, who can revoke them, and what corrupts if it drifts. Firms without that registry are the ones the next incident is written about.
Watch item: whether Palo Alto Networks puts a formal date and distribution behind its agent identity framing on inherited credentials. If it lands, the inherited-credential failure mode joins the IBM and Salesforce cluster, and the category consolidates faster.
WatchPalo Alto Networks on inherited credentials as the core agent exposure. Palo Alto's agent identity security framing identifies shared accounts and inherited user credentials as the primary agent permission failure mode. No publication date is confirmed, so this is held from the main brief. If the piece receives a formal date and distribution push, it belongs in the Identity Control Surface cluster alongside the IBM and Salesforce releases this week.