Skip to content
IAM Insights

Explainers · Glossary

SVID

SPIFFE Verifiable Identity Document · SVIDs

SPIFFE Verifiable Identity Document: the short-lived credential, an X.509 certificate or a JWT, that a SPIFFE system issues to a workload to prove its identity.

In our briefings

The claim each of the newest briefings on SVID would have you leave with.

  1. Uber runs per-hop token exchange with a full actor chain for AI agents in production, and has published sample tokens and a latency chart. Its security token service gives each hop a fresh token scoped to one audience, with a lifetime "in the order of minutes" (both sample payloads expire 300 seconds after issue), and the token carries the attested chain from the engineer to the agent making the call. Uber says "the system has been adopted by thousands of internal agents" and reports the exchange API's P99 as "consistently below 40 milliseconds" under current load; its chart sits mostly under 10 ms, with one spike reaching 40. The post covers this identity layer. Uber frames dynamic access control and a unified policy enforcement plane as its direction on top of it, and names session and intent claims as additions the token could carry in the future.

    Uber runs per-hop token exchange with a full actor chain for AI agents in productionBI-FIND-2026-0081

  2. October's releases differ on whose identity an agent acts under. Okta and Google tie the call to the user. An MCP server registered in Okta can exchange a user's access token for a downstream token, GA in preview on October 28, so downstream systems log the user. Okta's act claim, GA in production this month, also names the service app that requested an exchange and can chain up to five of them. Google's federated query mode reaches data through MCP connectors with each user's own credentials, in preview since October 2. GitHub moved the other way for shared work: shared Copilot Automations now run as Copilot instead of their creator, as of October 28, while personal automations ran under the creator's identity. A GitHub App can also call Copilot as a workload-owned identity, in public preview since October 27. Prisma AIRS, GA on October 25, logs actions against both the agent and the human.

    Okta and Google tie an agent's calls to the user, while GitHub's shared Copilot automations now act as CopilotBI-FIND-2026-2103

  3. A SPIFFE trust domain name has no registrar behind it. The core specification calls these names "nominally self-registered": no delegating authority ties a name to a legal entity, and there is no technical means of stopping two trust domains from using the same one. Each domain has its own root of trust, so when names collide the spec says identity claims from one fail validation in the other and the two cannot federate (connect to one another). It advises a registered domain name as a suffix, or a random name such as a UUID when names are generated automatically. We read the name as a label: a relying party tells two domains apart by the root it has chosen to trust, and the name alone says nothing about who runs the domain.

    SPIFFE trust domain names have no registrar, and the core spec warns that roles in a credential can go staleBI-FIND-2026-2081

›Cited in 17 briefings

Every briefing that discusses this term, newest first.

  1. Uber runs per-hop token exchange with a full actor chain for AI agents in production

    Article · · Uber Engineering blog · Matt Mathew et al. · May 21, 2026

  2. Okta and Google tie an agent's calls to the user, while GitHub's shared Copilot automations now act as Copilot

    Release tracker · · 11 vendors' release notes · Oct 2026

  3. SPIFFE trust domain names have no registrar, and the core spec warns that roles in a credential can go stale

    Article · · SPIFFE project (GitHub) · SPIFFE project · Jul 1, 2026

  4. OAuth's SPIFFE draft opens metadata URLs to all three credentials and says what a self-served key cannot prove

    Draft · · IETF Datatracker · Arndt Schwenkschuster et al. · Jun 15, 2026

  5. IETF workload practices draft describes single-audience JWTs in place of stored secrets and discourages token exchange

    Draft · · IETF Datatracker · Arndt Schwenkschuster et al. · Sep 22, 2026

  6. Orange researchers would drop certificates from agent handshakes by putting post-quantum keys on a ledger

    Paper · · arXiv · Karol Budzyn et al. · Oct 16, 2026

  7. Six companies' agent-auth draft, since adopted by the WIMSE group, keeps credentials out of the model's reach

    Draft · · IETF Internet-Draft (individual submission, since adopted by the WIMSE working group) · Pieter Kasselman et al. · Jul 6, 2026

  8. Sharif's profile writes an AI agent's rights to pay and delete into an identity certificate valid up to a year

    Draft · · IETF Datatracker · Raza Sharif, CyberSecAI · Oct 2, 2026

  9. NIST and CISA advise one-hour tokens, 90-day keys and hardware key storage; AI agents get one paragraph

    Article · · NIST (CSRC) · Ryan Galluzzo et al. · Sep 15, 2026

  10. A survey rates only workload identity ready for agents, and argues no standard can tell what an agent intends

    Paper · · arXiv · Takumi Otsuka et al. · Apr 25, 2026

  11. A SANS instructor's broker vaults agents' real keys, but its third delivery model breaks the abstract's promise

    Draft · · IETF Datatracker · Kenneth G. Hartman · Mar 29, 2026

  12. Two ways to give an AI agent an OAuth identity clashed in April; a draft now lets them work together

    Podcast · · Hybrid Identity Protection Podcast · Securing Non-Human Identities in the Age of Agentic AI with Sarah Cecchetti, Director of Product Management at Semperis · Apr 28, 2026

  13. Outside Azure, Argo CD uses stored secrets for repositories; a March plan for per-project identity is still open

    Video · · CNCF [Cloud Native Computing Foundation] · Uploaded March 24, 2026

  14. An Alibaba and Cisco draft signs what the user was shown, then enforces a policy the agent wrote

    Draft · · IETF Datatracker · Dapeng Liu et al. · Feb 28, 2026

  15. A draft binds workload credentials to their host via a local agent, and leaves that agent's compromise undecided

    Draft · · IETF Datatracker · Ram Krishnan et al. · Feb 26, 2026

  16. A genuine TPM does not prove the server is LinkedIn's, so its SPIRE first checks the switch port and cabinet

    Video · · CNCF [Cloud Native Computing Foundation] · Uploaded November 24, 2025

  17. Uber had workload identity on a quarter-million nodes two years before agents; certificates were the easy part

    Article · · Uber Engineering · Andrew Moore et al. · Nov 9, 2023