Skip to content
IAM Insights

Explainers · Glossary

NIST SP 800-207

Zero Trust Architecture · ZTA

The National Institute of Standards and Technology (NIST) Zero Trust Architecture publication: no implicit trust from network location or credential possession, and continuous verification of each request.

reference →

In our briefings

The claim each of the newest briefings on NIST SP 800-207 would have you leave with.

  1. Uber runs per-hop token exchange with a full actor chain for AI agents in production, and has published sample tokens and a latency chart. Its security token service gives each hop a fresh token scoped to one audience, with a lifetime "in the order of minutes" (both sample payloads expire 300 seconds after issue), and the token carries the attested chain from the engineer to the agent making the call. Uber says "the system has been adopted by thousands of internal agents" and reports the exchange API's P99 as "consistently below 40 milliseconds" under current load; its chart sits mostly under 10 ms, with one spike reaching 40. The post covers this identity layer. Uber frames dynamic access control and a unified policy enforcement plane as its direction on top of it, and names session and intent claims as additions the token could carry in the future.

    Uber runs per-hop token exchange with a full actor chain for AI agents in productionBI-FIND-2026-0081

  2. A delegated mission's authority must be a subset of the parent's, McGuinness argues, and OAuth token exchange (RFC 8693) does not guarantee it. Token exchange carries the delegation, but he calls enforcing the narrowing implementation-dependent and not a protocol guarantee. He writes that in production token exchange deployments today, child tokens routinely inherit the parent's full scope unless the implementation explicitly narrows them, so agents compound a failure that OAuth delegation already has. A child agent may also run in a different runtime or expose weaker telemetry, so authority that is narrower on paper can be less governable in practice. He proposes that the mission's state owner rate each hop's trust quality, meaning how well that hop can be observed and checked, and give a low-rated child a more conservative budget. For a sub-agent an orchestrator spawns at runtime, he says the state owner must still issue its authority, but asks what triggers that issuance. Our briefing on Uber's production design found a token chain that records each agent hop without describing any narrowing. Our briefing on Highflame's open-source ZeroID found narrowing by scope intersection offered as an explicit step.

    OAuth token exchange does not guarantee a sub-agent stays inside its parent's accessBI-FIND-2026-0228

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

    Anthropic asks for per-agent identity; its guide leaves Claude Code sub-agent credentials unspecifiedBI-FIND-2026-0596

›Cited in 18 briefings

Every briefing that discusses this term, newest first.

  1. Uber runs per-hop token exchange with a full actor chain for AI agents in production

    Article · · Uber Engineering blog · Matt Mathew et al. · May 21, 2026

  2. OAuth token exchange does not guarantee a sub-agent stays inside its parent's access

    Article · · Control Plane by Karl McGuinness · Karl McGuinness · Mar 18, 2026

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

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

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

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

  6. Corvic's own tests find its agent vault keeps keys out of prompts but does much less against a misused connector

    Paper · · arXiv · Kenney, Corvic AI · Sep 27, 2026

  7. PayPal moved MCP tool permission checks into the server, and prompt-injected agents stopped getting through

    Paper · · arXiv · Huan Li et al. · Sep 18, 2026

  8. A SANS instructor's broker vaults agents' real keys, but its third delivery model breaks the abstract's promise

    Draft · · IETF Datatracker · Kenneth G. Hartman · Mar 29, 2026

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

  10. An OAuth draft lets device checks set an app's scopes; a first review found a copied app could reuse the result

    Draft · · IETF Datatracker · Efe Kahraman, Mekarge · Jun 9, 2026

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

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

  13. Ericsson researchers would check every query a telecom network agent sends to its knowledge base

    Paper · · arXiv · Loay Abdelrazek et al. · Oct 22, 2025

  14. One author's OpenID Connect for Agents proposal checks each delegation hop but makes the chain optional

    Paper · · arXiv · Subramanya Nagabhushanaradhya · Sep 30, 2025

  15. A 'provable' bound on agent-memory injection assumes independent layers and fills in none of its detection rates

    Paper · · arXiv · Ken Huang et al. · Aug 17, 2025

  16. An early MCP security checklist was never tested, and the protocol has since adopted only part of it

    Paper · · arXiv · Vineeth Sai Narajala et al. · Apr 11, 2025

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

  18. 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 NIST SP 800-207 in the same briefings.

NIST SP 800-63ISO/IEC 42001NIST AI 100-1HIPAASPIREEU AI ActCrewAIHashiCorp