Skip to content
NewA calmer, faster ZeroHour
StoryAdvisoryinfo

NIST IR 8587 finalized: new playbook targets identity token theft and forgery

2 sources · 2 articlesFirst reported Updated ()1 · 1 read
What's new

Guidance finalized and released: IR 8587 was issued September 15, 2026 as dedicated token-protection implementation guidance building on NIST SP 800-53 Rev. 5.1.1. | Scope broadened beyond traditional user tokens: the guidance extends token protections to AI agents and adds post-quantum cryptography readiness. | Framing elevated: tokens are to be treated as high-value credentials equivalent to…

Merged summary · glm-5.3-flash · rewritten as coverage arrivesSummaries by Vani AI

NIST IR 8587, released September 15, 2026, gives federal agencies and cloud providers recommendations to prevent theft, forgery, and misuse of SAML, OpenID Connect, and OAuth 2.0 tokens, extending token protection guidance to AI agents and post-quantum…

NIST Internal Report (IR) 8587 provides implementation recommendations covering token creation, signing, validation, storage, revocation, lifecycle management, and session management across SAML, OpenID Connect, and OAuth 2.0 environments. The sources differ on attribution: Help Net Security says NIST and CISA finalized the playbook, while GBHackers attributes the September 15, 2026 release to NIST. The guidance builds on NIST SP 800-53 Rev. 5.1.1 and incorporates lessons from breaches involving stolen signing keys, abused OAuth applications, and replayed federated assertions. It cites an incident in which foreign actors forged tokens with a stolen commercial signing key to steal more than 60,000 emails from one government agency. Recommendations include strong signing algorithms, cryptographic key protection and rotation, strict claim validation, short token lifetimes, token binding, leakage prevention, and continuous monitoring for abnormal token use such as impossible travel and suspicious token reuse patterns. The report urges treating tokens as high-value credentials equivalent to authenticated sessions, defines shared security responsibilities between cloud providers and customer organizations, and promotes secure-by-design defaults from cloud service providers. It also recommends extending token protections to AI agents and preparing identity systems for a future post-quantum cryptography transition.

Key facts
  • Document: NIST Internal Report (IR) 8587, released September 15, 2026 (per GBHackers).
  • Attribution differs: Help Net Security says NIST and CISA finalized the playbook; GBHackers credits the release to NIST.
  • Scope: identity tokens, access tokens, and federated assertions across SAML, OpenID Connect, and OAuth 2.0 environments.
  • Builds on NIST SP 800-53 Rev. 5.1.1 and incorporates lessons from breaches involving stolen signing keys, abused OAuth applications, and replayed federated assertions.
  • Cites an incident in which foreign actors forged tokens with a stolen commercial signing key to steal more than 60,000 emails from one government agency.
  • Recommendations: strong signing algorithms, key protection and rotation, strict claim validation, short token lifetimes, token binding, leakage prevention, and monitoring for impossible travel and suspicious token reuse patterns.
  • Urges treating tokens as high-value credentials equivalent to authenticated sessions.
  • Defines shared security responsibilities between cloud providers and customer organizations and promotes secure-by-design defaults from cloud service providers.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat
Vendors
NISTCISA

Coverage

oldest first · one row per article · UTC
  1. · Sep 16, 2026 Help Net SecurityFirst report

    NIST and CISA finalize playbook to stop token theft and forgery

    NIST and CISA finalized NIST IR 8587, a playbook helping federal agencies and cloud providers defend identity tokens against theft and forgery.

  2. · Sep 16, 2026 GBHackers

    NIST Issues New Guidance to Protect SSO and API Tokens From Theft and Forgery

    NIST released IR 8587 giving agencies and cloud providers recommendations to prevent identity token forgery, theft, and misuse in SSO and API environments.