Skip to main content

Why are Virtual Private Networks and Software Defined Perimeters mutually exclusive?

Increased remote work, vulnerabilities popping up and the #killthevpn movement has the cyber security industry laser focused on the transition from VPN to SDP. Let’s start with an acceptable definition of SDP from Wikipedia: “Software-defined perimeter (SDP) framework was developed by the Cloud Security Alliance (CSA) to control access to resources based on identity. Connectivity in a Software Defined Perimeter is based on a need-to-know model, in which device posture and identity are verified before access to application infrastructure is granted.” I hope we all can agree that the “ground truth" of SDP is valid and any organizations will benefit by adopting SDP architecture and principals(including Zero Trust). How is a Remote Access VPN any different than the “Client-to-gateway” deployment model defined for SDP? “In the client-to-gateway implementation, one or more servers are protected behind an Accepting SDP Host such that the Accepting SDP Host acts as a gateway between the clients and the protected servers.” Following the model, the VPN Headend is the SDP Gateway and Radius Server(with advanced features, such as MFA/Passwordless, User/Device Trust verification and least privilege policy assignment) is the SDP Controller. The "SDP Host initiates a mutual VPN connection to all authorized Accepting Hosts" is a level of confirmation on the use of VPN as a core function of SDP. The main difference between a SDP Proxy or Gateway and a traditional RVPN is going to get down to the practicality of application protocol support. Most SDP Gateways support modern protocols, such as HTTP/HTTPS, RDP, VNC, SSH, etc, whereas VPN allow for a tunnel of any IP based traffic. Many organization across the globe have applications that cannot run in a web browser using modern protocols (e.g. thick client that directly connects to a legacy workload/application). While any security professional would agree that replacing aging infrastructure and applications should be a priority, status quo dictates that they haunt us for years to come. If an SDP architecture and strategy is dependent on modern protocols only, organizations could be missing out on some of the most important area of risk reduction and attack surface. Often I see organizations tout their new shiny security tool without incorporating the 20 year old application that is core to their business and could be hacked by a novice. To top things off, there are marketing teams across the industry hoping they can provide a self-fulfilling prophecy, by trying to differentiate and drive a wedge between SDP vs VPN. “VPNs Cannot Support Zero Trust Security” or “SDPs are very different from VPNs” just sound silly to anyone who has spent the time to understand the inner workings of both solutions and deploy them. They would be much better off showing a traditional experience (admin or user) and how their solution provides a simpler, more efficient or additional functionality that didnt previously exist. Stop providing claims that aren’t backed by example or proof points(proof is in the demo): I know a few people that preach this everyday. Final thought: If an organization cannot completely sunset their traditional IPSEC or SSL VPN, why wouldn’t the industry want to see them apply the same SDP(and zero trust) principals to that use case? I think this would be a fun debate topic.

Comments

  1. I am truly impressed by the details which you have provided regarding Network Cabling Services Houston. It is an interesting article for me as well as for others. Thanks for sharing such articles here.

    ReplyDelete
  2. After a long time, I read a very beautiful and very important article that I enjoyed reading. I have found that this article has many important points, I sincerely thank the admin of this website for sharing it. Best Network Practice Questions service provider.

    ReplyDelete
  3. I am attracted by the info which you have provided in the above post. It is genuinely good and beneficial info for us. Continue posting, Thank you. Network Cabling Services Houston

    ReplyDelete
  4. I read your post and got it quite informative. I couldn't find any knowledge on this matter prior to. I would like to thanks for sharing this article here.virtual private server

    ReplyDelete
  5. Great job for publishing such a nice article. Your article isn’t only useful but it is additionally really informative. structured network cabling services oakvilleThank you because you have been willing to share information with us.

    ReplyDelete

Post a Comment

Popular posts from this blog

Cisco Zero Trust Architecture

 As a follow up to the previous post around Zero Trust Architecture , Cisco has been delivering zero trust architectures for customers for many years. With the platform approach provided by Cisco Zero Trust organizations gain better visibility across users, devices, containers, networks, and applications, verifying their security states with every access request. Adopting this model provides a balance between security and usability. Security teams can make it harder for attackers to collect what they need (user credentials, network access, and the ability to move laterally), and users can get a consistent and more productive security experience, regardless of where they’re located, what endpoints they’re using, or whether their applications are on-premises or in the cloud. Cisco Zero Trust provides a comprehensive approach to securing all access across applications and environment, from any user, device and location. It protects the workforce , workloads and workplac...

Cisco Releases Idenity Services Engine (AKA ISE)

Introduction After years of innovation around Network Access Control, Cisco has released its next generation NAC solution: Identity Services Engine. ISE is combines existing loosely coupled devices AAA, profiling, posture and guest management - in single, scalability appliance. As part of the Cisco TrustSec solution and Cisco’s SecureX architecture for Borderless Networks, the Cisco Identity Service Engine provides a centralized policy engine for business relevant policy definition and enforcement. This policy work horse enables centralized, coordinated policy creation and consistent policy enforcement across the entire corporate infrastructure, from head office to branch office. ISE Features & Benefits Visibility: Single Platform & Pane of Glass - Let IT see who and what is on the network for advanced discovery and troubleshooting Dynamically collects & consolidates endpoint information to make adaptive policy decisions based on ‘context’ Integrates functions previously d...