ZTNAs Address Requirements VPNs Cannot. Here’s Why

ZTNA overview

I recently hopped on the Lookout podcast to talk about virtual private networks (VPNs) and how they’ve been extended beyond their original use case of connecting remote laptops to your corporate network. Even in this new world where people are using personal devices and cloud apps, VPN continues to be the go-to solution for remote access and cloud access. After my conversation with Hank Schless, I was inspired to put some additional thoughts about VPN on paper.

When most organizations were forced to shift to remote work last year, they needed a quick-fix solution that would enable their remote employees to access work resources securely. For many, this solution came in the form of VPNs. However, VPNs were not designed for the bring your own device (BYOD) and cloud app use cases.

While VPNs are able to provide remote access, it may come as a surprise that they fall short when it comes to security. This is because VPNs were built for when only a small portion of your workforce wanted to work from home. They also place too much trust on the device and the user. But now, as work from anywhere continues, it is important to rethink how to provide access for your entire organization in a secure manner.

What are the challenges of a remote-first workforce?

When they first debuted twenty years ago, VPNs were the de-facto method for connecting remote workers to an organization’s data center when laptops became common. Back then, computers still used modems and services like iPass for connectivity. A VPN ran over top of services like iPass to create a “private network” and keep the transmission secure. Read more:https://bit.ly/3fV53PJ

Leave a Reply

Your email address will not be published. Required fields are marked *