Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

Session Proxying

← Back to Glossary
By NHI Mgmt Group Updated November 18, 2026 Domain: Threats, Abuse & Incident Response

Session proxying is the technique of placing an attacker-controlled intermediary between the victim and the real service. It allows the attacker to observe or relay authentication traffic as it happens, which makes token theft and MFA bypass much harder to detect with static controls.

How session proxying works

Session proxying inserts an intermediary between the user and the real service, so the attacker can observe, relay, or selectively modify authentication traffic in real time. The core danger is that the victim still appears to be interacting with the legitimate service, which preserves the user experience while the attacker remains in the path.

This is different from a simple password theft event. The intermediary can sit inside an active session, which makes the technique useful for harvesting one-time codes, intercepting cookies, or relaying challenge responses that would otherwise be tied to the original login flow.

Why session proxying is dangerous

The technique is dangerous because it targets the moment when trust is highest: after a user has already begun authenticating. That lets an attacker work around static defences that only look for reused passwords, suspicious logins, or known-bad credentials. It is especially effective when the protected service relies on session cookies, step-up prompts, or browser-based trust decisions that are hard to distinguish from genuine user activity.

In practice, session proxying turns the defender's own authentication flow into an attack surface. If the service accepts a valid session token or a relayed authentication outcome, the attacker may not need to break the underlying password or MFA mechanism at all.

What organisations should look for

Exposure is usually easiest to assess from the outside-in and the inside-out at the same time. Check which internet-facing login portals, reverse proxies, identity providers, and remote-access paths could be placed in the middle of an authentication transaction, then compare those against vendor guidance and your own asset inventory.

For validation and design review, the most relevant references are the OWASP ASVS, which covers authentication and session requirements, and the NIST SP 800-63 Digital Identity Guidelines, which frame phishing-resistant authentication and binding the authenticator to the session.

Where the service uses tokens rather than direct browser sessions, RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP) is relevant because sender-constrained tokens reduce the value of a stolen bearer token.

How defenders reduce the attack surface

Controls that reduce session proxying usually focus on making the captured artefact less reusable. Strong session binding, phishing-resistant authentication, short-lived sessions, reauthentication for sensitive actions, and token constraints all make it harder for an attacker to reuse what they intercept.

Network and policy controls also matter. Zero trust assumptions, conditional access, device posture checks, and tighter session lifetime rules can help, but they should be treated as supporting controls rather than a guarantee. A live proxy can still pass some controls if they only inspect the initial login, not the continuity of the session.

For operational hardening, the OWASP Cheat Sheet Series is a useful implementation reference for session handling, authentication hardening, and practical defensive patterns.

Detection and response after suspected use

Detection is difficult because the attacker may preserve a normal user experience while quietly relaying traffic. Useful signals include unusual login timing, impossible travel paired with successful session reuse, authentication prompts that arrive in patterns inconsistent with the user's normal behaviour, and session state that changes without the expected device or browser continuity.

If session proxying is suspected, review token issuance, session reuse, and recent authentication events together rather than treating them as isolated alerts. The aim is to determine whether the session was merely observed, relayed, or fully hijacked, because each of those states implies a different containment path and a different likelihood of follow-on compromise.

Risk and Threat Considerations

Session proxying creates a direct path from authentication interception to account compromise, because the attacker can sit between the user and the service long enough to capture or relay live trust signals. The main risk is not just token theft, but the ability to keep pace with an active login flow while bypassing controls that assume the session is still tied to the real user.

Failure mechanism: A relayed authentication flow lets the attacker obtain a valid session artefact or successful MFA outcome without needing to defeat the underlying credential outright.

Impact: The attacker can gain authenticated access, persist through the session lifetime, and pivot to data access, privilege abuse, or additional account takeover activity.

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 OWASP ASVS, NIST SP 800-63 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP ASVSV6 — AuthenticationSession proxying targets authentication flow integrity and session handling.
V7 — Session ManagementThe attack abuses live session trust and token reuse.
Recommendation — Verify authentication flows resist relaying and bind sessions to the authenticated party. Harden session lifecycle controls so intercepted sessions cannot be reused easily.
NIST SP 800-63Digital Identity GuidelinesProvides phishing-resistant authentication and session-binding guidance for relayed logins.
Recommendation — Use phishing-resistant authenticators and bind sessions to the genuine authenticator and device.
OWASP API Security Top 10API2 — Broken AuthenticationRelayed authentication outcomes can undermine API and service authentication assurance.
Recommendation — Protect authentication endpoints against relayed or replayed login outcomes.
NIST Zero Trust (SP 800-207)Zero Trust ArchitectureSession proxying exploits assumptions of ongoing trust after initial authentication.
Recommendation — Continuously verify access instead of trusting an initial login alone.

Practitioner Guidance

What to watch for: Treat any control that only protects the first login step as incomplete, because session proxying exploits the gap between initial authentication and ongoing session trust. Pay particular attention to flows where the browser, token, or device trust is not continuously revalidated.

Governance implication: Owners of authentication and session infrastructure should define where session binding is required, where reauthentication is mandatory, and which sensitive actions must not rely on an older trust decision. That ownership matters because proxy-resistant design is usually a cross-team decision, not a single product setting.

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 18, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org