The Software Defined Perimeter (SDP) is an alternative to the traditional remote access VPN architectures we’ve been deploying for years. With users going mobile and apps leaving our data centers for the cloud it makes sense to rethink how we connect. Gartner states that by 2021 60% of enterprises will have phased out their VPN for SDP, which is massive change in such a short time.
To help you get started I’ve put together The Network Architect’s Guide to Adopting a Software-Defined Perimeter. This guide is designed to get you started on your journey to SDP by laying out the critical components and workflows including app discovery, micro-segmentation, and what happens when you’re users are on campus.
In this guide I’ll cover:
- Architectural differences between incumbent access technology and SDP
- A look at a reference architecture for deploying SDP
- The three phases to consider when adopting SDP within your company
- Pro-tips and considerations for getting the most out of your SDP deployment
Also be sure to check out Scott Bullock’s post - Understanding the SDP Architecture