ProcRoute: Process-Scoped Authorization of Split-Tunnel Routes
ProcRoute solves the problem of unauthorized internal route access in split-tunnel VPN/ZTNA deployments, providing a practical access-control solution for enterprise network security.
ProcRoute restricts internal-route access to explicitly authorized applications, preventing unprivileged processes from reaching internal services. In a WireGuard deployment, it matches baseline performance and is 13% faster than nftables, with 93 μs p50 connect latency, flat policy scaling to 5,000 prefixes, and sub-millisecond revocation.
In most split-tunnel VPN/ZTNA deployments, installing an internal route authorizes the entire device, not a specific application, to use it. An unprivileged malicious process can therefore reach internal services by reusing routes intended for corporate applications. We present ProcRoute, a system that restricts internal-route access to explicitly authorized applications. ProcRoute models route access as an access-control problem: application identities are principals, destination prefixes with port and protocol constraints are resources, and a total, default-deny decision function mediates every connect() and UDP sendmsg() to an internal destination. Processes without a grant retain external access but are denied internal routes under our threat model. We describe ProcRoute's formal model, a Linux prototype built on cgroup v2 and eBPF socket-address hooks, and two complementary evaluations. In a two-machine WireGuard deployment, ProcRoute matches the WireGuard baseline and 13% faster than an nftables cgroup-matching configuration, with a p50 connect latency of 93 $μ$s (+3.6 $μ$s over baseline), flat policy scaling to 5,000 prefixes, and sub-millisecond revocation. Single-machine loopback microbenchmarks confirm low hook overhead: 2.7 $μ$s on the internal-allow path, 82/82 unauthorized pivot attempts blocked, and zero transient allows across 1.2 million connection attempts during policy reload.