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

On-Path Attack

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

An on-path attack is an attack in which an adversary sits between two communicating parties and can observe, intercept, modify, or relay traffic. It usually targets network links, proxies, or compromised infrastructure, and it can defeat confidentiality or integrity when encryption and authentication are absent or improperly validated.

What an on-path attack changes in practice

An on-path attack matters because the adversary is no longer guessing from the outside, they are positioned to see or shape the communication itself. That makes it a control problem as much as an interception problem: if the channel is not strongly protected, the attacker can quietly read data, alter requests or responses, or relay traffic while remaining difficult to spot.

The core danger is that the attacker can preserve the appearance of a normal connection while degrading its trust properties. In real environments that often means targeting weakly protected links, unsafe proxy chains, or infrastructure that has already been compromised and can be used as a relay point.

Where on-path attacks happen

On-path attacks usually arise wherever two systems depend on an intermediate network path that an adversary can influence. That can include local network segments, wireless environments, corporate proxies, compromised routers, load balancers, VPN terminators, or cloud and edge infrastructure that sits between users and services.

The important point is not the device type but the position in the flow of traffic. If a party can inspect packets, alter them, or selectively drop and forward them, the attack shifts from passive eavesdropping into active manipulation. That is why routing integrity, endpoint trust, and the authenticity of intermediaries all matter.

Related exposure is often easiest to understand through attack-path thinking, especially when a reachable proxy, gateway, or other intermediary becomes the choke point that makes traffic interception possible. See Attack Path Analysis vs Attack Surface Management for how reachable paths differ from simple external exposure.

Why encryption and authentication are the deciding controls

Encryption helps protect confidentiality, but on-path attacks are especially dangerous when encryption is missing, misconfigured, or not validated end to end. If a client accepts the wrong certificate, trusts an injected proxy, or fails to verify the peer properly, the attacker can remain in the middle even when traffic looks encrypted.

Authentication matters just as much as confidentiality because the attacker is often trying to impersonate one side of the conversation. Strong channel authentication, certificate validation, and resistant session handling reduce the chance that the middle can silently substitute itself for the intended endpoint.

That is also why identity and key handling become relevant whenever the attacker can steal or replay session material. A compromise on the path can expose tokens, API keys, cookies, or other secrets that then outlive the original interception event.

Where the intermediary is a web or API endpoint, broken verification and trust assumptions can turn a network position into full logical access. For a protocol-specific view of that problem, compare it with OWASP API Security Top 10, which covers authentication and authorisation failures that are often amplified by interception.

Operational consequences after interception

The most immediate consequence is loss of trust in the traffic path. A successful on-path position can expose credentials in transit, alter commands or configuration, redirect users, downgrade protections, or inject malicious content into otherwise legitimate sessions.

Once traffic has been observed or modified, the impact can extend beyond the single connection. Captured tokens or keys may enable later session reuse, lateral movement, or repeated access from a different network location. That is why organisations often have to treat an on-path event as both a transport problem and a potential identity compromise.

Detection is difficult because the attacker can keep the service functioning. Sudden certificate anomalies, unexpected proxy usage, route changes, odd TLS failures, and unexplained session behaviour are all worth reviewing, but none of them alone proves an on-path attack.

For broader detection and adversary tradecraft context, MITRE ATT&CK Enterprise Matrix is useful for mapping credential access, lateral movement, and defence evasion that often follow interception.

How defenders reduce exposure to on-path attacks

Defence starts with removing easy interception opportunities: validate certificates correctly, avoid blind trust in intermediaries, harden network segments, and prefer protocols that authenticate endpoints rather than assuming the path is trustworthy. Monitoring proxy and routing changes also matters because a legitimate-looking intermediary can become part of the attack path.

When compromise is suspected, review whether credentials, tokens, signing material, or cookies traversed the affected path and whether any sessions need to be revoked. The practical goal is not only to restore network integrity, but also to close any access that was enabled by the interception.

If you need a control framework for formalising those protections, NIST SP 800-53 Rev 5 Security and Privacy Controls provides the access control, identification and authentication, audit, and system integrity controls most directly relevant to defending against on-path abuse.

NIST Cybersecurity Framework 2.0 is also useful at the programme level because on-path defence spans identify, protect, detect, respond, and recover, not just one technical fix.

Risk and Threat Considerations

On-path attacks are dangerous because they turn the network path into an attacker-controlled trust boundary. The biggest risk is silent compromise, where the connection still appears to function while traffic, credentials, or session material are being observed or altered.

Failure mechanism: A weakly authenticated or improperly validated channel allows the adversary to insert themselves between endpoints, relay traffic transparently, and exploit any trust placed in the intermediary, certificate, or route.

Impact: Confidentiality can be lost through interception, integrity can be lost through tampering, and stolen sessions or secrets can extend the compromise well beyond the original connection.

Standards & Framework Alignment

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

MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1557 — Adversary-in-the-MiddleDefines the interception and relay technique central to on-path attacks.
Recommendation — Map interception and relay indicators to T1557 and hunt for route, proxy, and session abuse.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementOn-path attacks often expose or replay authenticators, tokens, and session material.
IA-7 — Cryptographic Module AuthenticationValidates the peer and protects against impersonation on an intercepted channel.
SC-23 — Session AuthenticityProtects the integrity of active sessions against tampering or redirection.
Recommendation — Rotate, revoke, and protect authenticators and session material exposed on the path. Require strong peer authentication to prevent a middle party from impersonating the endpoint. Enforce session authenticity checks to detect tampering and session hijacking.

Practitioner Guidance

What to watch for: Treat unexplained certificate warnings, proxy changes, route anomalies, TLS failures, or sudden session instability as signals that the traffic path may no longer be trustworthy. The investigation should include whether any credentials, tokens, or other secrets crossed the affected path and whether they need to be rotated or revoked.

Governance implication: Ownership for the communication path should be explicit, because on-path risk often sits between network, platform, and application teams. The most effective response is usually the one that makes trust assumptions visible, testable, and continuously verified.

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