By NHI Mgmt Group Editorial TeamBased on Zero Networks: “Research Report: The Maturing Microsegmentation Market” (July 28, 2025)

TL;DR: EMA’s survey of 145 IT and security leaders found 95% rate microsegmentation as extremely or very important for cyber defence, while automated discovery, policy creation, and MFA integration are emerging as the features needed to overcome deployment friction and improve containment, according to Zero Networks. The market is moving from niche control to operational requirement, and that changes how teams should think about lateral movement risk.


At a glance

What this is: Zero Networks cites EMA research showing microsegmentation is becoming a mainstream containment control as enterprises try to reduce attack surface and limit lateral movement.

Why it matters: For IAM, PAM, NHI, and security teams, the shift matters because containment now depends on how well identity-adjacent access paths and east-west movement are controlled in practice.

By the numbers:

  • 95% of respondents rate microsegmentation as extremely important or very important for cyber defence.
  • The report is based on survey data from 145 IT professionals, information security practitioners, and technology business leaders.

Context

Microsegmentation is the practice of limiting east-west network movement so that a compromise in one area does not automatically spread across the rest of the environment. The control has often been treated as difficult to deploy and operationally brittle, which is why many organisations delayed it even when they understood the containment value. This report argues that the market is now shifting from conceptual interest to enterprise deployment.

For identity teams, the relevance is indirect but real. Attack containment is increasingly tied to who or what is allowed to talk to critical workloads after authentication has already succeeded, which means microsegmentation sits beside IAM, PAM, and NHI governance rather than outside them. The article’s starting point is typical of the market transition: organisations want stronger containment without a heavier operational burden.


Key questions

Q: What fails when microsegmentation is not operationally maintainable?

A: The control fails when policy drift, incomplete asset discovery, and manual rule updates make segmentation too slow to follow the environment. At that point, teams may believe they have containment, but internal movement paths stay open because the policy model cannot keep pace with change.

Q: Why does microsegmentation reduce breach impact even after authentication succeeds?

A: Authentication proves that an identity or workload was accepted, not that it should reach every internal target. Microsegmentation limits the paths available after that point, so a stolen credential, compromised admin session, or abused service account cannot freely traverse the environment.

Q: How do teams know if microsegmentation is actually working?

A: Microsegmentation is working when a compromised workload cannot reach anything outside its explicit policy boundary. The best signal is not the existence of a segmentation design, but the reduction in reachable assets after compromise. If east-west traffic still flows broadly, the control is not changing attacker economics.

Q: When should organisations treat segmentation as part of identity governance?

A: When authenticated users, admin sessions, or non-human identities still have broad internal reach after access is granted. At that point, segmentation becomes the backstop that enforces least reach in the environment, especially where identity compromise would otherwise turn into lateral movement.


Technical breakdown

Why microsegmentation matters when lateral movement is the real risk

Microsegmentation narrows the network paths available after an attacker gets a foothold. Instead of assuming that perimeter control or endpoint detection will stop an intrusion, it limits east-west communication so compromise stays local. That matters because modern breaches rarely depend on a single system being opened once; they depend on movement between systems after the first access event. In practice, the control becomes part of breach containment architecture, not just a design preference. The hard part is translating asset relationships into policies that are precise enough to block spread without breaking legitimate traffic.

Practical implication: Map critical workloads and segment the paths that would otherwise let an attacker move from one trust zone to another.

Automated discovery and policy creation are the operational unlocks

The article highlights automated asset discovery, tagging, and policy creation as the features that help microsegmentation escape its legacy complexity problem. These capabilities matter because segmentation fails when teams cannot keep up with changing assets, ephemeral services, and unclear application dependencies. Manual rule creation scales poorly in dynamic environments, especially where cloud workloads and hybrid estates change faster than security teams can document them. Automation does not remove the governance burden, but it shifts effort from one-off rule building to continuous policy maintenance tied to live inventory.

Practical implication: Use automated discovery and tagging to keep segmentation policies aligned with current workloads rather than static diagrams.

MFA integration shows where segmentation intersects with identity controls

Microsegmentation is often discussed as a network control, but the report also points to MFA integration as a priority capability. That is a reminder that containment is not only about packets and subnets. If identity controls fail, segmentation still has to absorb the impact by reducing what the authenticated entity can reach. For NHI and human identity programmes, that means segmentation should be treated as a compensating boundary that limits access paths after authentication and privilege assignment. It complements identity governance by making lateral movement harder even when credentials are abused.

Practical implication: Align segmentation policy with authenticated access paths so identity compromise does not automatically become environment-wide reach.


Threat narrative

Attacker objective: The attacker aims to move from a single foothold to broader internal access, persistence, and reach across critical systems.

  1. Entry occurs when an attacker gains initial access to one host, workload, or user context inside the environment.
  2. Escalation happens when flat or weakly segmented internal connectivity allows the attacker to probe adjacent systems and expand reach.
  3. Impact follows when lateral movement is constrained enough to stop the intrusion from spreading into higher-value assets or wider parts of the network.
  • Storm-2949 Azure Breach: Storm-2949 social engineering attack turns one cloud identity compromise into full Azure tenant breach.
  • Salt Typhoon telecom intrusions 2025: Salt Typhoon breached US telecoms mainly with stolen logins, then harvested SNMP strings and TACACS/RADIUS keys to spread and persist for years.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.


