# What is WIMSE?

> WIMSE is an IETF working group, and its architecture draft, for how software services prove who they are to each other with key-bound credentials and carry each request's security context across gateways and trust domains.

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

- What it is: architecture
- Defined by: IETF WIMSE working group, architecture draft -08 (Informational)
- Who it's for: Teams securing service-to-service and agent traffic

## What is WIMSE?

WIMSE stands for Workload Identity in Multi System Environments. It is an Internet Engineering Task Force (IETF) working group, and its architecture document is a draft, not yet a standard: revision -08, published 6 July 2026, with an intended status of Informational [S1]. A workload, in the draft's terms, is software that runs for a specific purpose, such as a microservice, a container, a virtual machine or a serverless function [S1 §2].

When one workload calls another, the receiver needs to know which workload is calling. Often it also needs the security context of the request: who the user is, or what processing has already happened [S1 §2, §3.4.6]. The draft builds its answer from three parts: a trust domain, a workload identifier and identity credentials [S1 §3.1].

A trust domain is a group of systems that share one set of security controls and policies, and it should be named by a domain name the organization owns [S1 §3.1.1]. The credential is either an X.509 certificate or a JSON Web Token (JWT) called a Workload Identity Token (WIT). Each comes paired with a private key that is kept secret and used only to prove the presenter holds the credential [S1 §3.1.3]. Deployments may also use plain bearer tokens, which work for whoever holds them, to interoperate with older systems that cannot handle key-bound credentials [S1 §2].

Think of it like this: Think of staff badges in an office building: security issues each badge, it names one person, and doors decide for themselves whether that person may enter. The comparison stops at lending, because a badge can be handed over, while a key-bound WIMSE credential is useless to anyone who lacks the matching private key, which is kept secret [S1 §3.1.3].

