Notifications
Clear all
Topic starter
10/07/2026 9:16 pm
TL;DR: Microsegmentation projects still stall because discovery, tagging, policy generation, and lifecycle upkeep are too manual to sustain at enterprise scale, even as the article cites 95% of security leaders calling segmentation key to cyber defence. Deterministic automation shifts the control model from static rule-writing to continuously maintained identity and traffic baselines, which is where the real governance challenge now sits.
NHIMG editorial — based on content published by Zero Networks: 6 Processes to Automate When Implementing Microsegmentation
By the numbers:
- Over 95% of security leaders agree microsegmentation is key to strengthening cyber defenses.
- Only 5% of organizations are microsegmenting their networks today.
- 88% of security leaders rank automated policy creation as an important factor when selecting a microsegmentation solution.
Questions worth separating out
Q: How should security teams implement microsegmentation without creating operational drag?
A: Start with automated discovery, then use observed traffic to generate a policy baseline, and finally enforce changes through simulation and staged rollout.
Q: Why do microsegmentation programmes fail when policies are based on static inventories?
A: Static inventories go stale quickly in modern environments, so segmentation built on them starts with incomplete reachability data.
Q: What breaks when internal network access is left always on?
A: Always-on internal access creates lateral movement paths that a single compromised identity can use to reach sensitive systems.
Practitioner guidance
- Map every always-on east-west path Identify internal services, admin protocols, and workload-to-workload routes that remain reachable by default, then rank them by blast radius and business criticality.
- Tie segmentation policy to live identity context Ensure policies are based on current asset state, workload role, and verified identity rather than static subnet assumptions or spreadsheet inventories.
- Automate policy simulation before enforcement Use staged rollout and sandbox testing to validate proposed rules against real traffic before moving them into production enforcement.
What's in the full article
Zero Networks' full article covers the operational detail this post intentionally leaves for the source:
- A six-part automation roadmap for discovery, tagging, policy generation, lifecycle management, and JIT enforcement.
- Implementation examples showing how automated policy simulation reduces the risk of breaking production traffic.
- A global shipping case study with environment scale, rollout scope, and operational outcomes.
- Cost and deployment claims that matter when you are evaluating whether the model fits your own environment.
👉 Read Zero Networks' article on automating microsegmentation and JIT enforcement →
Microsegmentation automation: what changes for identity teams?
Explore further
10/07/2026 9:38 pm
Microsegmentation automation is really an identity governance problem disguised as network design. Once policies depend on who or what is allowed to talk, the quality of asset discovery, account context, and lifecycle upkeep becomes the control itself. That shifts responsibility from pure network engineering into IAM, PAM, and NHI governance, where drift and exceptions are already familiar failure modes. Practitioners should treat segmentation as governed identity reachability, not just packet filtering.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to The State of Secrets in AppSec.
A question worth separating out:
Q: How do teams know whether automated segmentation is actually working?
A: Look for fewer standing paths, lower policy drift, and a visible reduction in exceptions over time. A working programme should show that discovery stays current, new workloads inherit accurate policy quickly, and access windows open only when needed. If manual fixes keep growing, the control is not yet sustainable.
👉 Read our full editorial: Automating microsegmentation changes the identity control model
