Join our Newsletter — 33% off our NHI Course

Why does microsegmentation still stall across hybrid cloud?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Microsegmentation remains hard to deploy and govern consistently across hybrid environments because topology-based policy depends on firewall rules, ACLs and VLANs, according to NetFoundry’s report with Omdia’s technical review. Identity-based policy can narrow lateral movement by shifting control to verified workload identity.

Editorial analysis by NHI Mgmt Group, based on content published by NetFoundry: “Omdia Technical First Look”.

By the numbers:

  • Only 24% of organisations have deployed microsegmentation extensively.

Key questions

Q: Why does identity-based segmentation reduce lateral movement risk for workloads?

A: Because it only permits connections between identities that policy explicitly allows, rather than between anything on the same subnet.

Q: How do security teams know if identity-based segmentation is actually working?

A: Teams should test whether a compromised or simulated compromised host can reach anything beyond the minimum required set of services.

Q: What breaks when cloud microsegmentation is still tied to IP addresses?

A: Static IP-based segmentation breaks when workloads scale, relocate, or disappear faster than policy updates can keep up.

Practitioner guidance

  • Inventory workload and AI agent identities Map which services, APIs and agents currently rely on IP-based reachability so you can identify where policy will break as infrastructure changes.
  • Shift segmentation policy to identity tags Define approved connections by cryptographic identity and service role, not by subnet, firewall zone or static address block.
  • Test immediate revocation paths Remove a single identity attribute from a non-production workload and confirm that access stops without waiting for firewall propagation or route changes.

Bottom line: Microsegmentation remains valuable, but topology-based policy makes it harder to deploy and govern consistently across hybrid environments.

Glossary terms: Identity-based Microsegmentation, Lateral Movement, Cryptographic Identity, Outbound-only connectivity

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 2 weeks ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Microsegmentation fails as a network-control project when the real problem is identity governance. The report shows that deployment complexity, not lack of intent, keeps many organisations from using segmentation extensively. When controls depend on firewall rules, ACLs and VLANs, the policy surface becomes too brittle for modern hybrid environments. The practitioner takeaway is that segmentation should be governed as an identity problem, not treated as another network tuning exercise.

A question worth separating out:

Q: What is the difference between network segmentation and identity segmentation?

A: Network segmentation limits where traffic can move, while identity segmentation limits what an identity can do and which resources it can reach. Both matter, but identity segmentation is critical for NHIs because a compromised token or service account can move through authorised paths even when the network is segmented.

👉 Read our full editorial: Identity-based microsegmentation narrows lateral movement in hybrid cloud


This post was modified 2 weeks ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.