Skip to main content
Legia

IT Infrastructure & Cloud

Do You Still Need a VPN if Your Apps Are in the Cloud?

Having applications in the cloud does not automatically remove the need for a VPN. The answer depends on what has to be reached: the application for users, servers for admins, or systems in the office.

SEO and Content Specialist

3 min read

A bundle of blue network cables on a switch rack

Short answer: a VPN is no longer required just to open an application that is already in the cloud, as long as the application is protected by login and multi-step authentication. A VPN or its replacement is still used for three things: connecting the office network to the cloud network, admin access to servers and databases that must not be exposed to the internet, and internal services that have no login of their own. The rest can be replaced by a proxy that checks the user’s identity.

This question comes up whenever a company moves its systems to the cloud: a VPN was built so employees could get into the office network, and now there is no office network to get into, so isn’t it obsolete? Partly true. The full guide for remote work is in Firewall and VPN for Secure Remote Work. This article answers only one thing: once the application is in the cloud, what is a VPN still needed for.

When is a VPN no longer needed?

A VPN is no longer a requirement when access is decided by the user’s identity rather than by network location. That is the idea behind zero trust. NIST SP 800-207 states that no implicit trust is given merely because of physical or network location, and it moves the focus of protection from network segments to the resources themselves. CISA describes it as a shift from a location-centric model to per-request access with least privilege.

An example of the idea in practice: Google Cloud Identity-Aware Proxy acts as a central authorization layer for HTTPS applications, so permitted users can reach the application without a VPN. A caveat: on Compute Engine and GKE, anyone who can reach the application’s serving port can bypass IAP, so firewall rules are still needed.

Illustration: cloud migration

When is a VPN still used?

NeedVPNAvailable alternative
Servers in the cloud must talk to systems in the officeSite-to-site VPN, e.g. an IPsec tunnel between the cloud gateway and the office VPN device (Azure VPN Gateway)A dedicated connection from the cloud provider, e.g. ExpressRoute on Azure
Employees reach many internal resources in the cloud and the officeClient VPN, e.g. AWS Client VPN, with authorization rules per groupAn identity-based proxy for web applications
Admins log in to serversVPN, then SSH or RDPAWS Systems Manager Session Manager: no open inbound ports, no bastion host or SSH keys, access through IAM policies
Serving an internal application without opening portsVPNCloudflare Tunnel: outbound-only connection, no public IP address

Note that a VPN gives access to a network, not to a single application. AWS Client VPN, for example, only allows access once authorization rules have been created for specific user groups. Without narrow rules, a connected user can reach more than needed.

How to decide for your company

  1. List every system employees access and who accesses it.
  2. Separate web applications with login (layered authentication is enough, see Securing Admin Access) from admin access and systems in the office.
  3. For admin access, choose one logged route: a VPN with a personal account per person, or a managed session service. Do not open SSH and RDP directly to the internet.
  4. If office and cloud systems must connect to each other, design the site-to-site VPN and its firewall rules from the start.

In the Office Network Installation service, Legia installs and configures firewalls and VPN for access from outside the office. The rules are agreed beforehand and the configuration is handed over in the documentation. The full picture of this pillar is on the IT Infrastructure & Cloud page.

Sources

Category IT Infrastructure & Cloud

Keep reading

Related articles

All Articles