Course contentsShow
← Security
Lesson 2685 of 3,05250. Secure Architecture and DesignFree lesson

Software-Defined Perimeter and Identity-Based Segmentation

Understand software-defined perimeters, identity-based micro-perimeters, and moving from network-centric to identity-centric controls.

Software-Defined Perimeter and Identity-Based Segmentation

What you'll learn: How software-defined perimeters shift security from network-centric to identity-centric controls by creating dynamic, per-user micro-perimeters.

From Castle Walls to Personal Bodyguards

Traditional networks rely on network-centric segmentation—VLANs, firewalls, and IP-based rules that ask "where is this request coming from?" Software-Defined Perimeter (SDP) flips this approach by asking "who is making this request?"

Think of it like upgrading from castle walls (protecting everyone inside equally) to personal bodyguards (protecting each individual based on their specific identity and context).

What is Software-Defined Perimeter?

SDP creates an identity-based micro-perimeter around each resource. Before any network connection is established:

  1. Authentication happens first (not after network access)
  2. Authorization determines visibility (users can't even see resources they're not entitled to)
  3. Dynamic tunnels are created on-demand between verified identities and specific resources

This approach makes infrastructure "dark" to unauthorized users—it simply doesn't respond to unauthenticated connection attempts.

Identity-Based Segmentation

Unlike traditional segmentation based on IP ranges or VLANs, identity-based segmentation enforces access control using:

  • User identity (who you are)
  • Device posture (security state of your endpoint)
  • Context (location, time, risk score)
  • Application identity (service-to-service authentication)

Each connection request is evaluated independently. Even if an attacker compromises one session, they cannot pivot laterally because network access is tied to verified identity, not network location.

Why This Matters

Moving from network-centric to identity-centric controls means trust is never based on where you connect from. Remote employees, cloud workloads, and on-premises systems are all protected by the same identity-driven policy framework—essential for Zero Trust architectures.

Key Takeaway: Software-defined perimeters and identity-based segmentation replace network location with verified identity as the primary security enforcement point, creating dynamic micro-perimeters that prevent unauthorized access and lateral movement regardless of network position.