Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Microsegmentation?

Microsegmentation enforces access policy at the individual workload rather than at a network boundary, so a compromised server cannot reach anything it has no business reaching.

Illustration for the cybersecurity term Microsegmentation
Home / Blog / Cybersecurity Terms / What Is Microsegmentation?
17 November 2026

What Is Microsegmentation?

What Is Microsegmentation?

Traditional network segmentation divides an estate into zones and puts a firewall between them. Inside a zone, everything talks to everything. That design is why an attacker who lands on one web server in the DMZ can usually reach the other fourteen, and why ransomware spreads across a server VLAN in minutes. Microsegmentation moves the policy decision down to the individual workload: each virtual machine, container, or process gets its own allow list, and traffic that is not explicitly permitted is dropped, including traffic between two servers on the same subnet.

How Policy Is Expressed and Enforced

The important shift is that policy stops referring to addresses. A rule reads something like “workloads labelled role=web, env=prod may reach workloads labelled role=api, env=prod on TCP 8443”, and the platform resolves those labels to whatever addresses currently exist. An autoscaling group that doubles in size inherits the policy automatically; a rule written against a /24 would not.

Enforcement happens in one of several places, and most real estates use more than one.

Why It Is Worth the Effort

The measurable benefit is blast radius. In the 2017 NotPetya outbreak, organisations lost entire global estates because once the malware had credentials it could reach every Windows host on the network. Flat internal connectivity is still the normal finding in internal penetration tests: a tester who compromises one workstation can usually reach management interfaces, database ports, and backup servers directly.

There is a compliance angle too. PCI DSS reduces scope to the systems that handle cardholder data plus anything connected to them; microsegmentation makes that boundary precise and evidenced rather than architectural and arguable. For organisations working towards zero trust under NIST SP 800-207, per-workload policy is the network half of the model.

Getting It Wrong Is Easy

Projects fail in predictable ways. Teams start by writing rules before they know what talks to what, and discover an undocumented dependency at the worst possible moment. They apply policy to everything at once rather than to one application at a time. They allow any on a few ports “temporarily” and never revisit it. Or they build thousands of rules that nobody can reason about and nobody dares remove.

The sequence that works is deliberate.

  1. Observe first. Deploy the enforcement layer in visibility-only mode and collect flows for several weeks, covering month-end and any batch cycles. Every platform supports this, and skipping it is the single most common cause of outages.
  2. Label properly. Policy quality depends entirely on metadata quality. Agree a labelling scheme for application, role, and environment, and pull it from your CMDB or tagging standard rather than inventing it per project.
  3. Start with ring-fencing. Before writing fine-grained rules, isolate each application so it cannot talk to other applications. This delivers most of the containment benefit for a fraction of the rule count.
  4. Then tighten within. Restrict tiers inside the application, and block east-west management protocols such as SMB and RDP between workstations, which is where lateral movement usually begins.
  5. Run it in test mode before enforcement, and keep the alerting on denied flows so a missing rule surfaces as a ticket rather than an incident.

The Ongoing Cost

Be honest about this in the business case. Microsegmentation is a lifecycle, not a project: every new application needs policy, every change needs review, and policy that drifts from reality becomes either an outage or a set of rules so permissive they achieve nothing. Budget for the operating model, integrate policy into the deployment pipeline so it ships with the application, and review denied-flow data regularly.

Our Infrastructure and Architecture Review Services map existing east-west exposure and define a segmentation target that can actually be maintained.

FAQ – Frequently Asked Questions

How Is Microsegmentation Different From VLANs?

VLANs separate broadcast domains and are enforced by switches and a firewall between zones, so anything inside a VLAN communicates freely. Microsegmentation enforces policy at each workload, including between two machines on the same VLAN. It also follows the workload when it moves or scales, because rules reference labels rather than addresses.

Will Microsegmentation Break My Applications?

It will if you enforce before you understand the traffic. Every platform supports a visibility-only mode; run it for several weeks including month-end and batch cycles, build the policy from observed flows, then test in simulation mode before enforcing. Keep alerting on denied connections afterwards so a missing rule appears as a ticket rather than an outage.

Do I Need a Dedicated Product?

Not always. Cloud security groups, Kubernetes NetworkPolicy, and host firewalls managed by configuration tooling can deliver ring-fencing at no licence cost. Dedicated platforms earn their place in large, mixed estates where you need one policy model across virtual machines, containers, and physical servers, plus dependency mapping and policy lifecycle management.

Where Should I Start?

Ring-fence applications from each other before attempting fine-grained rules inside them, because that step delivers most of the containment value for a small fraction of the rules. Then block east-west management protocols such as SMB and RDP between user workstations, which removes the path most lateral movement uses. Tighten within applications afterwards.

Related Terms

You May Be Interested In These

What Is DPoP?

Cybersecurity Terms

17 November 2026

What Is DPoP?

Read More
What Is a Honeypot?

Cybersecurity Terms

5 July 2021

What Is a Honeypot?

Read More
What Is Access Card Cloning?

Cybersecurity Terms

17 November 2026

What Is Access Card Cloning?

Read More