Google Cloud's Gemini Enterprise Agent Platform, the rebrand and expansion of Vertex AI unveiled at Cloud Next '26, has begun shipping five governance primitives through Q2-Q3 2026: Agent Studio, Agent-to-Agent Orchestration, Agent Registry, Agent Identity, and Agent Gateway, alongside Agent Observability. Agent Identity is a native IAM type built on the CNCF SPIFFE standard, giving every agent a unique cryptographic ID, least-privilege access policies, tokens bound to the agent's runtime, and a non-repudiable audit trail of every action it takes. Agent Registry, now in Preview, is the central catalog of agents, MCP servers, and endpoints across Google-built, customer-built, and third-party assets, with automated registration through ADK and the Apigee API hub.

Agent Gateway and Model Armor are now generally available: Agent Gateway is the central policy-enforcement point governing every agent tool call and authentication, and Model Armor extends it with runtime scanning against prompt injection, jailbreaks, and PII leakage. A newer layer, Semantic Governance Policies, currently in Preview, evaluates an agent's proposed tool calls against stated user intent and organizational business rules before execution, explicitly guarding against what Google calls "toxic combinations of tools," for example, an agent that can both read a customer record and send an external email in the same session.

What this means for platform leadership: Agent Identity solves the "who is this agent" question inside Google's own estate. It does not solve it for the agent that also runs on Salesforce, Microsoft, or an internal orchestration layer, which is exactly the gap Section 02 covers next.

At Knowledge 2026, ServiceNow deepened its AI Control Tower's integration with Microsoft Agent 365: administrators now review and approve ServiceNow AI specialists before they are published to the Microsoft Agent 365 Marketplace, where an approved specialist appears in the org chart as a digital employee, complete with defined roles, permissions, and accountability, subject to Microsoft 365 identity and admin policy. ServiceNow's Autonomous Security & Risk product, built with Veza, separately maps every identity, human and non-human, and enforces least-privilege access at the point of action with a full audit trail. That follows Microsoft's own Agent 365 push earlier this year to become the identity and management layer for agents across the Microsoft estate.

Three vendors, three governance claims, and no shared standard between them. A CIO running agents across Salesforce, Microsoft, Google, and internal tooling still has no single place to answer the question every one of these platforms is separately trying to solve: how many agents can touch customer data right now, and under whose authority.

For CIO and CISO leadership: treat each vendor's control-plane claim as a partial inventory, not a complete one. The organizations best positioned for the next 12 months are the ones building their own cross-platform agent registry now, before a regulator or a security incident forces the question.

FIS and Anthropic's Financial Crimes AI Agent, announced May 4, 2026 and heading toward general availability in the second half of the year, is designed to compress anti-money-laundering alert and case investigation from days to minutes, with BMO and Amalgamated Bank both in development. Fiserv has separately launched agentOS, an operating system purpose-built for agentic banking. A Wolters Kluwer survey finds 44% of finance teams expect to use agentic AI in 2026, with regulatory-change triage, financial-crime detection, and controls monitoring drawing the most investment, because each pairs high transaction volume with a containable cost of error.

For risk and compliance leadership: the safest posture right now is to document your own AML or financial-crime agent's identity model, its access boundaries, and its audit trail as though an examiner will ask about it next quarter, because the guidance that would tell you what's required has not caught up yet.

Valley Children's Hospital in California is using ambient documentation to cut physician administrative burden, Epic CosmOS to aid diagnosis of rare diseases, and genomic-data integration to optimize medication therapy across a service area of more than 1.3 million children. NextGen Navigator, an AI customer-service agent, now manages appointment scheduling, medication refills, and practice information, saving staff an estimated 2-3 hours daily. Across production administrative healthcare agents broadly, organizations report 60-80% reductions in manual admin FTEs and 40-55% cost-per-claim improvement; Smilist, a dental service organization scaling past 100 locations, runs more than 3,000 automated claim-status checks daily.

In manufacturing, Siemens' Erlangen factory cut energy consumption 42% while holding productivity gains, using an agentic system that aligns production against real-time grid pricing, demand, and environmental targets, shifting heavy loads into off-peak or green windows and making micro-adjustments without cutting total output. Grid-side agentic systems are increasingly asked to orchestrate wind, battery, and solar resources in real time and to self-heal during disruptions or outages, precisely as AI data center growth, manufacturing reshoring, and transportation electrification strain grid capacity.

For healthcare, manufacturing, and energy leadership: every one of these production agents already has real access to patient data, plant equipment, or grid assets. The identity question is not theoretical for these deployments, it is operational today, and it is the same OT/IT and clinical/administrative boundary question raised in Sections 01 and 02, just with a physical or clinical safety dimension layered on top.

On June 29, 2026, Senator Mark Warner (D-VA) released a discussion draft titled the Artificial Intelligence Access, Gatekeeper Exchange, and Nondiscriminatory Transfer Act, the AI AGENT Act. The draft would let users of large online platforms, those with more than 50 million monthly users or subscribers, choose at least one AI agent provider that complies with security and identity standards developed by the Federal Trade Commission. It directs the National Institute of Standards and Technology to identify protocols and technical standards supporting interoperability across agent platforms, tasks the FTC with issuing rules and policing compliance, and would bar covered agent providers from using data collected on a user's behalf for advertising or other secondary commercial purposes.

For general counsel and CRO leadership: this is a discussion draft, not law, and Warner is actively soliciting stakeholder feedback before formal introduction. That makes now the window to weigh in, and to make sure whatever agent-identity architecture your organization adopts this year can adapt to a federal interoperability standard rather than fight it.