It becomes a problem when cached tokens can survive beyond the intended session, move across devices, or remain valid after a user should no longer have access. Encryption helps, but governance still needs deletion on logout, revocation handling, and a clear decision on whether local persistence is acceptable for the application’s risk profile.
Why Client-Side Token Storage Becomes a Security Problem
Client-side storage is risky when a token outlives the browser session, can be copied off the device, or remains usable after access should have ended. That turns a convenience feature into a persistence mechanism for attackers, especially when refresh tokens, long-lived bearer tokens, or poorly scoped session cookies are involved. NIST’s Security and Privacy Controls emphasise lifecycle control, revocation, and access restriction, not just encryption at rest.
The practical issue is not merely where the token is stored, but what happens after logout, device loss, browser profile sync, or account disablement. NHIMG research on the Guide to the Secret Sprawl Challenge shows how credentials persist across workflows long after teams assume they are gone, and the same pattern applies to client-held tokens. In practice, many security teams discover token reuse only after a compromised endpoint or cached browser profile has already been used for unauthorized access.
How It Works in Practice
Whether client-side token storage is acceptable depends on token type, threat model, and revocation design. Short-lived access tokens in memory are materially different from refresh tokens persisted in localStorage, IndexedDB, or mobile device storage. The accepted pattern is evolving toward minimizing what the client can retain, binding tokens to context where possible, and making revocation observable and fast. For bearer tokens, possession is effectively authorization, so any exposed copy can be replayed until expiry or revocation.
Security teams typically evaluate four controls together:
NIST SP 800-53 Rev. 5 style lifecycle controls for issuance, storage, rotation, and revocation.
HttpOnly, Secure, and SameSite cookie settings when browser-based sessions do not need script access.
Short token TTLs and automatic revocation on logout, password reset, device removal, or privilege change.
Server-side session introspection or token binding checks so stale tokens are not accepted after the trust relationship changes.
This is why incidents such as the Salesloft OAuth token breach matter: once a token escapes the intended lifecycle, attackers do not need the original app login flow. The same lesson appears in the JetBrains GitHub plugin token exposure, where exposed credentials became a durable access path. These controls tend to break down in SPAs, mobile apps, and offline-first applications because developers often choose local persistence to preserve user experience while back-end revocation logic remains incomplete.
Common Variations and Edge Cases
Tighter token controls often increase login friction, token refresh traffic, and implementation overhead, so organisations have to balance usability against session resilience. There is no universal standard for whether local persistence is acceptable; current guidance suggests treating it as a risk decision, not a default. For low-risk applications, short-lived in-memory tokens may be enough. For high-value workflows, persistent client storage usually deserves extra scrutiny or a different session model.
Edge cases matter. Browser sync can copy tokens to another device. Shared devices can preserve access after a user logs out. Mobile app backups can restore credentials onto a new handset. Any architecture that relies on client storage should assume the token may be extracted, replayed, or retained longer than expected. That is why NHIMG’s IOS app secrets leakage report is relevant even beyond mobile secrets management: local persistence expands the blast radius when a device or backup is compromised.
When the application has strong revocation, rapid expiry, and low sensitivity, client-side storage can be an acceptable tradeoff. When tokens grant broad API access, can be refreshed indefinitely, or are reused across privileged workflows, the safer posture is to avoid durable client storage and rely on ephemeral, server-managed sessions instead.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST SP 800-53 Rev 5, NIST Zero Trust (SP 800-207) and NIST AI RMF set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-03 | Token persistence and rotation are core NHI credential lifecycle risks. |
| NIST CSF 2.0 | PR.AC-1 | Access token handling affects how identities are authenticated and authorized. |
| NIST SP 800-53 Rev 5 | SC-12 | Cryptographic key and token lifecycle management supports safer client storage. |
| NIST Zero Trust (SP 800-207) | AC-4 | Zero trust requires continuous evaluation, not blind trust in stored tokens. |
| NIST AI RMF | Contextual risk decisions help determine when persistence is acceptable. |
Verify every token use against current context instead of assuming prior login remains valid.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
