Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Kill Session
Cyber Security

Kill Session

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

Kill Session is a control that immediately ends an active user session and revokes the access tokens tied to it. In practice, it is used to cut off access during compromise, offboarding, or escalation events so the user can no longer operate inside connected SaaS applications.

What Kill Session Does in Practice

Kill Session is an immediate access cutoff, not a gradual timeout. It terminates the live browser or app session and invalidates the tokens tied to that session so the user cannot keep operating with an already-established authenticated context. That makes it a fast containment control when access has to end right away.

Because the control acts on an active session, it is most useful when the risk is not just future login, but continued use of a current trust relationship. In an environment with connected SaaS apps, that trust relationship can outlive the initial sign-in unless the session and its token set are explicitly revoked.

Why Session Termination Matters for Access Control

A kill session action sits between authentication and ongoing authorization. Authentication may already have succeeded, but the session still represents an active right to act until it is revoked. That is why this control is often paired with offboarding, suspected compromise, or privilege changes: it closes the gap between “the account is no longer trusted” and “the browser or client still works.”

Its effectiveness depends on how the application and identity layer manage token lifetimes, refresh behavior, and session state. If a system only logs the user out locally but leaves bearer tokens valid elsewhere, the practical effect is weak. A real kill session must end the live session and remove the access path the session was using.

This is also why session revocation is more than a convenience feature. It is a governance control for cutting off access quickly when a human user, contractor, administrator, or other account holder should no longer be able to act through connected services.

Where Kill Session Is Used

Kill session is commonly used in three moments: when compromise is suspected, when a person leaves or changes role, and when an escalation event requires immediate containment. In each case, the intent is the same, stop an existing authenticated context from being reused.

It is especially relevant in SaaS environments where users may have multiple active sessions across devices or browsers. One application logout does not always end every session everywhere, so administrators need a control that reaches the actual access tokens and not just the visible browser state.

In practice, the control is often part of a broader access review and incident response process. If the account still has valid credentials, or if related sessions remain active in other apps, session termination alone may only be a partial containment step.

What Can Go Wrong if Session Revocation Is Weak

Weak session revocation leaves a window where a user can continue acting after access should have ended. That creates exposure during offboarding, account takeover response, and privilege reduction, especially when a token can be replayed until it expires naturally. For a practical hardening reference on session revocation, token replay concerns, and related SaaS containment patterns, see the NetScaler ADC and Gateway Hardening Guide.

Because token-based sessions often bridge multiple connected services, the failure is not limited to a single app. If the session or token remains valid, an attacker or former user may retain access to data, actions, and administrative functions even after the organisation believes the account has been cut off.

Failure mechanism: The application revokes the visible session but leaves bearer tokens, refresh tokens, or parallel sessions usable, so the trust relationship persists after the intended cutoff.

Impact: Access continues beyond the decision to terminate it, which can prolong compromise, undermine offboarding, and delay containment across linked SaaS applications.

Standards & Framework Alignment

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

NIST SP 800-53 Rev 5 and OWASP ASVS set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementSession revocation depends on managing and invalidating authenticators and tokens.
AC-2 — Account ManagementKill session supports timely disabling of access tied to user accounts and lifecycle events.
Recommendation — Revoke or expire authenticators and related tokens immediately when access must end. Disable accounts and terminate active sessions when offboarding or compromise is confirmed.
OWASP ASVSV7 — Session ManagementKill session is a session-management control that ends authenticated sessions and their token state.
Recommendation — Invalidate session state server-side when a user logs out or loses authorization.

Practitioner Guidance

Why practitioners should care: A kill session is only effective if it is applied to the real session state, not just the user interface. When you use it for compromise or offboarding, verify that the action invalidates the session material that can still be presented to downstream services. NHIMG’s How to Read a CVE Advisory Guide is useful when you need to interpret advisory language around revocation, workaround, and post-patch rotation.

Common misunderstanding: Logging a user out is not always the same as revoking all active access. In many environments, administrators need to end every active session and consider whether related credentials, tokens, or remembered device trust also need attention.

Practitioner takeaway: Treat kill session as a containment control, not a cleanup step, and use it when you need immediate loss of trust to be enforced across the service boundary.

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