Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Expiration Claim
Cyber Security

Expiration Claim

← Back to Glossary
By NHI Mgmt Group Updated November 5, 2026 Domain: Cyber Security

The expiration claim sets the time after which a JWT must no longer be accepted. It limits how long a compromised or intercepted token can be replayed. When expiration is missing or ignored, access can persist indefinitely, which turns a temporary credential into a long-lived security exposure.

What the expiration claim does in a JWT

The expiration claim is the token’s built-in end time. It tells a relying service when the JWT must stop being accepted, even if the signature is otherwise valid. That makes time a security boundary, not just a convenience field, because the claim limits how long stolen, replayed, or cached tokens remain useful.

Why expiration matters for token trust

JWTs are often treated as proof that the caller is authenticated, but that trust only holds while the token is still within its validity window. Expiration narrows the replay window, reduces the value of intercepted tokens, and helps prevent old sessions from surviving after a user logs out, changes role, or loses access. If a verifier ignores the claim, the token’s authenticity no longer implies current authority.

How expiration interacts with session and credential lifecycle

Expiration is only one part of a broader lifecycle design. It works best when paired with short-lived access tokens, refresh-token controls, revocation logic where needed, and server-side session termination for high-risk actions. For long-lived access, organisations should treat the token as a bearer secret: once exposed, it can be reused until it expires or is otherwise invalidated.

In practice, the claim also helps limit blast radius after compromise. A short expiry can reduce the time an attacker has to pivot with a stolen token, while a long expiry increases the chance that a captured token will still be valid long after the original event. That is why expiration is usually a security control, not just an implementation detail.

When implementation mistakes make expiration ineffective

Expiration only protects the system if every verifier enforces it consistently and uses a trustworthy time source. Common failures include accepting expired tokens because of clock skew handling errors, allowing excessive leeway, or treating JWT content as trustworthy without checking the claim at all. Another failure mode is using expiration so far in the future that the token becomes functionally persistent.

Teams should also be careful not to confuse token expiry with user logout. A token can remain valid even after the user believes access has ended unless the application explicitly invalidates it or keeps the lifetime short enough that residual risk is acceptable.

Risk and Threat Considerations

Expired-or-ignored JWT checks create a replay problem: a bearer token can be copied once and then reused until the system finally stops accepting it. That turns a temporary compromise into a durable access path, especially when the token grants broad API or application access.

Failure mechanism: The verifier accepts tokens past their intended lifetime, or the lifetime is so long that theft, interception, or session reuse remains valuable to an attacker.

Impact: Attackers can continue accessing protected resources, keep sessions alive after the legitimate user should be cut off, and extend the usefulness of a stolen secret well beyond the original compromise window.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP API Security Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5, NIST SP 800-57 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP API Security Top 10API2 — Broken AuthenticationJWT expiration is part of API authentication validity and replay resistance.
Recommendation — Enforce token expiration checks and reject expired bearer tokens at every API boundary.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementExpiration governs the lifecycle and validity of authenticators and bearer tokens.
IA-2 — Identification and Authentication (Organizational Users)JWTs often assert authenticated user sessions that must not remain valid indefinitely.
Recommendation — Set and enforce short token lifetimes as part of authenticator lifecycle control. Require reauthentication when a session token is no longer valid or trusted.
NIST SP 800-57Key Management LifecycleJWT validity depends on cryptographic trust material and rotation timing for signing keys.
Recommendation — Align token lifetimes with signing-key rotation and retirement periods.
NIST CSF 2.0PR.AA-05 — Manage assets and identities through the identity lifecycleThe claim limits how long a token-backed identity assertion remains usable.
Recommendation — Set identity-bound token lifetimes so access does not outlive the approved lifecycle.

Practitioner Guidance

What to watch for: Treat expiration as a control that must be enforced everywhere a JWT is consumed, not just where it is issued. Review how your services handle clock skew, maximum token lifetime, refresh-token design, and whether any privileged workflows require shorter validity than ordinary sessions.

Governance implication: Define the acceptable token lifetime by risk, not by convenience, and make sure application owners understand that longer-lived JWTs increase replay exposure. For high-value systems, keep the validity window short enough that a stolen token is less useful than the response time to detect and contain the incident.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org