NHI Mgmt Group analysis

Microsegmentation is becoming a governance control, not just a network design choice. Once organisations treat lateral movement as a containment problem rather than a post-breach investigation problem, segmentation becomes part of identity and access governance by another name. That shift matters because it forces teams to ask which authenticated identities, workloads, and service paths should be allowed to talk after the first compromise. The practitioner conclusion is that containment policy now belongs in the same strategic discussion as privileged access and workload trust.

The market is moving because manual segmentation does not survive modern change velocity. Asset churn, hybrid connectivity, and application drift make hand-built policy sets fragile. EMA’s survey signal shows that practitioners value the control, but the real inflection point is operational feasibility: discovery, tagging, and policy generation must keep pace with live environments. The practitioner conclusion is to judge segmentation products by how well they reduce policy entropy over time.

Identity compromise and microsegmentation are converging at the containment layer. Authentication alone does not stop post-login abuse, especially where service accounts, admin sessions, or machine credentials can still reach too much once accepted. Containment trust gap: this is the gap between successful authentication and constrained movement, and it is where many programmes still over-trust internal reach. The practitioner conclusion is to design segmentation as a backstop for both human and non-human identity failure modes.

Microsegmentation is now part of breach resilience architecture. The report’s emphasis on stopping lateral movement reflects a broader market reality: resilience is not only recovery speed, but also how far an attacker can travel before containment engages. That makes segmentation a board-relevant control because it changes breach blast radius, not just detection quality. The practitioner conclusion is to evaluate containment as a measurable resilience outcome, not an optional network enhancement.

What this signals

Containment is now a governance outcome, not just a network objective. As enterprises modernise segmentation, the decisive question becomes whether internal reach is constrained in ways the organisation can actually sustain. That puts policy maintenance, inventory accuracy, and exception management into the centre of breach-resilience planning.

Identity programmes should assume internal access will be abused. When privileged or non-human identities are accepted, the security model still needs to limit what those identities can reach next. The practical signal for teams is that segmentation and identity controls must be designed together, or each will overestimate the protection the other provides.


For practitioners

  • Prioritise segmentation around crown-jewel paths Start with the applications, workloads, and administrative paths whose compromise would create the largest blast radius, then segment outward from those dependencies.
  • Automate asset discovery and tagging Use live discovery to map workloads, labels, and communication patterns before policy design, so segmentation reflects current reality rather than stale inventory.
  • Tie segmentation to identity-sensitive access paths Review where authenticated users, privileged admins, and service accounts can still reach critical systems after login, and narrow those reach paths explicitly.
  • Measure containment against lateral movement tests Validate whether a foothold on one system can still traverse to adjacent tiers during red team or pen test activity, and treat success as evidence of policy failure.

Key takeaways

  • Microsegmentation is shifting into mainstream breach containment because organisations are focused on reducing blast radius and stopping lateral movement.
  • The market friction is operational, not conceptual, which is why automated discovery and policy creation matter more than segmentation rhetoric.
  • Identity governance teams should treat segmentation as a backstop for credential abuse, privileged sessions, and non-human identity reach.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack surface, NIST CSF 2.0, CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKTA0008 — Lateral MovementThe report centres on stopping east-west spread after initial access.
Recommendation — Map segmentation gaps to TA0008 and test whether a foothold can still move between trust zones.
NIST CSF 2.0PR.AA-05 — Access Permissions, Entitlements and AuthorizationsMicrosegmentation constrains what identities and workloads can reach after access is granted.
Recommendation — Apply PR.AA-05 to narrow internal reach paths and remove unnecessary east-west access.
CIS Controls v8CIS-5 — Account ManagementIdentity compromise remains a key driver of internal spread, so account governance matters.
Recommendation — Use CIS-5 to reduce the access breadth available to compromised accounts and service identities.
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeSegmentation operationalises least privilege by limiting which systems an identity can reach.
Recommendation — Enforce AC-6 to keep authenticated identities and services from reaching more than they need.
ISO/IEC 27001:2022A.8.2 — Privileged Access RightsPrivileged sessions are one of the main ways lateral movement expands after entry.
Recommendation — Review A.8.2 so privileged access does not translate into unrestricted internal reach.

Key terms

  • Microsegmentation: A network control approach that divides environments into small security zones with explicit rules between them. Its purpose is to limit lateral movement and reduce blast radius when an identity, workload, or device is compromised.
  • Lateral Movement: A post-compromise technique where an attacker uses a compromised NHI to move through a network, accessing additional systems and escalating impact without triggering detection.
  • Blast Radius: The potential scope of damage if a specific credential or identity is compromised. Identities with broad permissions have a larger blast radius and represent a higher priority for least-privilege enforcement and security controls.
  • East-west traffic: East-west traffic is communication that moves between systems inside an environment rather than entering or leaving it. In microsegmentation programmes, it is the traffic most likely to expose hidden trust assumptions and is therefore the main target for workload-level policy.

Deepen your knowledge

NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security, and secrets management. It helps practitioners connect identity controls to containment decisions across modern environments.
NHIMG Editorial Note
Published by the NHIMG editorial team on July 12, 2026.
Updated on October 13, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org