The Default Remote Access Tool
Secure Sockets Layer (SSL) and Transport Layer Security (TLS) VPNs are the backbone of modern remote access. Unlike older, more complex VPN technologies, they are incredibly easy for users to operate. Most work through a simple web browser or a lightweight
client, creating an encrypted tunnel that makes a remote laptop behave as if it's right there in the office. This simplicity is why they became the default choice for businesses everywhere, allowing secure access to internal files, applications, and resources from anywhere in the world. For most organizations, they are a 'set it and forget it' utility—as long as people can connect, the job is considered done.
The Hidden Detail: Split-Tunneling
The hidden detail many engineers skip is not a flaw in the encryption itself, but in how traffic is routed. The feature is called 'split-tunneling'. When enabled, it splits a user's internet traffic into two streams. The first stream, destined for corporate resources, goes through the secure VPN tunnel as intended. The second stream, for everything else—like browsing news sites, streaming music, or checking personal email—bypasses the VPN and connects directly to the internet. The logic seems sound: it saves corporate bandwidth and can improve the user's internet performance. Why route a YouTube stream through company servers if you don't have to? But this convenience comes at a steep, often invisible, cost.
Why Convenience Creates a Major Risk
The danger of split-tunneling is that it creates an unprotected bridge between the wild west of the open internet and the supposedly secure corporate network. Imagine an employee working from a coffee shop. With split-tunneling active, their connection to company servers is encrypted. But their browsing on the public Wi-Fi is not. If they visit a malicious website or download a compromised file, that malware lands on their machine via the unprotected channel. Since the device is already authenticated to the corporate network through the active VPN tunnel, the malware can then 'pivot' and use that trusted connection to move laterally into the company's internal systems. Corporate security tools, like firewalls and web gateways, are completely blind to the initial infection because that traffic deliberately bypassed the VPN.
The 'Set It and Forget It' Trap
So why is this configuration so common? It often comes down to a mix of performance pressure and inertia. IT teams are judged on keeping remote employees online and productive, and split-tunneling reduces complaints about slow internet speeds. In many VPN appliances, it's a simple checkbox that gets enabled during initial setup and is rarely revisited. Engineers, tasked with a mountain of responsibilities, often prioritize connectivity and performance. The subtle, second-order security risk of a compromised endpoint acting as a bridge isn't as immediate as a user complaining about buffering video calls. Without a specific security audit focused on VPN architecture, this risky setting can persist for years, acting as a quiet backdoor waiting for an attacker to exploit.













