NSA
National Security Agency · NSA-CCSS · NSA Central Security Service
The US National Security Agency, whose Central Security Service (CCSS) mission includes contributing to open cryptographic and identity standards used across US government and critical-infrastructure systems.
In our briefings
The claim each of the newest briefings on NSA would have you leave with.
The IETF datatracker shows that the IESG approved OAuth Identity and Authorization Chaining Across Domains (draft-ietf-oauth-identity-chaining) as a Proposed Standard on 22 June 2026, and that it has been in the RFC Editor's queue since that day. Revision 17, the text we read, was posted on 19 July 2026 during that editing. Its authors are Arndt Schwenkschuster and Pieter Kasselman of Defakto Security, Kelley Burgin of MITRE, Mike Jenkins of NSA-CCSS, Brian Campbell of Ping Identity and Aaron Parecki of Okta. Campbell co-wrote RFC 8693 and RFC 7523, the two RFCs the draft combines, and Parecki co-wrote RFC 9728, one of the ways it names for finding the other domain's authorization server. The working group's write-up for the IESG lists implementations, among them Keycloak 26.5 and Okta's. Two other drafts we have read point to it: the transaction-tokens draft leaves crossing domains to it, and the AI agent authentication draft says cross-domain access SHOULD use identity chaining.
OAuth's draft for crossing trust domains is approved for publication and never says agentBI-FIND-2026-0184
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
Executive Order 14412, signed on 22 June 2026, holds the binding dates of the federal post-quantum migration: key establishment for high-value and high-impact systems by 31 December 2030 and their digital signatures by 31 December 2031. It also orders a NIST pilot to finish by the end of 2027, a cryptographic bill of materials standard from CISA within 270 days, and two proposed contract rules, one requiring contractors to meet NIST's post-quantum standards by 2030. The order says nothing about certificates, authentication, tokens or code signing. Every identity requirement, from PKI-based access control to post-quantum signed tokens, comes from OMB's memo two days later, which also turned the order's "transition all" by 2030 into mitigating "as much quantum risk as feasible".
The post-quantum executive order sets the hard dates; every identity requirement is in OMB's memoBI-FIND-2026-0708
Cited in 4 briefings
Every briefing that discusses this term, newest first.
- OAuth's draft for crossing trust domains is approved for publication and never says agent
Draft · · IETF OAuth Working Group · Arndt Schwenkschuster et al. · Jul 19, 2026
- Anthropic asks for per-agent identity; its guide leaves Claude Code sub-agent credentials unspecified
Article · · Anthropic (Claude) · Anthropic · May 27, 2026
- The post-quantum executive order sets the hard dates; every identity requirement is in OMB's memo
Article · · The White House · Executive Office of the President · Jun 22, 2026
- Once people hand their credentials to an AI, the question is whether the account is still human
Podcast · · Nexus: A Claroty Podcast · John Laliberte on AI and Non-Human Identity Controls · Aug 5, 2026