# What is SPIFFE?

> SPIFFE is an open standard that gives every running service a verifiable identity. A local API hands each workload a short-lived certificate that names it, so services can prove who they are to each other without shared secrets.

Explainer by Boston Identity, 2026-10-15. 7 min read. https://insights.bostonidentity.com/glossary/spiffe

- What it is: standard
- Defined by: SPIFFE project (CNCF), stable specifications
- Who it's for: Teams running services or AI agents that call each other

## What is SPIFFE?

Services call each other all day, and each needs to know who is calling. The usual answer has been a long-lived shared credential, such as an API key or a service-account password, and CyberArk now issues SPIFFE identity documents in its place [BI-FIND-2026-1186](https://insights.bostonidentity.com/ref/BI-FIND-2026-1186). SPIFFE, the Secure Production Identity Framework For Everyone, is a framework for bootstrapping and issuing identity to services across different environments and organizations [S1 Abstract]. Its certificate specification says that perhaps its most important job is securing communication from one process to another [S2 §1].

Every workload gets a SPIFFE ID, a URI such as spiffe://staging.example.com/payments/web-fe [S1 §2.2]. The part after spiffe:// is the trust domain, which names the system that issued the identity [S1 §2]. The path names the workload, and the administrator decides what it means [S1 §2.2]. A workload proves its ID with a SPIFFE Verifiable Identity Document (SVID), signed by an authority inside its trust domain [S1 §3]. An SVID reuses an existing format, an X.509 certificate, a JSON Web Token (JWT) or a workload identity token (WIT), and each format has its own specification [S1 §3.3].

Think of it like this: Think of a staff badge the front desk prints fresh each morning for whoever comes through the staff door, which another office accepts only if it keeps a copy of your company's stamp. The comparison stops at the desk: SPIFFE leaves how the caller is recognized to each implementation.

Not the same as: Not the same as SPIRE. SPIFFE is the set of specifications. SPIRE is software that runs them, such as the agent on each host that Uber's services ask for their credentials [BI-FIND-2023-0007](https://insights.bostonidentity.com/ref/BI-FIND-2023-0007).

## How does SPIFFE work?

Take the specification's own example: a web front end and a MySQL database, both part of a payments service in the staging.example.com trust domain [S1 §2.2]. The front end wants to call the database, and each service can reach a local Workload API.

[Figure: Neither service starts with a secret: each gets its certificate and key from the local Workload API, and trusts the other only through the bundle for the other's trust domain.]

1. **The front end asks the Workload API.** The front end connects to the local Workload API and calls FetchX509SVID [S3 §5.1]. It sends no password or key. The endpoint does no direct client authentication. Its implementation identifies the caller through out-of-band checks and decides what to serve [S3 §4.1]. A caller that is entitled to nothing should get a PermissionDenied error [S3 §5.2.1].
2. **The API hands back an identity.** The reply carries one X509-SVID for each identity the caller is entitled to [S3 §5.2.1]. Each comes with its private key and the trust bundle for its trust domain [S3 §5.1]. A bundle is the set of keys used to check that domain's SVIDs [S4 §3]. The certificate holds the SPIFFE ID in exactly one URI subject alternative name (SAN), and a validator must reject an SVID with more than one [S2 §2]. The database gets its own SVID the same way, since the API serves any process that can reach it [S3 §4.1].
3. **The two services open mutual TLS.** The front end connects to the database over TLS, and each side presents its X509-SVID as its certificate [S2 §1]. The database checks the client, and the front end checks the server [S3 §4.6]. A workload certificate should list its extended key usages, and if it does, it must allow both server and client use [S2 §4.4].
4. **Each side checks the other's SVID.** Each side picks the bundle for the trust domain in the peer's SPIFFE ID and validates against it [S3 §4.6]. If it holds no bundle for that domain, the peer is untrusted. The chain check must follow standard X.509 path validation (RFC 5280) [S2 §5.1]. Then come the SPIFFE checks: the certificate must not be a signing certificate, the scheme must be spiffe, and the ID must have a path [S2 §5.2]. A signing certificate may issue further signing certificates in other trust domains [S2 §3.2], and the name constraints that would stop it are optional [S2 §4.2]. Choosing the bundle by the peer's trust domain is what stops one domain's authority from vouching for another domain's IDs, which is why the Workload API specification requires that choice [S3 §4.6]. If one root key is shared across trust domains, the database's authorization rules also need to check the trust domain explicitly [S4 §6.2].
5. **A partner's bundle lets calls cross domains.** To trust a service in another trust domain, a workload needs that domain's bundle. The API can return bundles for foreign trust domains, keyed by the domain's ID [S3 §5.1]. The specification calls these federated bundles the main way trust domains connect [S3 §4.6]. A bundle is a standard JSON Web Key (JWK) set, and each key is marked with the kind of SVID it checks [S4 §4] [S4 §4.2.2]. Bundles are meant to pass between SPIFFE control planes, and the Workload API carries their updates to workloads [S4 §3].
6. **The API streams rotations and revocations.** The workload should keep its connection open [S3 §4.2]. The API sends a new message when something changes, such as a rotated SVID or an updated revocation list, and every message must carry the full set of information [S3 §4.3]. Anything left out counts as withdrawn: a missing bundle should be unloaded, and a dropped SVID should no longer be used [S3 §4.4] [S3 §5.2.1]. Root keys rotate through the bundle too. In the specification's example, a replacement certificate is added well before the old one expires [S4 Appendix A].

## Why does SPIFFE matter now?

AI agents have reopened the question SPIFFE answered for services. Six engineers from six competing companies wrote an IETF draft arguing that an agent is a workload, and that WIMSE, SPIFFE, OAuth and the OpenID Shared Signals Framework already cover it. The IETF's workload identity working group (WIMSE) adopted that work on 15 September 2026 [BI-FIND-2026-0178](https://insights.bostonidentity.com/ref/BI-FIND-2026-0178). The draft says an agent must hold short-lived, key-bound credentials, lists a SPIFFE SVID as one allowed form, and calls static API keys an antipattern [BI-FIND-2026-0179](https://insights.bostonidentity.com/ref/BI-FIND-2026-0179). An April 2026 survey graded WIMSE with SPIFFE as the only agent-identity work ready for production, though the grades are the three authors' own judgement [BI-FIND-2026-0643](https://insights.bostonidentity.com/ref/BI-FIND-2026-0643).

The standards bodies are building on SPIFFE. The IETF's workload certificate is an ordinary X.509 certificate with one URI SAN, which the draft calls fully compatible with the X509-SVID [BI-FIND-2026-0375](https://insights.bostonidentity.com/ref/BI-FIND-2026-0375). An OAuth working-group draft lets a workload sign in to an authorization server with its SPIFFE credential instead of a client secret, and one implementation, Keycloak in preview, supports part of it [BI-FIND-2026-0316](https://insights.bostonidentity.com/ref/BI-FIND-2026-0316). NIST's National Cybersecurity Center of Excellence lists SPIFFE among the existing standards it is considering for agent identity [BI-FIND-2026-0686](https://insights.bostonidentity.com/ref/BI-FIND-2026-0686).

Uber ran SPIFFE and SPIRE under 4,500 services on hundreds of thousands of hosts by 2023 [BI-FIND-2023-0006](https://insights.bostonidentity.com/ref/BI-FIND-2023-0006). When its agent platform went live, it still could not trace an automated pull request back to the engineer who started the chain [BI-FIND-2026-0082](https://insights.bostonidentity.com/ref/BI-FIND-2026-0082). We read the two Uber accounts together as evidence that workload identity is necessary for agents and not sufficient [BI-FIND-2023-0006](https://insights.bostonidentity.com/ref/BI-FIND-2023-0006). CyberArk's Secure Workload Access became generally available on 28 May 2026, issuing SPIFFE identity documents to Kubernetes and Unix workloads [BI-FIND-2026-1186](https://insights.bostonidentity.com/ref/BI-FIND-2026-1186).

## Where does it fit?

- Compared with WIMSE Workload Identifier: The IETF's workload identifier is a looser URI syntax that existing SPIFFE IDs pass unchanged, and it registers its own wimse scheme. Unlike SPIFFE, it does not say how identifiers are issued or verified [BI-FIND-2026-0386](https://insights.bostonidentity.com/ref/BI-FIND-2026-0386).
- Compared with OAuth SPIFFE Client Authentication: This OAuth draft builds on SPIFFE: it lets a workload present its SPIFFE credential to an authorization server in place of a client secret [BI-FIND-2026-0316](https://insights.bostonidentity.com/ref/BI-FIND-2026-0316). The four SPIFFE documents we read do not mention OAuth.
- Compared with JWT: A JWT is a general token format. SPIFFE uses it as one SVID type, the JWT-SVID, which a workload requests for a named audience and a validator checks against the bundle for the subject's trust domain [S3 §6.2.1] [S3 §6.3].
- Compared with OAuth: In WorkOS's account, a standard like SPIFFE issues the credential after the workload proves what it is, and runtime authorization is left to OAuth [BI-FIND-2026-0408](https://insights.bostonidentity.com/ref/BI-FIND-2026-0408).

## What goes wrong?

- Trust domain names are self-registered. Two operators can pick the same name, and colliding domains cannot federate, so the specification advises a registered domain name as a suffix [S1 §2.1] [S1 §2.1.1].
- An SVID's contents count as true for its whole lifetime. Revoking a claim inside one means waiting for every copy to expire, so the specification advises leaving out things that change, such as roles or group membership [S1 §4.1.1].
- A partner domain's word is only as good as that domain. A compromised domain could claim to have authenticated any user it wishes, and a role called admin in one domain means nothing in another [S1 §4.1.4] [S1 §4.1.2].
- A root key shared across trust domains blurs them: unless authentication checks the domain name, an SVID from any of them can pass. The specification strongly advises one key per domain [S4 §2] [S4 §6.2].
- Slow bundle refresh slows revocation. Without a refresh hint, clients should poll often, around every five minutes in the specification's example [S4 §6.1].
- The specifications leave how the endpoint recognizes a caller to the implementation [S3 §4.1]. At Uber, that check is mainly a label from a trusted launcher, and the post describes no measurement of the running code [BI-FIND-2023-0007](https://insights.bostonidentity.com/ref/BI-FIND-2023-0007).
- The OAuth draft that joins SPIFFE to OAuth does not discuss a compromised trust domain or SPIRE server [BI-FIND-2026-0318](https://insights.bostonidentity.com/ref/BI-FIND-2026-0318). The OpenID Foundation's paper argues that SPIFFE's identity depends on controlling the infrastructure, so it does not cross into another organization [BI-FIND-2025-0057](https://insights.bostonidentity.com/ref/BI-FIND-2025-0057).

## What should a security leader ask?

1. Which of our services still prove who they are to each other with a stored key or password?
2. How does our Workload API decide which process is calling, and who can change that registration data?
3. Which partner trust domains do our workloads accept, and how fast does a revoked key drop out of their bundles?
4. Do our authorization rules check the trust domain in a SPIFFE ID, or only the path?
5. For our AI agents, what records the person who started each task, since an SVID names only the workload?

## Sources

- [S1] [The SPIFFE Identity and Verifiable Identity Document](https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE-ID.md) (SPIFFE project (CNCF), Stable)
- [S2] [The X.509 SPIFFE Verifiable Identity Document](https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md) (SPIFFE project (CNCF), Stable)
- [S3] [The SPIFFE Workload API](https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_API.md) (SPIFFE project (CNCF), Stable (WIT-SVID profile incubating))
- [S4] [The SPIFFE Trust Domain and Bundle](https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Trust_Domain_and_Bundle.md) (SPIFFE project (CNCF), Stable)

## Evidence

- [BI-FIND-2026-1186](https://insights.bostonidentity.com/ref/BI-FIND-2026-1186): May's machine-identity releases split between replacing stored credentials and managing them. CyberArk's Secure Workload Access went GA on May 28, issuing SPIFFE identity documents to Kubernetes and Unix workloads in place of long-lived shared credentials. Microsoft's provisioning service can now reach SAP SuccessFactors with workload identity and short-lived tokens instead of a stored password, in public preview. Other releases still manage stored secrets: AWS Secrets Manager now rotates Datadog keys and Snowflake tokens, Okta's service account management for Privileged Access went GA, and CyberArk's Kubernetes discovery agent now collects secret values by default. (from "Three vendors put MCP controls in three different places in May, and only Auth0's was GA")
- [BI-FIND-2023-0007](https://insights.bostonidentity.com/ref/BI-FIND-2023-0007): What a workload is, in Uber's system, is whatever the launcher said it was. Identity reaches developers as an Auth library in Go and Java that subscribes to the local SPIRE agent, attaches the credential in RPC middleware and verifies it on the way in; Uber chose a library over a sidecar or binary because its monorepos and shared RPC frameworks made the library the cheaper path to every service. Attestation is 'primarily' container-based: launchers, themselves attested, apply labels naming the service, environment and platform, and the agent maps those labels to a registered entry. No measurement of the running code is described. The IETF's credentials draft leaves attestation out of scope, and this is what out of scope looks like at a large operator: a trusted launcher's label. (from "Uber had workload identity on a quarter-million nodes two years before agents; certificates were the easy part")
- [BI-FIND-2026-0178](https://insights.bostonidentity.com/ref/BI-FIND-2026-0178): Six engineers from six companies that compete with each other, Defakto, AWS, Zscaler, Ping Identity, OpenAI and Okta, wrote one draft whose first claim is that everyone else is 'reinventing existing mechanisms unaware of applicable prior art', and whose answer is to define no new protocol at all: an agent is a workload, and WIMSE, SPIFFE, OAuth 2.0 and the OpenID Shared Signals Framework already cover it. On 15 September 2026 the WIMSE working group adopted the work as draft-ietf-wimse-aims, 'AI Identity Management System', with the same six authors; the datatracker now marks the revision we read as replaced. That is the bet Highflame's ZeroID makes with its eighteen implemented specifications, the one Uber made by tracking this draft, and the one the summit's practitioner recommended from the stage: the agent-identity layer is assembled, not invented, and the assembly now has a working group. (from "Six rival vendors wrote the agent-identity draft the IETF just adopted, and it invents nothing")
- [BI-FIND-2026-0179](https://insights.bostonidentity.com/ref/BI-FIND-2026-0179): The rule Sierra built its cloud agent around is now normative text. An agent MUST have one WIMSE identifier and short-lived credentials bound to a key, a Workload Identity Token, an X.509 workload certificate or a SPIFFE SVID; 'static API keys are an antipattern for agent identity'; and the language model inside the agent never holds the credential, which the draft says 'prevents the Large Language Model from using, exposing, or being manipulated via prompt injection into disclosing the credentials'. Sierra's harness has no network access and a supervisor swaps the credential in; the summit's vendors said never hand an agent a raw token; Anthropic's evaluation agent improvised its own PyPI account because nothing stopped it. Three months after the incident and two after the post, the boundary is written down by six vendors at once. (from "Six rival vendors wrote the agent-identity draft the IETF just adopted, and it invents nothing")
- [BI-FIND-2026-0643](https://insights.bostonidentity.com/ref/BI-FIND-2026-0643): In the authors' grading of ten standards documents for agent identity, only the IETF's workload-identity work (WIMSE) with SPIFFE counts as available for production; SAML is graded incompatible, and the rest, including OAuth extensions for agents and the AI agent authentication draft whose security section still reads 'TODO', are partial or directional. The grades are the authors' own judgement over about 80 sources found by keyword search, with no scoring method or second rater, so they record what three researchers concluded in April 2026. (from "A survey rates only workload identity ready for agents, and argues no standard can tell what an agent intends")
- [BI-FIND-2026-0375](https://insights.bostonidentity.com/ref/BI-FIND-2026-0375): Half of this draft is already running and the other half is not, and the draft says so. The Workload Identity Certificate is an ordinary X.509 certificate with the workload identifier in exactly one URI SubjectAltName, which the implementation section calls 'fully compatible with the X509-SVID' that SPIFFE deployments have issued for years; SPIFFE deployments simply use their spiffe URIs as the subject. The new piece is the JWT form, and the self-reported status reads beta at SPIFFE, alpha at Defakto Security and research at Teleport, against production for the certificate at all three. The IETF is standardizing the certificate the industry already has and attaching a token nobody has shipped yet. (from "The IETF's workload credential binds one key to one name and says nothing else about the software holding it")
- [BI-FIND-2026-0316](https://insights.bostonidentity.com/ref/BI-FIND-2026-0316): An OAuth working-group draft lets a workload authenticate to an authorization server with the identity its platform issued, in place of a stored secret. It covers three forms of SPIFFE credential: a signed token presented under a new assertion type, a certificate presented over mutual TLS, and a key-bound workload token with a proof of possession. A server must advertise which it accepts and support at least one. This is the missing piece between workload identity and OAuth that speakers in this corpus have been calling duct tape, now on the standards track. One implementation is listed, Keycloak, in preview, for the first of the three forms. (from "A draft lets a workload sign in to OAuth with its SPIFFE identity, not a secret; one preview supports part of it")
- [BI-FIND-2026-0686](https://insights.bostonidentity.com/ref/BI-FIND-2026-0686): NIST's National Cybersecurity Center of Excellence framed agent identity in February as a question of applying what exists, not inventing something new. Its concept paper lists OAuth, OpenID Connect, SPIFFE, SCIM, the NGAC access-control standard and MCP as candidates it is "currently considering", and names none of the agent-specific IETF work, such as ID-JAG, the WIMSE drafts or token exchange for agents. It keeps human delegation and logging in scope and leaves agents from outside the enterprise for a later effort. The next steps are a possible project description and a lab-built practice guide, with no date; the comment period closed on 2 April. (from "NIST's agent identity work starts from OAuth, SPIFFE and SCIM and defers agents from outside the enterprise")
- [BI-FIND-2023-0006](https://insights.bostonidentity.com/ref/BI-FIND-2023-0006): Uber ran standards-based workload identity at fleet scale well before it had an agent problem. The post puts SPIFFE and SPIRE under '4,500 services running on hundreds of thousands of hosts across four clouds', later 'over a quarter million nodes', with the team involved in SPIRE 'since the early stages of the project in mid-2018'. The reasons are the ones the IETF's architecture draft would later write down: perimeter trust fails for ephemeral workloads, and 'provider-specific identity solutions are a non-starter' across clouds. This is the deployment that was already in place when Uber's agent platform went live in 2025 and still found a delegation gap, which is the strongest evidence in the corpus that workload identity is necessary for agents and not sufficient. (from "Uber had workload identity on a quarter-million nodes two years before agents; certificates were the easy part")
- [BI-FIND-2026-0082](https://insights.bostonidentity.com/ref/BI-FIND-2026-0082): The agent identity gap is a delegation gap, and a mature zero-trust shop hits it just as hard as anyone. Uber already had workload identity on SPIFFE/SPIRE and a service mesh when its agent platform went live in early 2025, and still could not trace an automated pull request back to the on-call engineer who set the chain in motion, because each hop dropped the context of the one before. The post's observability screenshot then shows the same three-agent example as a real session trace with a user attached to every hop. The panels and papers we have covered say the same thing from the outside; this is the first account from inside a deployment. (from "Uber built the delegation chain the rest of the field calls unsolved")
- [BI-FIND-2026-0386](https://insights.bostonidentity.com/ref/BI-FIND-2026-0386): The IETF's workload name is a URI and almost nothing about it is fixed. It must be absolute with a non-empty authority, that authority is the trust domain and 'SHOULD be a fully qualified domain name belonging to the organization', and it 'MUST NOT contain a query component, a fragment component, user information, or a port component'. The scheme is not defined: SPIFFE's spiffe scheme fits, and the draft registers a new wimse scheme whose path 'is not interpreted by this specification'. Implementations must accept names up to 2,048 bytes. Section 1 says the document 'does not prescribe how identifiers are issued or verified', and a workload is defined as microservices, containers, virtual machines and serverless functions; AI agents are not mentioned. This is a syntax that lets existing SPIFFE names pass unchanged, with the organization's DNS name as the one load-bearing part. (from "The IETF names a workload by a web address on the organization's domain; the verifier's allowlist decides trust")
- [BI-FIND-2026-0408](https://insights.bostonidentity.com/ref/BI-FIND-2026-0408): The year drew a clearer line around what SCIM provisions, without settling how far it reaches. The working group's framing splits public agent identity from ephemeral workload identity, and the post leaves open whether SCIM should cover both or only the first. In WorkOS's phrasing, SCIM 'provisions the right to an identity, not the identity itself': it says which agents exist and whether they are still active, a standard like SPIFFE issues the credential after the workload proves what it is, and runtime authorization is left to OAuth 'by design, not by omission'. The SCIM working group's IETF 125 slides go further than the post: they propose that SCIM drive both OAuth client registration and SPIFFE registration entries through the same identity provider. We read this as meaning that deprovisioning an agent through SCIM ends its right to exist, and reaches its credentials only if the identity provider also wires SCIM to those registrations; running sessions keep their own expiry either way. (from "Three companies merged SCIM's two agent drafts, but no working group has taken it up and it expires in December")
- [BI-FIND-2026-0318](https://insights.bostonidentity.com/ref/BI-FIND-2026-0318): What the draft leaves out is most of what a security team would ask. How an authorization server comes to trust a SPIFFE trust domain is 'out of band' and out of scope. Its own security text is one rule against accepting a token just because its issuer's keys verify it; replay protection goes no further than an expiry check and a single-audience rule, key rotation is a recommendation to poll, and a compromised trust domain or SPIRE server is not discussed. It does not mention AI agents or delegation at all. It replaces the secret. Everything about what the authenticated workload may then do is someone else's document. (from "A draft lets a workload sign in to OAuth with its SPIFFE identity, not a secret; one preview supports part of it")
- [BI-FIND-2025-0057](https://insights.bostonidentity.com/ref/BI-FIND-2025-0057): The paper finds every existing way of identifying an agent as a client incomplete. Dynamic client registration 'creates a large number of anonymous clients'. Client ID Metadata Documents fix that and are 'still insufficient as a workload identity'. SPIFFE gives a strong workload identity that depends on controlling the infrastructure, so it does not cross into another organization. Vendor systems such as Microsoft Entra Agent ID and Okta's are named as proprietary, with limited interoperability. In the year since, the Model Context Protocol has made metadata documents its preferred method and an IETF draft has joined them to SPIFFE. (from "OAuth handles an agent in one company, working while you watch. The OpenID paper says that is where it stops.")

---

© 2026 Boston Identity LLC. All rights reserved. Published by Boston Identity LLC.
Quote up to 100 words with the credit "Boston Identity, IAM Insights" and a link to https://insights.bostonidentity.com/glossary/spiffe. Claim numbers may be cited freely. Training, fine-tuning and text-and-data-mining use of this page is permitted.
Terms: https://insights.bostonidentity.com/terms · How to cite: https://insights.bostonidentity.com/cite
