NIST IR 8587 and token theft: what the guidance means for choosing an identity provider
Reviewed 2026-11-10 · Editorial assessment by the editors
By the editors · Published 2026-09-17 · 5 min read
NIST IR 8587, final on 15 September 2026, tells federal agencies and cloud service providers how to protect identity tokens, access tokens and assertions from forgery, theft and misuse. It is written for federal systems, but for any buyer it turns into a short list of questions about signing keys, token lifetimes and how quickly a provider can end a session.
What is NIST IR 8587?
It is a NIST Interagency Report titled "Protecting Tokens and Assertions from Forgery, Theft, and Misuse: Implementation Recommendations for Agencies and Cloud Service Providers". Its authors are from NIST, Accenture Federal Services and CISA. A draft was published on 22 December 2025 and the final version on 15 September 2026.
The NIST publication page associates the report with Executive Order 14306 and says it builds on updates to NIST SP 800-53 Release 5.1.1.
What does the report cover?
According to its abstract, the report outlines principles for cloud service providers and the agencies that use them, details architectural considerations for identity providers and authorization servers, and recommends enhancements to key management and token verification. It gives technical recommendations for three scenarios: single sign-on, federation and API access.
The abstract says the report addresses threats demonstrated in recent high-profile attacks, and stresses secure by design practices, configurability, interoperability and continuous monitoring. This note is based on the NIST publication page, the abstract and the OpenID Foundation's summary; it does not quote recommendations beyond those.
Which standards does it point to?
The OpenID Foundation wrote on 16 September 2026 that the report specifically recommends two of its specifications. The Shared Signals Framework "defines how identity providers and relying parties exchange security event signals in a standard way". The Continuous Access Evaluation Profile builds on it so providers can communicate changes in a user's session or risk posture, and access can be re-evaluated during a session rather than only at sign-in.
Both large vendors already work with signals. Okta's Identity Threat Protection takes signals from CrowdStrike, Zscaler, Palo Alto Networks and Jamf over the Shared Signals Framework and lists Universal Logout. Microsoft's Conditional Access evaluates user, device, location, application and risk signals. The conditional access comparison calls the two.
Why do signing keys matter so much?
An identity provider signs every SAML assertion and OpenID Connect ID token it issues, and applications trust a sign-in because the signature checks out. Anyone who obtains the signing key can therefore create valid tokens for any user; with SAML this is known as Golden SAML. Token theft is the other risk: a valid token copied from a device or a log can be replayed until it expires.
Vendors approach the key problem in different ways. NewCore states that its Secure Split Key "distributes signing authority between our cloud and your environment", and its launch release lists Golden SAML, adversary-in-the-middle, session theft and token replay as the attacks it targets. On the standards side, the OpenID Foundation approved OpenID Connect Key Binding 1.0 as an Implementer's Draft on 10 September 2026, a specification for binding cryptographic keys within OpenID Connect flows.
What can you check in the products you already run?
- Token lifetimes: Microsoft lists configurable token lifetime policies for access, ID and SAML tokens per application as generally available in April 2026. Find out what your current lifetimes are before changing them.
- Session revocation: Okta lists Universal Logout in Identity Threat Protection. Ask which of your apps support it.
- Signals: list which of your tools send or receive Shared Signals Framework or CAEP events today.
- Agent tokens: if AI agents call your tools, the MCP authorization spec requires audience-bound tokens and says authorization servers should issue short-lived access tokens. See the note on MCP authorization.
What should you ask an identity provider?
- Where are token-signing keys held, who can export them, and how often are they rotated?
- Are signing keys separated between tenants?
- What are the default and minimum lifetimes for ID tokens, access tokens and SAML assertions?
- Which Shared Signals Framework and CAEP events do you send and receive?
- How long does it take from a revocation to every connected app ending the session?
- Have you mapped your product to NIST IR 8587, and will you share the mapping?