Topic starter
10/07/2026 9:11 pm
TL;DR: Zero Trust often stalls when teams try to secure everything at once, but the Navy and DHS found progress by defining a protect surface and building controls around specific assets, according to Illumio. The shift matters because operational focus, not framework adoption, is what turns Zero Trust into measurable governance.
Editorial analysis by NHI Mgmt Group, based on content published by Illumio: “How the U.S. Navy and Department of Homeland Security Made Zero Trust Work”.
Key questions
Q: How should teams implement Zero Trust around a protect surface?
A: Start with one asset, application, or data set that would create mission impact if compromised, then define the identities, flows, and conditions that govern access to it.
Q: What do teams get wrong when they try to roll out Zero Trust too quickly?
A: The common mistake is trying to transform the entire environment at once.
Q: What are the signs that a Zero Trust programme is still immature?
A: Common signs include fragmented identity systems, heavy dependence on passwords and SMS or voice OTP, limited contextual access, and weak automation for provisioning and deprovisioning.
Practitioner guidance
- Define a protect surface for each critical service Break large environments into the smallest assets, data sets, or applications that would cause mission impact if compromised, then document them as the scope boundary for Zero Trust policy.
- Enumerate every identity that needs access List the human users, service accounts, workloads, and vendors that must touch the protect surface, then record when and why each access path exists.
- Map normal transaction flows before enforcing policy Capture how the protected resource is used in steady state so that policy rules reflect actual business flows rather than generic network assumptions.
Bottom line: Zero Trust becomes operational when teams stop treating the whole environment as the target and instead govern a clearly named protect surface.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
10/07/2026 9:34 pm
Protect surface thinking is the missing governance layer in many Zero Trust programmes. Zero Trust fails when organisations try to secure the whole estate at once because the control model has no practical unit of scope. The protect surface gives security teams a measurable boundary for identity, access, and telemetry decisions. For IAM and NHI programmes, that boundary is where policy stops being theoretical and starts governing real access paths.
A few things that frame the scale:
- 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How do organisations keep Zero Trust accountable to mission outcomes?
A: Tie the access model to the resource that would create mission failure if compromised, then assess whether the policy, monitoring, and approvals are built around that specific surface. When the protected asset is named clearly, accountability becomes easier to assign and measure.
👉 Read our full editorial: Zero Trust becomes operational when teams define a protect surface