Not the same as: Not the same as SPIFFE, whose deployments have issued workload certificates for years [BI-FIND-2026-0375](https://insights.bostonidentity.com/ref/BI-FIND-2026-0375). The WIMSE architecture names the SPIFFE identifier only as one example of a format that fits its rules [S1 §3.1.2].

## How does WIMSE work?

The draft explains itself through example deployments. We follow one request through them: an outside client, a gateway at the edge of the trust domain, a credential and token service, two internal workloads, and a service in another trust domain [S1 §3.2].

[Figure: Each workload gets a key-bound credential first; the gateway then trades the client's access token for a context token that travels with the request, and Workload 2 swaps its credential for an access token before calling another trust domain.]

1. **The credential service equips each workload.** Early in its life, each workload typically gets its identity credential from a credential service tied to its trust domain [S1 §3.2.1]. The credential carries a workload identifier, a name that is unique inside that trust domain [S1 §3.1.2]. The draft leaves the delivery method open: direct provisioning, a bootstrap credential, attestation (evidence about the platform the workload runs on), or a helper agent on the same host [S1 §3.4.1].
2. **The client sends its request to the gateway.** An outside client sends a request to the gateway over HTTPS [S1 §3.2.2]. The client may prove who it is with mutual TLS, where both sides present certificates, or with a credential such as an OAuth access token obtained earlier [S1 §3.2.2].
3. **The gateway gets a context token.** The gateway asks a token service for a security context token, which holds information about whoever is accessing the system [S1 §3.2.2]. One way to do this is to send the client's access token to a token exchange endpoint. The context usually matters only inside the system, so it is not returned to the client [S1 §3.2.2].
4. **The gateway forwards context, not the access token.** The gateway passes the request and the context token to the right workload [S1 §3.2.2]. The client's access token is not usually forwarded, because it is meant only for external access. The workload uses the context in its authorization policy, and it denies requests that rely on the context if no context token arrives [S1 §3.2.2].
5. **Workload 1 calls Workload 2 and proves who it is.** When Workload 1 needs Workload 2, it sends the context along [S1 §3.2.2]. Workload 2 may have a policy requiring Workload 1 to authenticate [S1 §3.2.2]. Workload 1 can do so with its credential, for example through mutual TLS or with a Workload Identity Token plus proof that it holds the private key [S1 §3.3]. Workload 2 then makes a separate authorization decision, and the component enforcing it may consult a policy decision point [S1 §3.3].
6. **Workload 2 trades its credential to leave the trust domain.** If Workload 2 needs a service in another trust domain, it first authenticates to the token service with its workload credential and gets a token it can use outside [S1 §3.2.3]. It uses that token to obtain an access token for the external service, then presents the access token to that service [S1 §3.2.3].

## Why does WIMSE matter now?

A new framework for agent identity puts WIMSE at its base. Engineers from six companies, among them AWS, OpenAI, Okta and Ping Identity, wrote a framework in which an agent is a workload with a WIMSE identifier that gets access through OAuth 2.0 [BI-FIND-2026-0178](https://insights.bostonidentity.com/ref/BI-FIND-2026-0178). The WIMSE working group adopted that draft on 9 September 2026, and it continues as draft-ietf-wimse-aims-00 [BI-FIND-2026-0178](https://insights.bostonidentity.com/ref/BI-FIND-2026-0178). A survey of ten standards documents for agent identity graded only WIMSE with SPIFFE as available for production, though the grades are the authors' own judgement [BI-FIND-2026-0643](https://insights.bostonidentity.com/ref/BI-FIND-2026-0643).

Readiness is uneven. By the implementers' own reports, the certificate form of the WIMSE credential is in production at SPIFFE, Defakto Security and Teleport, while the token form is at beta, alpha and research status at those same three [BI-FIND-2026-0375](https://insights.bostonidentity.com/ref/BI-FIND-2026-0375). Uber, which built its own delegation chain, tracks the working group for alignment rather than running its drafts [BI-FIND-2026-0085](https://insights.bostonidentity.com/ref/BI-FIND-2026-0085). Across vendors, agent identifiers remain split between JWT-based schemes, workload-identity standards and proprietary formats [BI-FIND-2026-0020](https://insights.bostonidentity.com/ref/BI-FIND-2026-0020).

The architecture treats an AI agent as a delegated workload, not a new kind of identity [BI-FIND-2026-0298](https://insights.bostonidentity.com/ref/BI-FIND-2026-0298). For agents calling agents it says each hop must scope and re-bind the security context, a rule stronger than OAuth token exchange, which leaves narrowing to the server [BI-FIND-2026-0299](https://insights.bostonidentity.com/ref/BI-FIND-2026-0299).

## Where does it fit?

- Compared with SPIFFE: SPIFFE deployments already issue workload certificates. In WIMSE, a SPIFFE identifier is one example of a format that fits the identifier rules [S1 §3.1.2], and the WIMSE certificate is compatible with SPIFFE's X.509 identity document [BI-FIND-2026-0375](https://insights.bostonidentity.com/ref/BI-FIND-2026-0375).
- Compared with Transaction Tokens: A transaction token carries one request's context between internal services. WIMSE allows context to travel as a transaction token, one option among several [S1 §2, §3.2.2], and the transaction-token draft leaves the workload's own authentication to WIMSE mechanisms [BI-FIND-2026-0173](https://insights.bostonidentity.com/ref/BI-FIND-2026-0173).
- Compared with OAuth Token Exchange: OAuth Token Exchange (RFC 8693) trades one token for another. The WIMSE architecture points to it when a workload must act for someone else: the workload authenticates to a token service and receives a token for delegation or impersonation [S1 §3.4.7].
- Compared with WIMSE Workload Proof Token: The Workload Proof Token is one WIMSE mechanism, not the architecture. It is a signed JWT that proves the caller holds the key in its credential [BI-FIND-2026-0378](https://insights.bostonidentity.com/ref/BI-FIND-2026-0378).

## What goes wrong?

- Authentication is not authorization. A valid credential shows the workload controls the key and was issued under a trusted authority; it does not mean the workload may reach every resource in its trust domain [S1 §4.5].
- Gateways blur who is calling. TLS protects traffic only between each adjacent pair of endpoints, so a destination must not assume that an identity an intermediary authenticated is the caller's, unless protocol or policy establishes that link [S1 §4.1, §3.4.3].
- Bearer tokens leak. A bearer credential exposed in traffic or logs can let an attacker impersonate a workload or move laterally; key-bound credentials are typically less exposed because the key is not disclosed [S1 §4.4].
- Logs can leak secrets. The draft says each authenticated request must leave a verifiable trace, and audit logs must not contain secrets such as bearer tokens or private keys [S1 §3.4.5].
- Revocation is weak. The WIMSE credentials draft says JWT credentials are not generally revocable on demand, so short expiry is the main defence for a stolen token and key [BI-FIND-2026-0377](https://insights.bostonidentity.com/ref/BI-FIND-2026-0377).
- Some parts are unfinished. The cross-boundary section still carries a to-do note about aligning with OAuth's cross-domain work [S1 §3.4.10]. The two protections the draft names for agent chains, cryptographic binding of delegation tokens and attestation of what an intermediary did, are mentioned but not specified [BI-FIND-2026-0299](https://insights.bostonidentity.com/ref/BI-FIND-2026-0299).

## What should a security leader ask?

1. Which of our services still authenticate to each other with bearer tokens or static API keys, and what would it take to bind them to keys?
2. Where do our gateways, load balancers or service meshes end TLS, and how does the receiving service learn who the original caller was?
3. When one of our agents calls another agent or service, which component narrows its authority at that hop, and where is that recorded?
4. How fast can we stop accepting a stolen workload token, given that JWT credentials are not generally revocable on demand?
5. Does our vendor support the WIMSE token form in production, or only the certificate form?

## Sources

- [S1] [Workload Identity in a Multi System Environment (WIMSE) Architecture](https://datatracker.ietf.org/doc/html/draft-ietf-wimse-arch) (IETF WIMSE working group, Internet-Draft draft-ietf-wimse-arch-08, 6 July 2026, intended status Informational)

## Evidence

- [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-0178](https://insights.bostonidentity.com/ref/BI-FIND-2026-0178): Engineers from six companies, Defakto Security, AWS, Zscaler, Ping Identity, OpenAI and Okta, wrote a draft that opens by saying many agent authentication efforts "develop solutions in isolation, often reinventing existing mechanisms unaware of applicable prior art". It answers with a framework of existing standards and no new protocols: an agent is a workload with a WIMSE identifier that gets access through OAuth 2.0, and revocation and risk signals travel over the OpenID Shared Signals Framework. It still sets requirements of its own, such as the rule keeping the language model away from credentials, and says a framework like this helps find the gaps where extensions or profiles of existing standards are needed. The IETF datatracker records the WIMSE working group adopting the draft on 9 September 2026. It continues as draft-ietf-wimse-aims-00, posted on 15 September with the same six authors. (from "Six companies' agent-auth draft, since adopted by the WIMSE group, keeps credentials out of the model's reach")
- [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-0085](https://insights.bostonidentity.com/ref/BI-FIND-2026-0085): The practitioner who built this says the standards are not ready to implement as written. Uber's exchange is 'conceptually based on' RFC 8693 and customized for its own auditing, and it names the IETF WIMSE working group and an individual draft on agent authentication as things it tracks for alignment rather than things it runs. The delegation-chain shape a large deployment needs is ahead of what the standards bodies have adopted. (from "Uber built the delegation chain the rest of the field calls unsolved")
- [BI-FIND-2026-0020](https://insights.bostonidentity.com/ref/BI-FIND-2026-0020): Agent identifier standards are fragmented: schemes based on JSON Web Tokens (JWTs), the workload-identity standards SPIFFE and WIMSE, and proprietary formats, with no convergence across providers. Practitioners name interoperability as the gating factor and compare the moment to the early divergence of multi-cloud. (from "Give every AI agent a stable identifier the day it is created, then start with one team and one use case")
- [BI-FIND-2026-0298](https://insights.bostonidentity.com/ref/BI-FIND-2026-0298): The IETF's workload-identity architecture does not give AI agents an identity type of their own. Its one passage on them says 'AI intermediaries are a special case of delegated workloads': an agent is software that inherits the security context of whoever called it and SHOULD pass that context on unless it has been authorized to reduce it. The one line it draws is between acting for someone and acting alone. Actions an agent takes that cannot be attributed to a principal MUST be clearly distinguished from delegated ones, for example with a separate workload identity or different token scopes. Vendors argue over whether agents are a third kind of identity; the standards text treats them as workloads with a caller. (from "The IETF's workload-identity architecture gives AI agents one subsection, calling an agent a delegated workload")
- [BI-FIND-2026-0299](https://insights.bostonidentity.com/ref/BI-FIND-2026-0299): For agents calling agents, the draft states the rule the rest of the field has been circling: 'each hop in the chain MUST explicitly scope and re-bind the security context', because otherwise a chain can extend authority well beyond what was granted. That is stronger than the OAuth token exchange standard, which leaves narrowing to the server's discretion. It is also only a requirement on paper. The document is informational, and the two protections it names, cryptographic binding of delegation tokens and attestation of what an intermediary did, are mentioned and not specified. (from "The IETF's workload-identity architecture gives AI agents one subsection, calling an agent a delegated workload")
- [BI-FIND-2026-0173](https://insights.bostonidentity.com/ref/BI-FIND-2026-0173): The draft keeps context and credential apart on purpose. A transaction token 'MUST NOT' be used by a workload to authenticate itself, 'MUST NOT' be used as an OAuth access token, must never carry an access token inside it, travels in its own header because the Authorization header 'may be used by the workloads for other purposes', and must not be logged verbatim because its request context can hold personal data such as the caller's IP address. Workload authentication is left to the WIMSE mechanisms. That is the opposite bet from the agentic JWT proposal, which binds an agent's intent into the access token itself. If the OAuth group's design holds, an agent's task description rides beside the credential in a second token, and any product that stuffs intent into the bearer token is off the standards track. (from "OAuth's transaction token goes unchanged down a service chain and names who started it, not who acted in between")
- [BI-FIND-2026-0378](https://insights.bostonidentity.com/ref/BI-FIND-2026-0378): A Workload Proof Token proves that the caller holds the key in its credential, and that is the limit of what it proves. The signed JWT carries the target URL as audience (query and fragment stripped), a hash of the workload's identity token, and hashes of any transaction token or other token in the request; it does not cover the HTTP method, the path beyond the audience, headers or the body. Section 3.3 states the consequence without softening it: the proof 'does not protect major portions of the request and response and therefore does not provide protection from an actively malicious middle box'. A workload that chooses this proof over the HTTP message-signature profile is trusting every proxy between it and the recipient with the content of the call. (from "The IETF's simplest workload proof proves the key and leaves the request unprotected, and the draft says so itself")
- [BI-FIND-2026-0377](https://insights.bostonidentity.com/ref/BI-FIND-2026-0377): The draft defines no way for a verifier to find out who to trust. Trust anchors belong to a trust domain and 'MUST be distributed out of band'; section 3 says the issuer claim 'MUST NOT be used to look up trust anchor material directly from information carried only in the token', which closes the key-fetch-by-URL shortcut OpenID Connect relies on. Federation between trust domains is not mentioned. Revocation is not solved either: section 9.2.1 states that JWT credentials 'are not generally revocable on demand', so a short expiry is 'the primary mitigation' for a stolen token and key. Sections 3 and 4 are new in this revision, so the working group added the out-of-band rule on purpose rather than leaving it unsaid. (from "The IETF's workload credential binds one key to one name and says nothing else about the software holding it")

---

© 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/wimse. 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
