Skip to content
IAM Insights

Explainers · Glossary

X.509

X509 · X.509 certificate · X.509 certificates

By Boston Identity · Explained · 6 min read

The short answer

X.509 is the standard format for a public-key certificate: a record, signed by a certification authority, that ties a public key to a named person, server or workload for a limited time.

What it is
A standard
Defined by
ITU-T X.509; IETF profile RFC 5280
Who it's for
Teams issuing identities to servers, workloads and agents
In our briefings
91By month of the source: 2025-12: 1, 2026-01: 1, 2026-02: 3, 2026-03: 3, 2026-04: 1, 2026-05: 4, 2026-06: 3, 2026-07: 8, 2026-08: 2, 2026-09: 6, 2026-10: 8, 2026-11: 11by month, last 12
01

What is X.509?

A public key is only useful if you know whose it is. X.509 answers that with a certificate: a data structure that binds a public key to a subject, the person or system that holds the matching private key.§3.1 A certification authority (CA) asserts the binding by signing the certificate.§3.1 Because anyone can check the signature and the dates, certificates can travel over untrusted networks and sit in unsecured storage.§3.1

The format comes from the International Telecommunication Union (ITU-T), which first published it in 1988; version 3 added extension fields and was completed in June 1996.§3.1 RFC 5280, from the Internet Engineering Task Force (IETF), is the profile that says how Internet software should use version 3 certificates and certificate revocation lists (CRLs).§1 It names web, email, user authentication and IPsec among the uses.§2

Every certificate carries the subject's and issuer's names, the subject's public key, a validity period, a version and a serial number.§4.1.2 Most also carry extensions, such as the subject alternative name, which binds a DNS name, IP address, email address or URI to the key.§4.2.1.6

X.509 is not a protocol for logging in or connecting. It is the certificate format; TLS, mutual TLS and SPIFFE are among the systems that carry and check X.509 certificates.

02

How does X.509 work?

Four parties take part: the subject that holds a key pair, the CA that signs, a repository that stores certificates and CRLs, and the relying party that wants to trust the subject's key.§3

Figure steps
  1. The subject registers with a CA
  2. Clients are loaded with trusted CA keys
  3. The CA signs the certificate
  4. The certificate is published
  5. The relying party builds a path
  6. The relying party checks signature, dates and status
Fig. 1

The CA's signature binds the subject's name to its public key, and the relying party trusts that binding only after chaining it back to a CA key it was loaded with and checking the latest revocation list.

Drawn from RFC 5280, sections 3 and 4.1

Swipe for the full figure →

  1. The subject registers with a CA

    The subject first makes itself known to a CA, either directly or through a registration authority (RA), a system the CA hands some management work to.§3, §3.5 The subject's client typically also needs its own key pair.§3.5

  2. Clients are loaded with trusted CA keys

    Before it can check anything, a client must be loaded with the public key of at least one CA it trusts.§3.5 A path starts from a CA in the user's own domain or from the top of a hierarchy, and a self-signed certificate is how such a starting key is conveyed.§3.2

  3. The CA signs the certificate

    The CA fills in the subject's name, public key, validity dates, a serial number unique to that CA, and any extensions, then signs the whole block.S1 By signing, the CA certifies the binding between the key and the subject.§4.1.1.3 Every part of a subject alternative name must be verified by the CA.§4.2.1.6

  4. The certificate is published

    The CA returns the certificate to the subject's system, posts it in a repository, or both.§3.5 Any means of distribution may be used; a directory is not required.§2.1

  5. The relying party builds a path

    A relying party usually needs a chain: the subject's certificate signed by one CA, plus zero or more certificates of CAs signed by other CAs, back to a key it already trusts.§3.2 It links each certificate to the next by matching the issuer name in one with the subject name in a CA certificate.§4.1.2.4 A key may sign certificates only if its certificate says it belongs to a CA.§4.2.1.9

  6. The relying party checks signature, dates and status

    The relying party checks the certificate's signature and validity period, then fetches a suitably recent CRL and confirms the serial number is not on it.§3.3 It must reject a certificate with a critical extension it does not recognise.§4.2 Online checking, such as the Online Certificate Status Protocol (OCSP), may stand in for CRLs.§3, §3.3

03

Why does X.509 matter now?

