VPN Encryption and IP Protection: TLS/SSL and IPSEC

A few years back, VPNs were secured using the Secure socket layer (SSL) by providing end-to-end-encryption between a server and a client. Commonly, it creates an encrypted connection between a browser and a web server. Further, the created link ensures the data being communicated is secure enough and certifies that a user is connected to the correct server. Transport Layer Security (TLS) has replaced the SSL as it minimizes the vulnerabilities found with the SSL protocol. The SSL/TLS handshake creates a secure tunnel that ensures the security and confidentiality of the data being communicated by detecting changes in one place. On the other hand, Internet Protocol Security (IPsec) is a structure that formulates the protection of IP traffic on the network layer. The framework has four major features that include anti-replay, authentication, integrity, and confidentiality. 

VPN encryption alters data in a given network by securing it with a specific key that enables user encryption and decryption from a VPN server. This applies in both incoming and outgoing data and thus a limit to any unauthorized persons. Varying types used in securing the VPNs are differentiated from encryption strength, management of keys, interfaces used, OSI types, conveniences in deployment, and performance. In my opinion, the SSL/TLS is my preferred handshake. First, IPsec connections demand a pre-shared key from the client and server to secure and send traffic between the two parties ( Gero et al., 2017) . This creates an opportunity for attackers to crack the pre-shared key. SSL VPNs are exceptional in this problem as they use public-key cryptography to exchange traffic. More so, SSL/TLS requires more regular patch updates for the convenience of the client and server. IPsec VPNs travel in UDP packets and specifically UDP 4500 of which is a transversal problem that does not allow the efficacy of bypassing firewalls while the SSL/TLS handshake can allow traffic over port 443 which ensures a go-around for firewall. 

Reference 

Gero, C. E., Shapiro, J. N., & Burd, D. J. (2017).  U.S. Patent Application No. 15/390,587 .