CISSP 8.1 - Secure Design Principles (Part 3 of 3)

This episode of the ISC2 Certified Information Systems Security Professional (CISSP) exam prep series closes the secure design principles topic in Domain 3 by rethinking where trust lives in a modern network. It covers zero trust and the dissolved perimeter, microsegmentation, air-gap isolation, the trust-but-verify comparison, privacy by design, and secure access service edge.

Frequently Asked Questions

What is zero trust, and why did the old perimeter fail?

Zero trust means nothing and no one is trusted automatically, inside or out. The old model assumed everything inside the network was safe, which crumbled the moment an insider went rogue or an attacker slipped past the edge, and with mobile devices and cloud services the inside-outside line barely exists. Zero trust flips the assumption to never trust, always verify, and assumes a breach has already happened, so every request must be authenticated, authorized, and encrypted before access is granted.

How does microsegmentation contain a breach?

Microsegmentation slices the internal network into many small, walled-off zones separated by internal firewalls, subnets, or virtual LANs, and a zone can be as small as one high-value server. Traffic between zones is filtered, often forced to authenticate, and usually encrypted. The payoff is that a breach in one zone cannot spread sideways, so it stops lateral movement and an intruder who lands in one corner stays stuck there, like a ship built with watertight compartments.

When is total isolation with an air gap the right call?

Sometimes filtering is not enough and you need to cut a system off completely with an air gap, where a machine has no wired and no wireless link to any other system, physically severing the network path. Because wireless signals are everywhere, enforcing a real air gap can even require shielding like a Faraday cage to block stray radio. You reserve this for the most sensitive systems, because the isolation that protects them also makes them hard to use.

How does trust but verify compare to zero trust, and which one wins today?

Trust but verify is the older approach, where anyone inside the security perimeter is trusted after an initial login and then largely left alone. That standing trust is exactly what lets insiders abuse access and lets intruders move laterally once they are in. Given how fast threats evolve, a single check at the door no longer holds, so when the exam asks zero trust or trust but verify, the modern answer is zero trust, because continuous verification beats a one-time handshake.

What are privacy by design and secure access service edge?

Privacy by design builds privacy protections into a product from the very start rather than tacking them on, mirroring security by design across the whole software development life cycle and aiming to prevent violations before they happen. Secure access service edge, often shortened to SASE, merges network security functions with wide area networking into one cloud-delivered service, pushing security out to the edge near users. Its core is identity-centric, leaning on zero trust network access with multi-factor authentication and continuous monitoring.

Reference: This article is based on concepts discussed in CISSP 8.1 - Secure Design Principles (Part 3 of 3).