Guidance on agent security now names certificates directly. Anthropic's agent security guide asks for a cryptographic identifier for every agent instance, and its higher tiers add X.509 certificates with rotation and revocation, then mutual TLS.1 It also says static API keys are not acceptable even at its entry tier, and points to certificates or short-lived tokens bound to the agent.2

The IETF's workload identity drafts lean on the same format. The Workload Identity Certificate is an ordinary X.509 certificate with the workload's identifier in one URI subject alternative name, and its implementation section calls it compatible with the certificates SPIFFE deployments already issue.3 An agent-authentication draft lists an X.509 credential among its accepted formats and leaves the choice to each deployment.4

New drafts also try to load more into the certificate itself. One profile writes an agent's owner, trust level and capabilities into its certificate, valid for up to 365 days.5 Another draft argues the opposite, that capabilities and operator must never sit in the identifier.6 Which model a deployment picks decides whether a change of permissions means reissuing the agent's identity.

04

Where does it fit?

Compared withHow X.509 differs
SPIFFESPIFFE is a framework for handing identities to workloads; one of the forms it issues is an X.509 certificate with a spiffe URI as the subject.3 X.509 is the format, SPIFFE decides how workloads get one.
mTLSMutual TLS is the connection in which both sides present a certificate. The IETF's workload mutual TLS draft requires exactly one workload identifier URI subject alternative name, a path to a trust anchor configured for the trust domain, and a revocation check under the PKIX rules.7
JWTOne workload metadata draft carries attributes as claims inside a JSON Web Token (JWT) credential, but gives an X.509 certificate only an extension that points to a metadata endpoint.8
Token Status ListToken Status List is a revocation method for tokens, which the SD-JWT standard names only as an example.9 X.509 revokes certificates through a CA-signed CRL that names revoked certificates by serial number, or through an online service.§3.3
05

What goes wrong?

  • The CA's basis for signing can be thin. A CA may base the binding on a proof of possession, on presentation of the private key, or on the subject's own assertion.§3.1
  • Revocation lags. A CRL is reissued on a schedule, such as hourly, daily or weekly, so a revocation may not reach relying parties until the next one.§3.3 Online checking shortens the delay, but the relying party then has to trust the online service.§3.3
  • Unknown extensions can be skipped. A relying party may ignore a non-critical extension it does not recognise.§4.2 A draft agent profile marks its authority extension non-critical, so software that does not know it accepts the certificate and skips every limit in it.5
  • The CA's checks set the ceiling. The same profile says the issuing CA is not required to check whether the requested capabilities make sense.5 Another draft scores agents at an issuing CA that each operator typically runs for itself, and where neither the attestation nor the score comes from outside, we read that as operators grading their own agents.10
  • Attributes may belong elsewhere. RFC 5280 itself says that as tools such as attribute certificates emerge, it may be appropriate to limit the authenticated attributes in a certificate.§2
  • Certificates can leak what they contain. An ACME draft for device certificates warns that a hardware identifier in a certificate logged to certificate transparency becomes permanently public.11
  • Long lives need a plan for their end. When an issuer cannot keep status information until the expiry date, it must make sure no valid path to the certificate remains.§4.1.2.5
06

What should a security leader ask?

  1. 01

    Which CAs do our servers, workloads and agents trust as starting points, and who can add one?

  2. 02

    How long do our workload and agent certificates live, and how fast do they rotate?

  3. 03

    How do our relying parties check revocation, and how stale can a CRL or status answer be before they reject a certificate?

  4. 04

    Which non-critical extensions do we rely on for access decisions, and does every service that checks the certificate understand them?

  5. 05

    What does our issuing CA verify before it signs, and does anyone outside the team that runs the agents check it?

07

Sources

