It’s been a while since I’ve blogged, but I wanted to expand a bit on how Software Defined Perimeter technology works. The key reason that this technology helps reduce the network attack surface is that before SDP is deployed onto a host, the default TCP/IP stack will automatically strip, parse and process all headers/packets and then send payloads up to the Application Layer for reciept. In an SDP implementation, application connectivity is only provided once the user and device is authenticated and trust is established. This means that traditional attacks that rely on the default-trust flaws built into traditional TCP/IP will be thwarted when using SDP because any non-SDP trusted traffic is discarded prior to stack processing. SDP is not a panacea, but does provide a significant improvement for trusted system access and it tightly couples ubiquitous encrypted network access to applications. The down-side of other offerings that deliver similar functionality is the complexity and lack of ubiquity across many environments, especially where you don’t own the underlying infrastructure (for example public clouds & external hosted environments). Technology providers that play in the networking space should take notice of SDP and its implications. Gartner clients that have questions related to SDP can have an inquiry with me as part of their Gartner subscription.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.