NIST SP 800-63
NIST 800-63 · Digital Identity Guidelines
NIST's Digital Identity Guidelines: originally federal e-authentication rules that became the de facto benchmark for identity-proofing and authentication assurance levels well beyond government procurement.
In our briefings
The claim each of the newest briefings on NIST SP 800-63 would have you leave with.
Asked which identity and security controls are most likely to break first as agentic systems scale, John Yeoh, CSA's chief scientific officer, names lifecycle management. He cites CircleCI and Microsoft's Midnight Blizzard breach as poor lifecycle management of non-human identities, where keys for secrets were not rotated fast enough, and expects agents to fail faster because people now give them specs that spin up sub-agents. Access reviews that ignore intent and behaviour come next, then logging, in what he calls "a good domino of control collapse". Aizome's Amir Ofek answers the same question differently: applying controls built for non-human identities, which are deterministic rather than dynamic, is what will break first.
CSA's John Yeoh expects lifecycle management to be the first agent control to breakBI-FIND-2026-0113
Revision -02 reverses the draft's rule on which agents count when a service admits a call. Revision -01 had the Serving Party check the principal and every actor in the delegation chain, which it said went beyond RFC 8693 token exchange, where earlier actors are informational only. Now the service checks the principal and the current actor, the agent making the call. Earlier actors named in nested act (actor) claims "are informational only, are recorded in actor_chain as audit history, and MUST NOT be used to decide admission," which the draft says Section 4.1 of RFC 8693 requires. The authors call the chain "attribution, not authority": the token issuer's asserted history, which is not complete and is no evidence that any hop held or narrowed authority. They concede that a Serving Party cannot refuse a call because an earlier actor was suspended; linked verification shows after the fact that the work continued. Admission on the whole actor history is an open issue, proposed for discussion at IETF 127 and not defined in the draft. Nor can the receipts show mechanically that authority narrowed at each hop: that would need a common way to represent scopes, another open issue, and the draft defines no mechanism for carrying authority across hops, pointing instead to delegation-chain mechanisms such as the OAuth identity-chaining draft.
Agent-audit draft now admits a call on the principal and the current agent, as RFC 8693 requiresBI-FIND-2026-2152
ChainIT's protocol ties each payment's policy decision, budget reservation and single-use execution credential to one canonical transaction digest: a hash over every material field of the instruction that will actually be transmitted. Inside the band an agent's grant allows (in the paper's invented example, approved cloud-services vendors up to $5,000 per transaction and $25,000 a month), the deterministic control plane decides with no human involved. Past the step-up boundary, such as a new payee, a changed destination or a higher value, a person with independent authority must approve that exact digest; in the authors' words, "the approver approves a digest, not a screen." Either way, the adapter at the payment rail "must reconstruct the canonical transaction digest from the rail instruction" and check it against the policy decision, the reservation and any approvals before it consumes the credential, before or atomically with submission. A beneficiary account changed after approval gives a different digest, so the existing approvals no longer apply. The authors describe this as the EU's dynamic-linking rule for strong customer authentication extended from amount and payee to every field, and say it shares the goals of transaction binding and single use with Lan et al.'s addition to Google's AP2.
ChainIT's design has the payment rail rebuild each payment's hash before money moves; the paper reports no testBI-FIND-2026-1374
›Cited in 16 briefings
Every briefing that discusses this term, newest first.
- CSA's John Yeoh expects lifecycle management to be the first agent control to break
Podcast · · The Non-Human & AI Identity Podcast · NHI & AI Identity Summit : The Next 24 Months · Sep 7, 2026
- Agent-audit draft now admits a call on the principal and the current agent, as RFC 8693 requires
Draft · · IETF Datatracker · Shameer Thaha et al. · Oct 19, 2026
- ChainIT's design has the payment rail rebuild each payment's hash before money moves; the paper reports no test
Paper · · arXiv · Jeremy Blackburn et al. · Oct 16, 2026
- Eve Maler says the push to give every AI agent a responsible human misses agents a company does not own
Podcast · · Identity at the Center · #453 - Treating Identity Like a Product with Eve Maler · Oct 12, 2026
- NIST's agent identity work starts from OAuth, SPIFFE and SCIM and defers agents from outside the enterprise
Article · · NIST National Cybersecurity Center of Excellence · Harold Booth et al. · Feb 5, 2026
- 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
- The 'intent' in the Agentic JWT draft is a workflow step, and the agent reports its own fingerprint
Draft · · IETF Datatracker · Abhishek Goswami · Jul 1, 2026
- xChk ships human OIDC portfolios and a separate agent approval API
Paper · · arXiv · Sean MacGuire · Jul 15, 2026
- Glide pitches the SIM card's key as the replacement for SMS codes, resting its AAL3 claim on hardware alone
Podcast · · The Future of Identity · Eran Haggiag – Rebuilding Digital Identity Around SIM Cards for the AI Era · Jun 23, 2026
- A 'decentralized' agent identity draft blocks risky calls when its Registry is down, and did:aip is taken
Draft · · IETF Datatracker · Paras Singla · Apr 17, 2026
- For US banks to accept mobile driver's licenses, an OpenID Foundation group proposes five trust signals
Article · · OpenID Foundation · Serj Hallam · Nov 5, 2025
- FIDO pairs passkeys with digital ID credentials but spells out steps only for moderate assurance
Article · · FIDO Alliance · Christine Owen et al. · Sep 22, 2025
- 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
- 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
- RFC 6750 tokens work for whoever holds them; RFC 9700 now urges key binding and bars them from query strings
Article · · RFC Editor · Michael B. Jones et al. · Oct 1, 2012
- A 32-author 2024 paper asks for a credential that proves you are human and nothing more
Paper · · arXiv · Steven Adler et al. · Aug 15, 2024
Related terms
What appears alongside NIST SP 800-63 in the same briefings.
NIST SP 800-207NISTIR 8587REAL IDISO/IEC 29115GNAPmDL / mobile IDsForgeRockSAML