Learn · Standards
SPIFFE/SPIRE and the agentic identity gap
SPIFFE and SPIRE are excellent at what they do: giving a workload a verifiable identity. But an AI agent is not just a workload, it acts semi-autonomously, often on a person's behalf. That difference is where the gap opens, and where teams add a layer on top.
What SPIFFE/SPIRE give you
SPIFFE defines a standard for workload identity, the SPIFFE ID, and SPIRE issues and rotates expiring credentials (SVIDs) that let workloads prove who they are to each other, typically inside a service mesh. This solves a genuinely hard problem: workload-to-workload identity without shared secrets, with automatic rotation and attestation. If you run SPIRE, you already have strong, automatically rotated identity for your services. That foundation is worth keeping.
Where the agentic gap is
Workload identity answers "which workload is this?" An AI agent raises questions workload identity was never meant to answer. Who is the sponsor accountable for this agent? What task is it authorized to perform right now, and against which resources? Did a principal approve it before it started acting? Was this specific action, not just this workload, attributable and in-scope? A SPIFFE ID identifies the process; it does not carry a sponsor, a task-scoped authority, an enrollment approval, or a per-action operation proof. For an agent acting autonomously on someone's behalf, those are the things that make it governable.
SPIFFE tells you the workload is who it says it is. It does not tell you who stands behind the agent, what it is allowed to do today, or whether a principal signed off.
How teams fill the gap
The pattern that works is to keep SPIFFE/SPIRE as the workload-identity substrate and add an agentic identity layer beside it. The workload still gets its SPIFFE ID for mesh and workload trust. The agent also gets its own key, an enrollment approval by a person before it acts, and per-request operation proofs that make each action attributable. A sponsor recorded at enrollment, and identity tokens and boundaries scoped to a specific audience and task, complete the layer. You are not replacing SPIRE, you are giving the agent the approval, authority, and accountability that autonomous behavior demands. With Oathera, the key, the approval and the operation proofs are in place, authority is scoped to an audience and a task, and the sponsor who answers for the agent is recorded.
Oathera vs SPIFFE/SPIRE in one table
| SPIFFE/SPIRE | Oathera | |
|---|---|---|
| What it attests | The workload and node that are running | The agent's own key and host, and the person who approved it |
| Who answers | Not part of a SPIFFE ID | A verified principal, recorded at enrollment |
| Granularity | The workload's credential | A single-use proof over each operation and its arguments |
| Used together | A SPIRE-issued JWT-SVID can be optional enrollment evidence for an allow-listed trust domain. The identity stays the anchor key. | |
Putting it together
- Keep SPIRE for workload identity. Workloads keep their SPIFFE IDs for mesh and workload-to-workload trust.
- Add per-agent identity with an approval. Give each agent its own key and have a person approve it at enrollment; see making a named person accountable.
- Scope authority to the task. Define an operational boundary enforced per request.
- Attribute every action. Produce an operation proof for each request so each action is provable; see auditing agent actions.
Oathera adds the agentic layer: a per-agent anchor key bound to its host, enrollment approval by a principal through your identity provider, and an operation proof on every call. The Oathera Identity Service accepts a SPIRE-issued workload identity as extra evidence at enrollment; the agent's identity stays its anchor key. A signed task context scopes authority to a task, and the sponsor who answers for the agent is recorded. See integrations.
FAQ
Why isn't SPIFFE enough for AI agents?
SPIFFE and SPIRE attest which workload is running: the node and the workload. For an AI agent that acts for a person, that is necessary and not sufficient. It does not record which named person answers for the agent, what that person approved, or what each individual call was. Oathera records the accountable principal at enrollment, treats a SPIRE-issued JWT-SVID as optional enrollment evidence, and checks a single-use operation proof on every call.
SPIFFE and SPIRE give workloads an identity but I am not sure they cover the agentic use case where an agent acts autonomously on behalf of a user. What is missing and how do people fill the gap?
SPIFFE/SPIRE prove which workload is calling, with automatically rotated, expiring credentials, a strong substrate worth keeping. What they do not carry is an accountable person, authority approved before the agent acts, and per-action attribution. Teams fill the gap by keeping SPIRE for workload identity and adding an agentic layer beside it: give each agent its own key, have a person approve it at enrollment, check its calls at an enforcement point, and produce an operation proof for each action so it is attributable. With Oathera, the agent has its own key, a person's approval and an operation proof for each action. The Oathera Identity Service accepts a SPIRE-issued identity as enrollment evidence, a signed task context scopes authority, and the sponsor who answers for the agent is recorded.
Do I have to replace SPIRE to get agentic identity?
No. The agentic layer sits beside SPIFFE/SPIRE. The workload keeps its SPIFFE ID for mesh and workload trust. With Oathera, the agent gains its own key, enrollment approval by a principal and per-action operation proofs. A signed task context scopes authority, and the sponsor who answers for the agent is recorded.
What specifically does a SPIFFE ID not express for an agent?
It does not express who the accountable sponsor is, what task the agent is authorized for right now, whether a principal approved it, or whether a specific action was in scope and attributable. Those are properties of agentic identity, not workload identity.