Get fresh insights, pro tips, and thought starters–only the best of posts for you.
Site-to-site VPN is a network-to-network VPN connection that securely links two or more private networks over the internet or another untrusted network.
It is commonly used to connect headquarters, branch offices, data centers, and cloud environments so users and systems at each location can reach approved internal resources without exposing traffic directly to the public internet.
A Site-to-site VPN uses VPN gateways, usually firewalls, routers, cloud gateways, or dedicated VPN appliances, at each network edge. These gateways authenticate each other, negotiate encryption settings, build an encrypted tunnel, and route selected traffic between the connected networks.
Most deployments use IPsec with IKE for authentication and key exchange. Administrators define routes, allowed subnets, encryption parameters, failover options, and logging so the tunnel carries only trusted business traffic.
| VPN component | Role |
| Gateway | Terminates the tunnel, authenticates the peer gateway, and applies encryption and routing policies. |
| Tunnel | Encrypts traffic between trusted networks so data is protected while crossing public or shared infrastructure. |
| Routing rules | Decide which subnets, applications, and traffic flows are allowed to use the secure connection. |
A Site-to-site VPN connects entire networks, so users usually do not launch a VPN client individually. Once traffic matches the configured route, the gateway handles the encrypted connection in the background.
A remote access VPN connects one user or device to a private network. It is better for mobile employees, contractors, and work-from-home scenarios, while site-to-site connectivity is better for persistent links between offices or cloud networks.
Hexnode does not replace the network gateway that terminates a site-to-site tunnel. It supports the endpoint side of the architecture by helping IT teams keep managed devices compliant, visible, and ready to use trusted network services.
With Hexnode UEM, teams can enforce security policies, deploy certificates and VPN profiles where applicable, monitor endpoint compliance, manage applications, run patch workflows, and trigger remote actions. This reduces the chance that unmanaged or noncompliant devices become the weak point behind a trusted tunnel.
Organizations should use a Site-to-site VPN when two trusted networks need continuous, encrypted connectivity. Common use cases include branch-to-headquarters access, cloud migration, backup replication, shared enterprise applications, and partner network integrations with strict routing rules.
It is less suitable when access must be limited to individual users, unmanaged devices, or highly granular application-level permissions. In those cases, remote access VPN, zero trust network access, or per-app VPN may offer tighter control.
Most enterprise deployments use IPsec with IKEv2 because it supports strong encryption, mutual authentication, and interoperable gateway-to-gateway tunneling.
Yes. Many cloud providers support VPN gateways that connect on-premises networks to virtual private cloud networks for hybrid workloads and migration projects.
No. The tunnel protects traffic between networks, but endpoint compromise, weak credentials, missing patches, or excessive permissions can still create risk inside the trusted environment.