Skip to content
IAM Insights

Explainers · Glossary

Session hijacking

session hijack

An attack in which an unauthorised party obtains a valid session identifier and uses it to impersonate the original client and act on its behalf.

reference →

In our briefings

The claim each of the newest briefings on Session hijacking would have you leave with.

  1. Mattson, SecureAuth's chief executive, argues that a model cannot be secured the way tested software is: it is non-deterministic, and a request phrased another way, or in another language, gets around whatever it was told not to do. His advice is to "just assume that it could do anything any time" and put the guardrails around the model, so that a financial transaction or a database change the agent attempts is approved and recorded. He cites Anthropic as saying no guardrail is adequate. The statement we take him to mean, Anthropic's of 12 June, which he recalls as "three weeks ago, I believe", says the company suspects perfect jailbreak resistance "is not currently possible for any model provider", while defending its own safeguards as strong. Briefings we have published on other sources move the control off the model too: a Silverfort guest calls guardrails on a probabilistic system guidance rather than control, ClearVector's John Laliberte compares them to bowling bumpers, and a zero-trust framework paper for agents adds a session-enforcement layer.

    When the model cannot be trusted, control what the agent can reach, checked on every actionBI-FIND-2026-0151

Cited in 1 briefing

Every briefing that discusses this term, newest first.

  1. When the model cannot be trusted, control what the agent can reach, checked on every action

    Podcast · · Tech Talks Daily · AI Agent Security: Why Identity and Access Control Matter More Than Guardrails · Aug 11, 2026