Glossary
Session hijacking
Definition
Session hijacking lets an attacker use someone else's active sign-in session to access a service as that person.
A stolen session token may let an attacker skip the normal sign-in step. Changing a password does not always end every existing session.
A customer may include “Session hijacking” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
Session hijacking is the unauthorised use of an existing sign-in session. After a person signs in, a service commonly uses a session token, such as a browser cookie, to recognise later requests. Someone who obtains a usable token may be able to act as that person.
The token can be exposed by malware, a vulnerable website or an attacker intercepting a sign-in flow. The attacker may not need the password or a fresh multi-factor authentication check because the session already represents a successful sign-in. How long that access lasts depends on the service's session controls.
Hypothetical example: an employee's laptop is infected with software that copies browser session data. An attacker uses a still-valid business session to download files. Resetting the password helps protect future sign-ins but may not revoke that token unless the service also ends existing sessions.
Protect devices as well as accounts, and revoke active sessions or tokens when compromise is suspected. Review unfamiliar sign-ins; shortening session lifetimes may reduce exposure but does not prevent token theft and can affect normal work.
Sources: OWASP session hijacking; MITRE theft of web session cookies.