›Evidence: 11 claims from 11 briefings
  1. 1BI-FIND-2026-0596 · Anthropic asks for per-agent identity; its guide leaves Claude Code sub-agent credentials unspecifiedAnthropic requires a cryptographic identifier for each agent instance at its Foundation tier. "Every agent instance needs a unique, cryptographically rooted identifier that persists across its actions", and "Unique identifiers alone are a labeling exercise". Service tokens should be measured in minutes, and static API keys and shared service-account passwords "are no longer a legitimate entry point, not even at Foundation". Higher tiers add X.509 certificates with rotation and revocation, mutual TLS, then hardware-backed identity with remote attestation, and access control climbs from deny-by-default roles to per-action authorization with immediate revocation. The standards named are OAuth 2.0, X.509, mTLS, FIDO2 and OpenTelemetry; SPIFFE, WIMSE and token exchange do not appear.
  2. 2BI-FIND-2026-0542 · Anthropic says agents should never use static API keys, yet its sub-agents can carry the parent's permissionsAnthropic's guide raises the entry bar for an AI agent. Its framework has three cumulative tiers, Foundation, Enterprise and Advanced, with Foundation meant for small businesses and teams and Enterprise "where most organizations should aim". Even Foundation requires a persistent agent identity "backed by cryptographic material (not just labels)", OAuth 2.0 or similar tokens "with expiration measured in minutes", and no static API keys, embedded credentials or shared service-account passwords: "they are no longer a legitimate entry point", and existing ones should be treated as already compromised. "Static API keys are not acceptable for tool authentication, even at Foundation"; the guide's suggested route is certificates or short-lived tokens bound to the calling agent. The stated test for any control is whether it makes an attack impossible or only tedious, because AI-accelerated attackers will wait out friction.
  3. 3BI-FIND-2026-0375 · The IETF's workload credential binds one key to one name and says nothing else about the software holding itHalf 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.
  4. 4BI-FIND-2026-0179 · Six companies' agent-auth draft, since adopted by the WIMSE group, keeps credentials out of the model's reachThe draft's sharpest rule reads "The Large Language Model MUST NOT have access to an agent's credentials or to credentials that may be needed to access tools and services", which it says keeps prompt injection from getting the model to use, expose or disclose them. Around it sit the identity rules. An agent MUST be assigned exactly one WIMSE identifier and MUST hold credentials cryptographically bound to it; those credentials SHOULD be short-lived and MUST carry an explicit expiry, and static API keys are "an antipattern for agent identity". The draft names WIT, X.509 WIC and SPIFFE SVIDs as formats and leaves the choice to the deployment. Our briefing on Sierra's cloud agent platform found a similar boundary built in: a proxy approves each call and swaps in the credential, so the agent never holds it.
  5. 5BI-FIND-2026-0748 · Sharif's profile writes an AI agent's rights to pay and delete into an identity certificate valid up to a yearSharif's profile writes an agent's authority into its identity certificate: the owning organization, a trust level from L0 to L4 defined by the actions it allows (L3 may pay and transfer; L4 may deploy and delete, with human approval), a capability list, a delegation depth and a kill-switch URL, in a certificate that may last up to 365 days. The issuing CA checks that the request came from an authorized platform and that the organization controls its SPIFFE domain, but it is 'NOT required to validate the semantic correctness of the requested capabilities'. The extension must be marked non-critical, so any X.509 stack that does not know it accepts the certificate and skips every limit.
  6. 6BI-FIND-2026-0754 · Drake's case for an agent identity that outlives its keys and its operator, made without weighing OAuth, SPIFFE or X.509Two agent-identity drafts posted a week apart take opposite positions on what an identity should hold. Sharif's X.509 profile puts the owning organization, trust level and capabilities inside the agent's certificate; Drake's requirement R5 says trust tier, role, operator and capabilities must never be encoded into the identifier and belong in separate, changeable authorizations. Whichever model a deployment takes decides whether a change of operator or permissions means reissuing the agent's identity.
  7. 7BI-FIND-2026-0517 · WIMSE mutual TLS -03 ties certificate acceptance to trust-domain anchorsWIMSE mutual-TLS revision -03 requires a peer certificate to validate to a trust anchor configured for the trust domain in its workload identifier, and requires certificate revocation status to be determined under the referenced PKIX rules. The certificate must contain exactly one workload-identifier URI subject alternative name; zero or multiple such entries must be rejected. On a DNS-based connection, the client must also reject a missing or mismatching DNS identity even when workload-identifier validation succeeds. Authorization must retain the trust domain and the trust anchor rather than evaluate only an identifier path.
  8. 8BI-FIND-2026-1355 · An individual IETF draft takes a workload's role and group out of its name and puts them in separate metadataMetadata travels in one of two ways: as claims inside a JWT credential, or from an authenticated metadata endpoint. The draft defines no way to carry the attributes themselves in an X.509 certificate, only a non-critical extension pointing to that endpoint, and JWT credentials can carry the pointer as an optional metadata_uri claim. An endpoint configured out of band takes precedence over the pointer. When neither exists, a client may use a default /.well-known/workload-metadata address if its policy trusts that domain. The endpoint authenticates each caller and discloses claim by claim, so knowing a workload's identifier does not get you its metadata, and an omitted claim asserts nothing. A selected endpoint that fails MUST NOT trigger fallback to a lower-precedence one. If required metadata cannot be had from an acceptable source, access that depends on it MUST NOT be granted. A response is not a signed assertion meant for forwarding to another party; signed responses are one of the draft's open issues.
  9. 9BI-FIND-2025-0145 · The SD-JWT standard that agent drafts build on never mentions agents and leaves key binding to each verifierWhat RFC 9901 hands to the protocol or profile on top is, as we read it, most of what an agent deployment has to settle: how the holder's key pair is established (section 4.1.2), how the key-binding JWT's audience is represented and how its nonce is obtained (4.3), if and how consent to disclose is obtained (7.2), which validity claims a verifier must see, which application-specific profiles SHOULD list (9.7), and how verifiers get issuers' keys, which it does not define (9.8). It defines no status or revocation check for an issued SD-JWT; Token Status List appears only as an example of a revocation callback that tells the issuer little. In our briefings these gaps mostly carry forward: Verifiable Intent v0.1 and the Delegate SD-JWT draft define no revocation, and the SD-Card draft puts the registry that issues agent cards out of scope. Our briefing on SD-JWT VC found that it answers the issuer-key question with a well-known metadata document or an X.509 chain.
  10. 10BI-FIND-2026-1291 · An agent certificate draft ties access to a trust score set by the issuing CA, usually the agent operator's ownAPKI writes a trust score from 0 to 100 into each agent's certificate, and relying parties MUST reject a certificate scored below the minimum tier they set. The score comes from a Trust Score Computation Engine at the issuing CA, which the draft says is typically the intermediate CA that each organization running agents deploys for itself. The starting score adds fixed allowances (up to 30 points for attestation strength, 20 for organization reputation, 15 each for model provenance and code attestation, 20 for history), and relying parties' reports then move it by set ranges. The draft gives no basis for any of these numbers and leaves the reporting protocol to a companion specification. Against score inflation, behavioural signals MUST be authenticated with the reporting relying party's credentials, scores SHOULD draw on several independent sources and "no single relying party should be able to move a score by more than 15 points", and the CA MUST NOT issue a certificate scoring above the agent's historical peak minus any penalty history. Another organization MAY apply its own mapping to a partner's scores; the draft's example counts them 10 points lower. A separate field records how the agent's capabilities were attested, from self-declared through CA-verified and third-party to hardware-bound: relying parties requiring high assurance MUST require CA-verified or higher, and third-party attestation SHOULD be required for regulated uses such as financial services. CA-verified means the issuing CA tested the agent, and the draft describes third-party as an independent auditor's check. The draft answers a malicious operator with transparency logs, third-party attestation and federated trust with minimum score thresholds, and answers an insider with separation of duties between the CA operator and score computation; section 6.3 still places the score engine at the issuing CA. Where neither the attestation nor the score comes from outside, we read the score as the agent's operator grading its own agents.
  11. 11BI-FIND-2026-1052 · An ACME draft lets company CAs issue device certificates from the device's own proof, and each CA judges itAt -01, putting a device's identifiers in the certificate was already optional: a client MAY include the permanent identifier in its certificate request, a CA that wants only privacy-preserving certificates MAY reject requests that carry it, and a CA MAY leave the hardware-module identity out. By -10, posted in August 2026, the authors had turned the option into advice and a change to ACME itself. The draft now updates RFC 8555 so that, for these two identifier types, the certificate request SHOULD rather than MUST repeat the identifiers in the order. It tells implementers to treat leaving them out as the default unless there is an operational need to include them, warns that a hardware identifier in a certificate logged to certificate transparency becomes permanently public, and for workload mutual TLS advises preferring logical identifiers such as SPIFFE URIs, with the hardware attestation used only to bootstrap.

