Learn · Standards
Standards map for AI agent identity: what Oathera uses, and what it does not
This page lists which standards and frameworks Oathera uses, which it works alongside and which it does not use. It exists so that an answer to 'does it support X?' can be exact. Naming a standard here is not a claim of certification or conformance.
In use
- OIDC with PKCE for the principal's approval at your identity provider.
- JWT and JWS with EdDSA for identity tokens, key-bindings, operation proofs and decisions.
- RFC 7800 confirmation claims, so a token names its session key.
- RFC 7638 key thumbprints, the basis of the key digest.
- RFC 9421 HTTP message signatures for Oathera's own HTTP calls.
- W3C Verifiable Credentials 1.1 from the credential service.
- SCIM, and Shared Signals (SSF and CAEP) for departures and for agent revoked, suspended and host-changed events.
- OWASP NHI Top 10 questions at enrollment, self-reported.
Alongside
- SPIFFE and SPIRE. A SPIRE-issued JWT-SVID can be optional enrollment evidence for an allow-listed trust domain. The identity stays the anchor key. See SPIFFE/SPIRE and the agentic identity gap.
- Microsoft Entra. Federation turns an agent's Oathera identity into a token Entra accepts.
- OAuth 2.1. Works beside it for client authorization. Oathera adds per-agent proof.
- A policy engine. Policy engines such as Open Policy Agent can decide on the verified facts Oathera provides. Oathera Agent Enforcement runs its own rules, watch first, then enforce.
Not used
- DPoP. The operation proof plays that role, and also covers arguments.
- mTLS binding of tokens. Binding is by the anchor key and the session key.
- RFC 8693 token exchange as the mechanism. Federation to Entra issues a token Entra accepts.
Frameworks to read
The OWASP Top 10 for Agentic Applications names identity and privilege abuse among its risks. The NIST National Cybersecurity Center of Excellence has a project on software and AI agent identity and authorization. Oathera makes no claim of conformance to either.
How Oathera helps
Oathera builds on these standards where it can and says plainly where it does not. Decentralized identifiers are not part of how Oathera names an agent: the identity is the key digest of the anchor key.
Oathera does not verify people, judge model output, inspect or rewrite prompts, or replace your identity provider. Your identity provider and proofing sources do the first; Oathera is the layer under them for agents.
FAQ
Does Oathera use DPoP?
No. The single-use operation proof plays that role for each call and also covers its arguments.
Does Oathera support SPIFFE?
A SPIRE-issued JWT-SVID can be optional enrollment evidence. The agent's identity is still its anchor key.
Does Oathera use OAuth 2.1?
It works beside OAuth 2.1 and adds per-agent proof. It federates with Microsoft Entra.
Is Oathera certified to any standard?
No claim of certification or conformance is made here.
Related: Proof of possession for AI agents · SPIFFE/SPIRE and the agentic identity gap · What is agentic identity?
Become a design partner Watch the simulator More guides
← Back to Learn