VPN vs ZTNA

vpn

Since the democratization of Internet at the end of the 1990s, the VPN (Virtual Private Network) has been used by companies to provide their employees with private and secure remote access to their information systems. Nowadays deployed in many organizations, the VPN still presents some risks to the integrity of information systems. To overcome this issue, ZTNA (Zero Trust Network Access) solutions, which are much more secure, are gradually replacing the VPN within organizations.

VPN: connecting two networks of trust


The primary role of the Virtual Private Network is to make two trusted networks communicate with each other. It consists in allowing, for example, a company to connect two sites through a VPN to exchange data between their information systems. For convenience, the VPN has also traditionally been used for external access, but by definition, in this case, one site is not trusted.
The operating mode of a VPN is quite simple, a user workstation authenticates itself on a VPN server; this one will check its identity on a corporate directory and once the identity is validated, it will authorize the access to a network and thus allow the access to the various resources located on it.


The VPN is not a totally reliable solution, since the press regularly reports attacks based on its vulnerabilities, leading organizations to look for an alternative solution, the ZTNA. According to the Gartner, the ZTNA is expected to replace the VPN in companies and become the leading secure remote access solution by 2023.

ZTNA: managing access authorization at the application level


The betterWE social and community platform defines ZTNA as a security model designed to trust no one by default. It manages access authorizations at the application level and not at the network access level as does the VPN.
From an architectural point of view, the ZTNA is based on two bricks; the first one being a mediation server and the second one, the gateway server(s), which will be as close as possible to the applications and resources which we want to provide access to. First, the gateway connects to the mediation server, indicating that it exists, that it can be contacted and the resources which it can give access to. The user will authenticate himself on this mediation server which will check his identity on a company directory. Once this identity is validated, the user will view a list of applications to which he can request access. When he requests access to an application, the mediation server contacts the gateway to authorize a communication flow to it and the gateway will establish the session with the application and not with the network.



VPN vs ZTNA


The ZTNA architecture is therefore much more secure than the VPN architecture. The VPN provides access to a network, whereas the ZTNA provides access to an application or resource, allowing a granularity of access. Concerning the traceability, the VPN allows to know who logs in but once a person is connected, there is no information about his or her actions whereas the ZTNA allows to know who logs in to which resources and possibly to go further by interconnecting in a transparent way with a PAM (Privileged Access Management) tool, which is not possible with a VPN.
The ZTNA also allows to very quickly provide access to applications, declare new accesses and assign these new accesses. They can be assigned without necessarily having a local agent on the user’s workstation. The ZTNA will allow a very precise conformity check, much more granular than with a VPN. Finally, if the VPN manages the primary authentication (the account used to authenticate to the VPN to enter) the ZTNA will also manage the secondary authentication, i.e. the accounts that are used to access applications and resources.

 VPNZTNA
ArchitectureSimple barrierDouble barrier
ArchitectureMono siteMulti sites
AccessNetworkApplication/resource
TraceabilityWho logged inWho logged in to what
TraceabilityNot interconnectable with PAMTransparent interconnection with PAM
AdministrationNo application declaration and complex access assignmentApplication declaration and fast access assignment
AgentNecessaryAccess possible without an agent
Conformity checkSimpleGranular
Authentication managementPrimary Authentication ManagementPrimary and Secondary Authentication Management

Do not miss these events: