Google gives Gemini agents their own cryptographically attested workplace identity

Google gives Gemini agents their own cryptographically attested workplace identity

by

At its Gemini at Work 2026 event on 8 October 2026, Google Cloud announced a Gemini agent for enterprise work — and, in the same keynote, a concrete answer to the question Know Your Agent starts with: who is the agent?

In the keynote, adapted for the Google Cloud blog by CEO Thomas Kurian, coworker agents get “dedicated identities including their own @agents.company.com emails, their own persistent storage, and only … access to the context that you or your team members provide”. The same agent can dynamically create a roster of sub-agents — “temporary, job-specific agents, each with their own identity“.

The blog’s governance section reduces agent deployment to four questions — who is the agent and what identity does it have; what is it allowed to do; what did it do and where can I see it; what should it never touch — and sets out Google’s answers:

  • Identity: “Every agent gets its own identity, cryptographically attested and governed like an employee, with least-privilege permissions. That identity is stamped into the logs that capture its work, and into any virtual machine spun up to run code on its behalf.”
  • Authorization: each agent gets fine-grained, role-based permissions approved by security administrators; when it connects to an external system, its identity is “mapped and propagated through industry standards such as OAuth“.
  • Auditing: “every action Gemini takes is written to an audit trail and attributed to the agent rather than to a person“, with the identity travelling into any VM the agent spins up.

Why it matters for KYA

Google has shipped much of the KYA checklist as a product feature: a dedicated agent identity, attestation, least privilege, delegation to sub-agents, and audit records attributed to the agent rather than silently to the human whose session it borrowed. The default it normalises — agents get their own identity, isolated storage and attributable logs — is exactly the shift KYA argues for, now aimed at mainstream enterprise buyers.

Two caveats keep this in proportion:

  • It is provider-scoped. This identity lives inside Google Workspace / Google Cloud. Cross-vendor recognition of a Gemini agent’s identity — the part that makes an agent passport worth carrying between systems — is not what a single vendor’s directory solves.
  • It is a vendor description, not a published standard. “Cryptographically attested” is Google’s account of its own implementation; the mechanisms, and how they interoperate with emerging agent-identity work at the IETF, W3C and DIF, are not specified here.

The practical takeaway is straightforward. If you are standing up agents this quarter, the pattern to copy is the boring one: one identity per agent, a named owner, least privilege, and a log that names the agent — not the human whose credentials it used to borrow.

Sources

Know Your Agent (KYA) explains agent identity, verification and accountability. This is an explainer, not legal or compliance advice — see our Sources & methodology. New to KYA? Start with What is Know Your Agent? and the glossary.