Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Network segmentation splits a network into separate zones with controlled traffic between them, so that an attacker who breaches one area cannot roam freely across the rest.

What Is Network Segmentation?
Network segmentation is the practice of dividing a network into smaller, separate zones and strictly controlling the traffic allowed between them. Instead of one large, flat network where every device can reach every other device, you create boundaries that an attacker has to cross, and each boundary is a chance to stop or detect them.
The idea mirrors the watertight compartments of a ship. A breach in one compartment should not sink the whole vessel. In the same way, a phishing infection on a reception PC should not give an attacker a direct route to your payment systems, domain controllers, or production databases.
Many of the most damaging cyberattacks of the last decade spread because networks were flat. When WannaCry struck in May 2017, it moved between machines using the SMB protocol, and parts of the NHS were badly affected partly because vulnerable systems could reach one another freely. A month later, NotPetya tore through global companies such as Maersk in a similar way, combining an exploit with stolen credentials.
Once an attacker has a foothold, lateral movement is how they turn a single compromised laptop into a full domain compromise. Segmentation does not prevent the first infection, but it dramatically limits how far that infection can travel, which is why it features in almost every serious security framework.
Segmentation can be implemented at several layers, and most organisations combine them.
Good segmentation starts with understanding what you are protecting. Build an inventory of assets and data flows, then group systems by sensitivity and function. Typical zones include user workstations, servers, management interfaces, payment systems, development environments, operational technology, and third-party connections.
Next, define which flows are genuinely needed. Rules should allow specific sources to reach specific destinations on specific ports, rather than whole subnets on any port. Administrative access deserves special attention: management interfaces and domain controllers should be reachable only from hardened jump hosts or privileged access workstations.
Finally, roll out gradually. Monitor traffic in each zone first, then tighten rules step by step to avoid breaking business processes.
Segmentation has a direct compliance benefit. Under PCI DSS, systems that store, process, or transmit card data form the cardholder data environment. Properly isolating that environment reduces the number of systems in scope for assessment, which saves both time and money. Segmentation controls must be tested regularly to prove they work, and PCI DSS requires segmentation testing at least annually (every six months for service providers).
In operational technology, the IEC 62443 standard describes zones and conduits for the same purpose, and UK operators of essential services under the NIS Regulations are expected to show how they separate critical systems.
Zero Trust takes segmentation to its logical conclusion. Rather than trusting everything inside a zone, it checks every request based on identity, device health, and context. In practice, most organisations reach Zero Trust gradually, and well-designed network segments remain one of its foundations.
The most frequent problem is segmentation that exists on paper but not in practice: “temporary” any-to-any rules that were never removed, shared management networks that connect every zone, or backup servers that can reach everything. Over time, rule sets drift. Regular reviews and penetration testing are the only reliable way to confirm that boundaries still hold.
At Privia Security, our Network Security Services test whether your segments genuinely stop lateral movement, from the attacker’s point of view.
Traditional segmentation divides the network into broad zones, such as user, server, and guest networks, usually with VLANs and firewalls. Microsegmentation applies much finer policy, often to individual workloads or applications, so that even systems in the same zone cannot talk to each other unless a rule explicitly allows it. Microsegmentation is common in data centres and cloud environments.
It will not stop the initial infection, but it can significantly limit how far ransomware spreads. If backup servers, domain controllers, and critical systems sit in tightly controlled zones, an infected workstation cannot easily reach them. That containment often makes the difference between a contained incident and a business-wide outage.
Test it. Segmentation testing, usually part of an internal penetration test, tries to reach restricted zones from less trusted ones and checks that firewall rules block what they should. Reviewing rule sets is helpful, but only active testing proves that traffic is really stopped in practice.
PCI DSS does not strictly require segmentation, but without it your entire network falls within the scope of assessment. Isolating the cardholder data environment reduces scope considerably, and if you rely on segmentation for that purpose, you must test it at least annually, or every six months if you are a service provider.
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.