Table of Contents
Segmentation splits an enterprise network into isolated zones, stopping ransomware on a compromised device from reaching critical systems. This guide covers segmentation types, pairing it with detection and response, a phased rollout, and common mistakes.
Network segmentation divides an enterprise network into isolated zones so that one compromised device cannot reach everywhere. It is one of the most effective ways to limit ransomware, because modern attacks rarely stop at the first machine. Once inside, attackers look for domain controllers, backups, and file servers, and on a flat network nothing slows them down.
Segmentation on its own does not find an intruder, though. It buys time for the IT teams. This guide covers how segmentation works, which type fits which environment, how it pairs with detection and response, and how to roll it out without breaking the business.
Key Takeaways
- Segmentation limits how far ransomware can spread by forcing attackers to cross controlled boundaries.
- Microsegmentation applies policy at the workload level and is the most granular option for Zero Trust architectures.
- Containment only works if someone detects the intrusion and acts while the boundaries are holding.
- Domain controllers, backups, and OT systems should be the first assets you isolate.
- Segmentation needs continuous testing; policies drift as networks change.
What Is Network Segmentation?

Network segmentation splits a network into smaller zones, each with its own access rules. Traffic between zones passes through an enforcement point, such as a firewall or software policy engine, that decides whether to allow the connection.
The approach is central to Zero Trust. NIST SP 800-207 states that Zero Trust assumes no implicit trust is granted to assets or user accounts based solely on their physical or network location. A laptop on the corporate network is not trusted simply because it is inside the building.
For ransomware defense, the value is simple. Ransomware that lands on a marketing laptop should not be able to reach the finance servers, the backup repository, or the production line. Each boundary the attacker has to cross means new credentials, new exploits,s and another chance for your team to spot the activity.
Types of Network Segmentation
Most enterprises combine several types, layering physical and logical controls to match the risk of each environment.
|
Type |
How it isolates |
Best for |
Watch out for |
|
Physical |
Separate switches, cabling, and firewalls |
OT and IT separation, high-security zones |
Cost and slow change |
|
Logical (VLANs and subnets) |
IEEE 802.1Q tagging on shared hardware |
Department and function separation |
VLAN hopping and trunk misconfiguration |
|
Firewall-based |
Internal firewalls filter traffic between zones |
DMZs and trust-level boundaries |
Rule sets that grow into thousands of entries |
|
Software-defined |
Central controller pushes policy programmatically |
Cloud and fast-changing infrastructure |
Dependence on the controller's visibility |
|
Microsegmentation |
Policy enforced per workload or application |
Zero Trust, data centers and containers |
Mapping dependencies before enforcement |
CISA published dedicated guidance on microsegmentation in 2025, describing it as a core part of Zero Trust network architecture. It is the most granular option, but it also demands the most accurate picture of how your applications communicate. If your team lacks that expertise in-house, you can browse cybersecurity companies and read verified client reviews before choosing a partner.
How Segmentation Contains Ransomware
Segmentation works by controlling east-west traffic, the connections between systems inside your network. A policy decision point evaluates each request against identity, device health, and business rules, and a policy enforcement point allows or blocks it.
Speed is the reason this matters. Mandiant's M-Trends 2026 report found that the median time between initial access and handoff to a second threat group, often a ransomware operator, fell from more than eight hours in 2022 to 22 seconds in 2025. The same report found that global median dwell time rose from 11 days to 14 days. Attackers are moving faster while many intrusions still go unnoticed for weeks.
That combination is dangerous on a flat network. Segmentation slows lateral movement, so the attacker's 22-second advantage at the start does not turn into full encryption of the environment. What it cannot do is notice the intrusion or remove the attacker.
Pairing Segmentation With Detection and Response
Segmentation buys time; detection and response decide what happens with it. If an alert fires at 2 a.m. and nobody acts until Monday, even a well-segmented network gives the attacker two days to work through each boundary.
This is where managed detection and response (MDR) complements segmentation. An MDR provider monitors endpoint and network telemetry around the clock, investigates suspicious activity, and can isolate a compromised host before ransomware spreads beyond its zone. ESET, for example, combines AI-assisted detection with 24/7 human-led investigation and global threat intelligence, and reports a mean time to respond of six minutes, compared with 22 minutes for MDR providers on average based on their published figures. KuppingerCole named it a Market Leader in its 2026 Leadership Compass for MDR.
The two controls reinforce each other. Segmentation limits what a single compromised device can reach, and fast response removes the attacker while those limits hold. When you design segments, decide in advance what actions responders can take in each zone, especially for systems such as domain controllers or production servers where automatic isolation could disrupt operations.
Real-World Lessons: Maersk and Colonial Pipeline
In 2017, NotPetya, destructive malware that posed as ransomware, entered A.P. Moller-Maersk through a compromised Ukrainian accounting software update and spread across its global network. The company had to reinstall about 45,000 PCs, 4,000 servers, and 2,500 applications over ten days, and estimated the cost at USD 250 million to 300 million.
Recovery depended on a single domain controller in Ghana that was offline during the attack because of a power outage. A flat network let the malware reach every domain controller; isolated identity infrastructure and offline backups would have changed the recovery entirely.
The 2021 Colonial Pipeline attack began with a compromised password for a legacy VPN account that did not use multifactor authentication. The ransomware hit business IT systems, and the company shut down pipeline operations as a precaution because it could not be sure the attack would not spread to operational technology. It paid a ransom of about USD 4.4 million, part of which the Department of Justice later recovered. Strong separation between IT and OT, and confidence in that separation, is what lets an operator keep running during an IT incident.
Network Segmentation Implementation Strategy
A phased rollout reduces risk and keeps the business running, and it works best as part of wider cybersecurity strategies that also cover patching, multifactor authentication, and incident response planning. CISA's Zero Trust Maturity Model supports moving portions of the enterprise over time rather than all at once.
Phase 1: Map and baseline. Inventory workloads, applications, and data flows. You cannot write a policy for traffic you have not seen.
Phase 2: Protect critical assets first. Isolate domain controllers, backup infrastructure, OT systems, and sensitive data stores before anything else. These are the assets ransomware operators target to maximize leverage.
Phase 3: Monitor before enforcing. Run new policies in logging mode, review what they would have blocked, and fix legitimate flows before switching enforcement on.
Phase 4: Enforce and expand. Turn on enforcement zone by zone, then extend to lower-risk areas and cloud environments.
Phase 5: Validate continuously. Test boundaries after every major change. For organizations handling card data, PCI DSS v4.0 Requirement 11.4.5 requires penetration testing of segmentation controls at least once every 12 months and after any change; Requirement 11.4.6 requires testing every six months for service providers.
Common Segmentation Mistakes
- Leaving backups on the production network. If ransomware can reach your backups, it will encrypt or delete them.
- Allowing "any-to-any" exceptions. Temporary rules added during rollout often become permanent gaps.
- Ignoring identity. Segmentation that trusts any valid domain admin credential, as Maersk's network did, fails once those credentials are stolen.
- Applying static rules to dynamic environments. Cloud workloads and containers change too quickly for manually maintained IP-based rules.
- Skipping detection. Boundaries without monitoring only delay an attacker; they do not stop one.
Conclusion
Network segmentation is one of the most reliable ways to keep a single compromised device from becoming a company-wide ransomware event. Start with the assets attackers want most, move from monitoring to enforcement in phases, and test your boundaries regularly. Then make sure someone is watching those boundaries around the clock, because segmentation is most effective when a fast responder acts on the attack on time.
FAQs
Segmentation restricts lateral movement between zones. When ransomware compromises one device, policies at each boundary block it from reaching backups, domain controllers, and production systems in other segments, limiting the damage and giving defenders time to respond.
Network segmentation creates broad zones using VLANs, subnets, and firewalls. Microsegmentation enforces policy at the individual workload or application level, providing finer control and supporting Zero Trust architectures, cloud workloads, and containers.
No. Segmentation contains spread but does not detect intrusions or remove attackers. It works best alongside endpoint detection, continuous monitoring, fast incident response, multifactor authentication, and offline or immutable backups.
Start with the assets attackers target for maximum leverage: domain controllers, backup infrastructure, operational technology, financial systems, and stores of sensitive customer data.
Test after every significant network change and on a regular schedule. PCI DSS v4.0 sets a minimum of every 12 months for segmentation testing, and every six months for service providers, but many organizations test more often.
Recent Blogs
How Much Does a Search Marketing Agency Really Cost in 2026?
-
19 Nov 2026
-
6 Min
-
15
Custom Shopify Development: When a Theme Stops Being Enough and How to Scope the Build
-
19 Nov 2026
-
6 Min
-
16
How Smartphone Accessory Brands Combine Product Design and eCommerce Innovation
-
05 Nov 2026
-
8 Min
-
240