VPN split tunneling is a configuration that sends some traffic through the VPN while allowing other traffic to go directly to the internet. It can improve performance, but it also creates exposure if sensitive traffic bypasses the encrypted tunnel. The security outcome depends on which applications are permitted to escape and how consistently policy is enforced.
Expanded Definition
VPN split tunneling is a network routing choice, not a security control by itself. It determines whether device traffic is forced through the corporate VPN or allowed to bypass it for direct internet access. In practice, the term covers full, inverse, and app-based split tunneling patterns, although definitions vary across vendors and remote access stacks. The security question is not whether split tunneling exists, but which traffic classes are exempted, under what policy, and how that decision is monitored.
For NHI Management Group, the key distinction is that split tunneling changes the trust boundary of a remote endpoint. When traffic leaves the VPN, it may avoid enterprise inspection, logging, DNS controls, or data loss policies. That makes the configuration especially sensitive in environments handling secrets, identity workflows, admin consoles, or agentic AI tooling. The most common misapplication is enabling broad traffic exceptions for convenience, which occurs when organisations treat split tunneling as a performance setting rather than a risk decision.
Examples and Use Cases
Implementing split tunneling rigorously often introduces policy complexity, requiring organisations to weigh user experience and bandwidth savings against inspection coverage and attack surface reduction.
- A remote worker sends SaaS collaboration traffic directly to the internet while keeping internal application access inside the VPN to reduce latency.
- A security team blocks direct access for privileged admin tools so they continue to traverse the VPN, while allowing low-risk public browsing to bypass it.
- A developer endpoint uses split tunneling for package downloads and cloud documentation, but routes source control, secrets stores, and identity portals through the tunnel.
- An organisation disables split tunneling for finance users after discovering that direct traffic bypassed web filtering and reduced visibility into phishing delivery paths.
- In a hybrid environment, VPN policy is combined with endpoint posture checks so only managed devices can use bypass rules for selected applications.
For broader governance context, NIST Cybersecurity Framework 2.0 is useful for framing how remote access choices affect protective and monitoring outcomes across the environment.
Why It Matters for Security Teams
Split tunneling matters because it can quietly undermine the assumptions behind secure remote access. If a device can reach the internet outside the VPN, then DNS filtering, content inspection, traffic logging, and data controls may no longer apply uniformly. That creates inconsistent security enforcement, especially when users move between corporate apps, personal browsing, and sensitive identity systems on the same endpoint.
This becomes more consequential where privileged access, NHI credentials, or agent-based workflows rely on stable inspection and policy enforcement. A bypass path can expose authentication portals, secrets managers, or orchestration interfaces to unmonitored network conditions, which complicates incident response and forensic reconstruction. Security teams also need to consider whether split tunneling aligns with the organisation’s broader zero trust and access governance model, rather than treating it as a standalone VPN preference.
Organisations typically encounter the operational cost of split tunneling only after a leakage, bypass, or investigation gap, at which point the routing policy becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207), NIST SP 800-63 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | PR.AC-4 | Split tunneling changes how remote access and routing enforce least privilege. |
| NIST Zero Trust (SP 800-207) | SP 800-207 | Zero trust architecture requires policy-driven access, not implicit trust in a tunnel path. |
| NIST SP 800-63 | IAL/AAL guidance | Remote access assurance depends on device and authenticator confidence for sensitive sessions. |
| NIST SP 800-53 Rev 5 | AC-4 | Information flow enforcement governs what traffic may leave the protected boundary. |
| OWASP Non-Human Identity Top 10 | NHI sessions and secrets access can be exposed when traffic escapes tunnel controls. |
Limit which traffic may bypass the tunnel and review remote access exceptions as access control decisions.
Related resources from NHI Mgmt Group
- How do security teams know whether split tunneling is still undermining CUI protection?
- When is a reverse proxy better than a VPN for access control?
- How should security teams split identity governance from implementation work?
- How should security teams replace VPN trust with zero trust access controls?