›In our briefings

What our briefings say about X.509 itself, with the most direct claims first.

  1. The core spec lists WIT as a third SVID format next to X.509 and JWT, and its text does not say what WIT is or that it is less settled than the other two. A commit on 1 July 2026 added WIT to that list, and the core file was marked Stable the same day. The separate WIT-SVID file in the repository, which we checked, is marked Incubating, while the X.509 and JWT files are marked Stable. The project's stability document says that at Incubating, breaking changes are avoided but "may be made in response to real-world implementation experience", and that features relying on such a spec are "typically gated behind a feature flag". The WIT-SVID file describes itself as a profile of the Workload Identity Token from the IETF's WIMSE working group.

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

  2. RFC 7517 gives a JWK four optional ways to tie itself to an X.509 certificate: a URL (x5u), the chain itself (x5c), or a SHA-1 or SHA-256 thumbprint (x5t, x5t#S256). For all four, the key in the certificate MUST match the JWK's public key, and any "use" or "alg" member MUST agree with the certificate. For x5u, the fetch MUST use TLS and the server's identity MUST be validated. Sections 4.6 to 4.9 do not tell the recipient to validate the certificate chain itself. That step appears in Section 9.1, which uses no normative keywords: if the application validates the certificate and checks that the JWK matches it, the key "can be associated with" the certificate's attributes, such as its subject name. Section 9.1 adds that in almost all cases applications decide whether to trust a key from attributes bound to it, such as names, roles and the key's origin. We read this as a format that keeps key and certificate consistent and leaves the trust decision to whoever uses the JWK.

    RFC 7517 makes a JWK agree with its certificate and leaves trusting the certificate to the applicationBI-FIND-2015-0032

  3. SD-JWT VC defines two ways for a verifier to find the issuer's key: a metadata document fetched from a well-known path under the issuer's HTTPS identifier, or an X.509 certificate chain in the credential's x5c header. Since revision 20 the draft says that chain is validated against a trust anchor that policy permits for that issuer, and revision 24 adds that a certificate is not a trust anchor merely because it is included in x5c. Other specifications or ecosystem rules may add mechanisms, and a verifier MUST ensure that for any given issuer an attacker cannot influence the type of verification process used. Decentralized identifiers (DIDs) appear nowhere in the body of the draft; the change log for revision 10 says a DID mechanism is still possible through a profile or extension, and the terms section sets the format apart from the W3C Verifiable Credentials Data Model. We read the IETF's credential format as anchoring issuer trust in the web's names and certificates.

    In SD-JWT VC, the X.509 key route does not authenticate the iss claimBI-FIND-2026-0636

›Cited in 91 briefings

Every briefing that discusses this term, newest first.

  1. In SD-JWT VC, the X.509 key route does not authenticate the iss claim

    Draft · · IETF Datatracker · Oliver Terbu et al. · Aug 31, 2026

  2. IETF draft: AI agents you need to audit or revoke separately should not share one identity

    Draft · · IETF Datatracker · Joseph A. Salowey et al. · Jul 6, 2026

  3. OAuth's token revocation list nears RFC, and a shared list hides which token is checked

    Draft · · IETF Datatracker · Tobias Looker et al. · Aug 13, 2026

  4. The attested-TLS draft drops cached verifier results, so the verifier now sits inside each handshake

    Draft · · IETF Datatracker · Thomas Fossati et al. · Oct 14, 2026

  5. 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

  6. An IETF draft puts TLS attestation after the handshake and bans session resumption; its formal analysis is unfinished

    Draft · · IETF Datatracker · Muhammad Usama Sardar et al. · Nov 2, 2026

  7. 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

  8. WIMSE's agent draft adds how an agent's access ends and where policy engines fit, without a new requirement

    Draft · · IETF WIMSE Working Group · Pieter Kasselman et al. · Sep 15, 2026

  9. 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

  10. An unadopted AGTP draft would let gateways refuse an agent's out-of-scope requests from its TLS certificate

    Draft · · IETF Datatracker · Chris Hood, Nomotic, Inc. · Oct 30, 2026

  11. 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

  12. WIMSE credentials -03: a valid signature proves trust-domain membership, not which workload is calling

    Draft · · IETF Datatracker · Brian Campbell et al. · Jul 2, 2026

  13. AGTP checks that an agent ID is signed; binding it to the connection is an add-on in the author's patent notice

    Draft · · IETF Datatracker · Chris Hood, Nomotic, Inc. · Jun 28, 2026

  14. Agent delegation records not anchored in trusted time become deniable once timestamps can be forged

    Draft · · IETF Datatracker · V.K. Uppalapati · Sep 29, 2026

  15. Drake's revised draft: an agent identity outlives its operator but is never reissued once its last key is gone

    Draft · · IETF Datatracker · Christopher Drake, 1id.com · Sep 25, 2026

  16. Attestation shows which image is running, not which copy; a new IETF draft weighs two ways to tell copies apart

    Draft · · IETF Datatracker · Tirumaleswar Reddy.K et al. · Oct 28, 2026

  17. The IETF names workloads with a URI on the owner's domain; revision -04 pins down how two names are compared

    Draft · · IETF Datatracker · Yaroslav Rosomakho et al. · Oct 23, 2026

  18. RFC 9943 makes a log prove who signed a statement, not that it is true or that nothing was left out

    Article · · IETF (RFC Editor) · Henk Birkholz et al. · Jun 30, 2026

  19. RATS wraps attestation messages in one envelope and requires composite evidence to be bound together

    Draft · · IETF Datatracker · Henk Birkholz et al. · Dec 11, 2025

  20. 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

  21. An individual IETF draft takes a workload's role and group out of its name and puts them in separate metadata

    Draft · · IETF Datatracker · Shlomo Zalman Heigh et al. · Oct 16, 2026

  22. 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

  23. The SD-JWT standard that agent drafts build on never mentions agents and leaves key binding to each verifier

    Article · · IETF (RFC Editor) · Daniel Fett et al. · Nov 20, 2025

  24. Anthropic asks for per-agent identity; its guide leaves Claude Code sub-agent credentials unspecified

    Article · · Anthropic (Claude) · Anthropic · May 27, 2026

  25. Anthropic says agents should never use static API keys, yet its sub-agents can carry the parent's permissions

    Article · · Anthropic · Anthropic · May 18, 2026

  26. Okta's expired SCIM agent draft recorded certificates and OAuth clients; the joint draft after it dropped both

    Draft · · IETF Datatracker · Macy Abbey et al. · Oct 16, 2025

  27. The signing-key draft under AAuth offers eight ways to trust a key, and only one says who the agent works for

    Draft · · IETF Datatracker · Dick Hardt et al. · Sep 13, 2026

  28. 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

  29. 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

  30. WIMSE mutual TLS -03 ties certificate acceptance to trust-domain anchors

    Draft · · IETF Datatracker · Joseph A. Salowey et al. · Jul 6, 2026

  31. A SCIM agent extension draft gives the agent five lifecycle states, a quarantine, and an archive it can never leave

    Draft · · IETF Datatracker · Saurabh Kushwaha, Oracle · Jul 27, 2026

  32. Okta's answer to agent sprawl: put the identity provider between every agent and every app

    Podcast · · Cloud Security Podcast · Who Governs Your AI Agents? Identity, Offboarding & Open Standards · Jul 2, 2026

  33. July TLS-attestation draft withdraws itself and leaves key safeguards outside the protocol

    Draft · · IETF Datatracker · Hannes Tschofenig et al. · Jul 23, 2026

  34. A preprint cuts off every sub-agent within about 40 seconds of its parent stopping, with no revocation server

    Paper · · arXiv · Saurabh Deochake, SentinelOne · May 20, 2026

  35. A proposed standard for agent authority advises against delegating it across company lines by default

    Paper · · arXiv · Partha Madhira · May 12, 2026

  36. An agent certificate draft ties access to a trust score set by the issuing CA, usually the agent operator's own

    Draft · · IETF Datatracker · Raza Sharif, CyberSecAI · Apr 10, 2026

  37. 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

  38. A cross-domain agent trust draft requires the call chain, then leaves its format to a version that never came

    Draft · · IETF Datatracker · Daniel King et al. · Mar 15, 2026

  39. An MCP signing draft shows a client who wrote a tool, and admits a poisoned tool can still be validly signed

    Draft · · IETF Datatracker · Raza Sharif, CyberSecAI · Mar 14, 2026

  40. A Huawei agent draft keeps one 'master agent' as gatekeeper and drops the line that had servers re-check it

    Draft · · IETF Datatracker · Yuan Ni et al. · Feb 28, 2026

  41. 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

  42. IETF draft bars CAs from using attestation as proof about a key without a validated binding

    Draft · · IETF Datatracker · Mike Ounsworth et al. · Feb 11, 2026

  43. ACME's device-attestation draft now advises leaving device IDs out of certificates and drops a key-export rule

    Draft · · IETF Datatracker · Brandon Weeks et al. · Jan 29, 2026

  44. SIG Auth's storage-token fix needs driver changes

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

  45. Uber reports authorizing over 2 million service-to-service connections a second after staged rollout

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

  46. State Farm moved SPIRE from many token issuers to one, then hit an AWS key quota and a 15-character name limit

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

  47. 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

  48. A 2025 draft would map attestation results to the business terms that access policies use

    Draft · · IETF Datatracker · Mark Novak et al. · Nov 5, 2025

  49. Credential wallet draft makes holder binding a MUST; its own SD-JWT profile names no way to provide it

    Draft · · IETF Datatracker · Leif Johansson et al. · Nov 4, 2025

  50. AAGATE maps NIST's AI risk framework onto Kubernetes, and its paper never times the 'millisecond kill switch'

    Paper · · arXiv · Ken Huang et al. · Oct 29, 2025

  51. Attested workload identities need a mapping that survives authorized updates

    Draft · · IETF Datatracker · Mark Novak et al. · Oct 20, 2025

  52. WIMSE leaves its application proof choice open, with different integrity coverage

    Draft · · IETF Datatracker · Brian Campbell et al. · Oct 16, 2025

  53. An October SCIM draft gives agents their own records, with security still unfinished

    Draft · · IETF Datatracker · Macy Abbey et al. · Oct 11, 2025

  54. IETF HSM evidence draft: a device may call a key device-bound only if no route, now or later, can export it

    Draft · · IETF Datatracker · Jean-Pierre Fiset et al. · Oct 10, 2025

  55. SPIFFE can authenticate an OAuth client; trust and registration still come first

    Draft · · IETF Datatracker · Arndt Schwenkschuster et al. · Oct 3, 2025

  56. OpenID's credential issuance standard is OAuth for wallets, and its recommended wallet check is built for native apps

    Article · · OpenID Foundation · Torsten Lodderstedt et al. · Sep 16, 2025

  57. CAEP 1.0 tells apps what changed after login and leaves almost every response to the receiver

    Article · · OpenID Foundation · Tim Cappalli et al. · Aug 29, 2025

  58. Auth0's DPoP explainer leaves out the access-token hash that RFC 9449 requires on every API call

    Article · · Auth0 Blog · Andrea Chiarelli · Aug 25, 2025

  59. Attestation-key EKU draft makes the CA ensure only the Attester controls the key

    Draft · · IETF Datatracker · Jean-Pierre Fiset et al. · Aug 5, 2025

  60. CMP adds KEM authentication with fresh secrets for each certificate-management operation

    Article · · RFC Editor · Hendrik Brockhaus et al. · Jul 29, 2025

  61. OpenID4VP 1.0 makes verifiers re-check what a wallet returns, and cannot show a holder acting for someone else

    Article · · OpenID Foundation · Oliver Terbu et al. · Jul 9, 2025

  62. Arm's PSA attestation RFC trusts two device states, and its Table 1 labels one as root-of-trust debug

    Article · · RFC Editor · Hannes Tschofenig et al. · Jun 13, 2025

  63. A Cloud Security Alliance paper wants AI agents on a new identity stack, with OAuth kept for simple cases

    Paper · · arXiv (cs.CR preprint 2505.19301) / Cloud Security Alliance · Ken Huang et al. · May 25, 2025

  64. W3C Data Integrity proofs name their purpose, so a verifier can refuse a credential signature offered as a login

    Article · · W3C · Manu Sporny et al. · May 15, 2025

  65. The first Agent Name Service paper puts capabilities in the name and leaves protocol translation and governance out

    Paper · · arXiv (cs.CR preprint 2505.10609) / OWASP Agentic Security Initiative · Ken Huang et al. · May 15, 2025

  66. The W3C credential standard leaves out what agents need most: which issuers to trust, and who may present

    Article · · W3C · Manu Sporny et al. · May 15, 2025

  67. SAGA meters agent-to-agent contact through one registry; its speed and 300-million-agent figures are modelled

    Paper · · arXiv · Georgios Syros et al. · Apr 27, 2025

  68. RFC 9700 bans OAuth's password grant and loose redirect matching; binding access tokens stays a SHOULD

    Article · · IETF (RFC Editor) · Torsten Lodderstedt et al. · Jan 2025

  69. RFC 9679 lets a CBOR token name its holder's key by thumbprint alone, and leaves finding the key to the verifier

    Article · · RFC Editor · Kohei Isobe et al. · Dec 20, 2024

  70. In GNAP (RFC 9635), a client is known by its key, and tokens stay key-bound unless the server flags them bearer

    Article · · RFC Editor · Justin Richer et al. · Oct 1, 2024

  71. Lockstep’s 2023 wallet proposal puts credential acceptance outside the wallet

    Video · · Identiverse - A CRA Resource · Uploaded June 17, 2024; talk recorded May 31, 2023

  72. The 2024 'IDs for AI' paper puts the ID on a chat session, not a model, and leaves trust in its issuer to others

    Paper · · arXiv · Alan Chan et al. · Jun 17, 2024

  73. In March 2024 ENISA found deepfake injection leading attacks on ID proofing, with no agreed standard to detect it

    Article · · ENISA · Evgenia Nikolouzou et al. · Mar 12, 2024

  74. TLS clients must match a service they chose independently of the certificate

    Article · · RFC Editor · Peter Saint-Andre et al. · Nov 8, 2023

  75. COSE certificate headers leave trust validation with the relying application

    Article · · RFC Editor · Jim Schaad · Feb 16, 2023

  76. RATS keeps device-state appraisal separate from the decision to grant access

    Article · · RFC Editor · Henk Birkholz et al. · Jan 2023

  77. RFC 9053 allows identity inputs in COSE key derivation to be omitted

    Article · · IETF / RFC Editor · Jim Schaad · Aug 1, 2022

  78. Certificate Transparency 2.0 lets clients refuse unlogged certificates and leaves logged misissued ones for monitors to find

    Article · · RFC Editor · Ben Laurie et al. · Dec 1, 2021

  79. NIST's 2020 zero trust model named AI agents that manage security and left their authentication open

    Article · · NIST · Scott Rose et al. · Aug 11, 2020

  80. RFC 8705 lets OAuth bind tokens to a client certificate, and leaves the proxy in front of the API to the deployer

    Article · · RFC Editor · Brian Campbell et al. · Feb 28, 2020

  81. A 2020 simulation fit the web's certificate revocations in under 5 MB; OAuth's Token Status List draft cites it

    Article · · NDSS Symposium 2020 · Trevor Smith et al. · Feb 12, 2020

  82. TLS 1.3 requires applications to choose which early data is safe to replay

    Article · · RFC Editor · Eric Rescorla, Mozilla · Aug 10, 2018

  83. SCIM leaves the meaning of active status and group access to each provider

    Article · · RFC Editor / IETF · Phil Hunt et al. · Sep 1, 2015

  84. A JWK thumbprint identifies a known key, and RFC 7638 warns it cannot reliably block one

    Article · · RFC Editor · Michael B. Jones et al. · Sep 1, 2015

  85. RFC 7522 lets a SAML assertion serve as a grant or authenticate the client independently

    Article · · IETF / RFC Editor · Brian Campbell et al. · May 1, 2015

  86. JWE’s JSON headers can sit outside integrity protection

    Article · · Michael B. Jones et al. · May 1, 2015

  87. RFC 7517 makes a JWK agree with its certificate and leaves trusting the certificate to the application

    Article · · RFC Editor · Michael B. Jones, Microsoft · May 1, 2015

  88. RFC 7515 lets a signed JSON object name or carry its own key, and leaves trusting that key to the application

    Article · · RFC Editor · Michael B. Jones et al. · May 1, 2015

  89. RFC 5280 takes the trust anchor as input before checking a certificate path

    Article · · David Cooper et al. · May 1, 2008

  90. A 2025 workload identity draft kept credential exchange for crossing trust domains, and never to gain more trust

    Draft · · IETF Datatracker · Arndt Schwenkschuster, Defakto · Mar 3, 2025

  91. Microsoft's 2023 keynote: workload standards should carry identity across service calls first, policy later

    Video · · Identiverse - A CRA Resource · Recorded May 31, 2023 · Uploaded June 17, 2024

Related terms

What appears alongside X.509 in the same briefings.

X.509 PKI Certificate and CRL Profile (RFC 5280)SPIFFEmTLSJWTJavaScript Object Notation (JSON)RATSHTTPJOSE

Was this explainer useful?

Share this explainer

Every finding, forecast and open question on this site has a permanent ID. If we reword one, its ID stays the same, so a citation keeps pointing to the same claim.

Follow us on LinkedInRSS feed

Working on an identity problem that involves X.509? Talk to Boston Identity