Diversion is the redirection of a user, request or process away from its intended destination to another path or target. In security work, it can describe traffic steering, phishing redirects, or any mechanism that changes where data, credentials or sessions are sent, often to capture, inspect or misuse them.
What Diversion Means in Security Context
Diversion is the deliberate or accidental redirection of a user, request, or process away from its intended destination. In security, the concept matters because the new path may be controlled by an attacker, a proxy, or a misconfigured system, changing where data, credentials, or sessions are delivered and who can observe or alter them.
At a technical level, diversion can happen in web traffic, API flows, authentication journeys, email delivery, or application routing. The security significance is not the redirection itself, but the trust decision hidden inside it: if the redirected target is not the one the user or system expected, the integrity of the exchange is already in doubt.
How Diversion Is Used in Attacks and Operations
Diversion is a common building block in phishing, token theft, traffic interception, and session abuse. A redirect can move a user from a legitimate sign-in page to a lookalike site, send credentials through an attacker-controlled endpoint, or steer a process into a hostile integration that captures data before it reaches the original destination. The same pattern also appears in benign operations, such as load balancing, failover, content routing, and traffic inspection.
That dual use is what makes diversion risky. A valid redirect chain can be indistinguishable from a malicious one unless the organisation can verify destination control, certificate trust, request integrity, and the reason the path changed. For this reason, diversion should be treated as a control point, not just a networking detail.
Security teams often map these behaviours to MITRE ATT&CK Enterprise Matrix when they are looking at credential access, lateral movement, or adversary-controlled redirection in an attack chain.
Why Diversion Matters for Trust, Credentials, and Sessions
Diversion becomes especially dangerous when the redirected flow carries secrets or state. Credentials, session cookies, API tokens, authorization codes, and callback URLs can all be exposed if the destination is untrusted or if the redirect breaks the original trust boundary. Even when the data is not disclosed directly, the attacker may still gain a foothold by capturing an authentication response, replaying a session, or inserting themselves into a workflow that was assumed to be direct.
That is why diversion is closely related to phishing resistance and routing assurance. If users, browsers, or services can be steered to an unintended endpoint, the attacker may not need to break cryptography at all, only the assumptions around where trust is supposed to terminate. Identity assurance and redirect validation are therefore part of the security model, not optional extras.
For identity-centric controls, NIST SP 800-63 Digital Identity Guidelines is relevant because diversion often targets the authentication journey itself, while NIST SP 800-53 Rev 5 Security and Privacy Controls is useful for framing access control, authentication, audit, and system integrity expectations around redirected flows.
Detection and Control of Divergence in Traffic Paths
Detecting diversion means comparing the intended path with the actual one. That usually involves inventorying approved redirect patterns, monitoring destination drift, inspecting DNS and HTTP redirect chains, validating application callbacks, and reviewing whether user traffic is leaving expected trust zones. The key question is whether the redirection was expected, authorized, and bounded.
In practice, strong controls reduce the chance that a redirect can be used to steer credentials or sessions to a malicious endpoint. Zero Trust thinking is useful here because it assumes the path itself is not trustworthy and requires verification at each step. For broader operational governance, organisations also benefit from inventorying redirectors, tracking third-party dependencies, and testing whether authentication flows still land only where they should.
NIST SP 800-207 Zero Trust Architecture is a strong fit for this concept because diversion is fundamentally about refusing to trust the route simply because it appears familiar.
Examples of Benign and Malicious Diversion
Not every diversion is harmful. A browser redirect after login, a failover to a backup service, or a security proxy that inspects traffic before forwarding it may all be legitimate. The difference lies in intent, authorization, and transparency. If the redirect is documented, expected, and constrained, it is a routing mechanism. If it is hidden, deceptive, or used to capture sensitive data, it becomes a security issue.
That distinction matters in incident investigations as well. Analysts should ask whether the diversion changed only the delivery path, or whether it also changed the security properties of the exchange. If the destination, certificate chain, domain ownership, or callback target no longer matches the expected trust model, the diverted flow deserves deeper review.
When diversion is used for malicious collection or interception, the pattern often overlaps with phishing infrastructure and credential theft techniques described by NIST SP 800-53 Rev 5 Security and Privacy Controls and the attack-path perspective used in MITRE ATT&CK Enterprise Matrix.
Risk and Threat Considerations
Diversion creates risk when the redirected path is easier to compromise than the original one, or when defenders assume the path remains trusted after redirection. That can expose credentials, sessions, tokens, and sensitive traffic to interception, replay, or misuse, especially when users cannot easily see that the destination has changed.
Failure mechanism: An attacker or misconfiguration alters the route, then exploits the trust placed in the new endpoint to capture secrets, manipulate traffic, or insert a fraudulent destination into a normal workflow.
Impact: The organisation can lose confidentiality of credentials or data, break authentication integrity, and create a foothold for account takeover, session abuse, or downstream compromise.
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 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1021 — Remote Services | Diversion can reroute access paths used in adversary movement and interception. |
| Recommendation — Map diverted access paths to attacker movement techniques and hunt for abnormal redirection chains. | ||
| NIST SP 800-53 Rev 5 | IA-2 — Identification and Authentication (Organizational Users) | Diversion often targets user authentication flows and credential handling. |
| SC-23 — Session Authenticity | Redirected sessions can be replayed or misbound if authenticity is not preserved. | |
| AU-3 — Content of Audit Records | Redirects need traceable records to detect and investigate path changes. | |
| Recommendation — Verify that redirected authentication flows still satisfy user identification and authentication controls. Enforce session authenticity checks on redirected web and application flows. Log redirect source, destination, and decision context for later investigation. | ||
| NIST Zero Trust (SP 800-207) | 3.1 — Zero Trust Architecture principles | Diversion challenges implicit trust in the network path and destination. |
| Recommendation — Apply continuous verification to redirected traffic instead of trusting the path by default. | ||
Practitioner Guidance
Why practitioners should care: Diversion is not just a routing issue, it is a trust boundary issue. Security teams should treat every redirect path as part of the attack surface when it can carry authentication traffic, user input, or sensitive data. The practical question is whether the destination is the one the user or system intended to reach.
What to watch for: Unexpected redirect chains, destination drift, callback mismatches, and sign-in flows that leave the expected domain or trust boundary should be investigated quickly. These are often the earliest signs that a legitimate flow has been bent toward interception or abuse.
Related resources from NHI Mgmt Group
- How should security teams reduce the impact of lateral phishing, invoice fraud, and payroll diversion as attackers target human behaviour instead of technical flaws?
- What happens when healthcare organizations rely on manual monitoring instead of AI-assisted analytics for drug diversion detection?
- How should organisations reduce the risk of BEC payroll diversion scams in payroll operations?
- Why do payroll diversion scams succeed even when emails contain no malicious links or attachments?
Deepen Your Knowledge
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.
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