Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
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.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.