§ The CISO Learning Journey · Week 5 · Phase 2 · Diagnosis · June 23, 2026

The Agent Governance category —
what Google just formalized.

By Lindsay Hiebert · Founder · CISSP

The four-layer Shadow AI risk model places agentic AI as Layer 4 — the surface Google formalized at Cloud Next '26 under the Agent Governance category.
Layer 4 · The agentic surface

Google Cloud Next ’26 (April 2026) formalized a new category of enterprise software: Agent Governance. The category covers AI agents, MCP (Model Context Protocol) servers, A2A (agent-to-agent) discovery chains, and the autonomous AI tools increasingly acting on enterprise systems without continuous human oversight. Google’s five-pillar architecture — Agent Registry, Agent Gateway, Agent Identity, Pluggable Policies, Agent Observability — is the most thorough public articulation of how to govern this surface to date. It is also designed for the Fortune 1000 with a platform engineering team.

The existing security stack — IAM (Identity and Access Management), SIEM (Security Information and Event Management), GRC (Governance, Risk, and Compliance), CNAPP (Cloud-Native Application Protection Platform), and even AI-SPM (AI Security Posture Management) platforms like Wiz and Palo Alto AI Access — was not built for this category. It governs human accounts, not autonomous agent identities. It enforces network controls, not delegated-authority policies. It observes runtime telemetry, not the regulation-anchored AUP a board signs. The category is genuinely new, not a renamed AI-SPM, and the mid-market (50–2,000 employees) needs a companion to Google’s architecture that does not require a platform engineering team to deploy.

What to do. Treat Agent Governance as its own discipline. Understand the four-layer Shadow AI risk surface (Layer 4 is the agentic layer). Produce a regulation-anchored AUP that includes a Deployed Agent Policy section. SanctumShield generates that AUP — Section 14 explicitly covers agent registration, MCP server allowlisting, A2A discovery boundaries, agent identity and credentials, kill-switch procedures, and agent-authored code governance — in 10 minutes for $99/month with no platform engineering required. Multi-LLM agentic synthesis (Claude + Gemini) cross-validates every clause at generation time. Next step: see the Layer 4 audit in a real Acme Health artifact at /sample-outputs.

§ Why this is a legal question, not a tooling preference

Everything above is an argument about method. Underneath it sits an obligation that does not depend on which method you pick. Documented, dated, demonstrable governance is what the law asks for, and the dates have stopped being in the future.

EU AI Act Article 4 — AI literacy
In force since February 2, 2025. National enforcement began August 2, 2026.
EU AI Act Article 50 — transparency
Applies since August 2, 2026.
Colorado SB 26-189
Effective January 1, 2027.
EU AI Act Articles 12, 14 and 17 — record-keeping, human oversight, quality management
High-risk regime: December 2, 2027 (Annex III) and August 2, 2028 (Annex I).

Read those together and the shape is consistent. Each one asks an organization to produce something — a measure taken, a disclosure made, a record kept, a review performed — and to be able to show it after the fact. None of them names a product, a platform or a link, and nothing here should be read as saying a law requires one. What a law requires is the record. Making that record dated and third-party-verifiable is simply how you let an auditor, an underwriter or a board confirm it without being handed the contents, or being asked to take your word for it.

And literacy is not one obligation among several. It is the one the others rest on. You cannot exercise due diligence over a system you cannot recognise, and you cannot govern an authority you do not understand you have delegated.

That is why Article 4 sits in the opening chapter of the Act, ahead of the risk tiers, and why it applied eighteen months before the high-risk regime does. The duty is to take measures that support the development of AI literacy among the people operating AI on the organization’s behalf — and the useful version of that is matched to the seat. What a director needs to recognise is not what a developer needs to recognise, and neither is what the person pasting a contract into a browser tab needs to recognise. A single org-wide module satisfies the form and misses the point.

Free Shadow AI Risk Audit

See what your current stack is missing — in 12 questions.

The SanctumShield free Shadow AI Risk Calculator runs in your browser. No account, no email, no credit card. Twelve questions, instant risk score, three primary findings tailored to what you submit.

CISO Learning Journey: Week 5 of 27 · Phase 2 (Diagnosis) · see the full series →

The Agent Governance Category — What Google Just Formalized — SanctumShield