Picture an illustrative 300-bed private hospital. Its network grew over ten years: reception PCs, doctors’ laptops, the billing system, the lab information system, CCTV cameras, infusion pumps, the visitor Wi-Fi and a building management system, all on one large network where any device can reach any other. One morning a receptionist opens a malicious attachment. By lunchtime, ransomware has spread from that PC to the billing servers, the lab system and the backup server, because nothing stood in the way.
The attack did not need to be clever. It needed a flat network. Segmentation is the practice of dividing a network into zones and controlling what may pass between them, so that compromising one zone does not automatically mean compromising all of them.
Drawing the zones
Good segmentation starts with grouping assets by function, trust and sensitivity, not by floor or department. For the hospital, a reasonable first pass might be:
- User workstations, with clinical and administrative users possibly separated.
- Core application servers: billing, lab system, patient records.
- Medical devices, which often run old operating systems that cannot be patched.
- Building systems and CCTV.
- Guest Wi-Fi, which should reach the internet and nothing else.
- Management: the interfaces administrators use to control servers and network devices.
- Backups, isolated as tightly as possible.
Then comes the important part: writing down which zones genuinely need to talk, on which ports, in which direction. Workstations need to reach application servers on specific ports. They almost never need to reach other workstations, medical devices, or the backup system directly.
VLANs separate; they do not protect
The usual building block is the VLAN, a way of splitting one physical switch infrastructure into several logical layer 2 networks. Devices in different VLANs cannot talk directly; their traffic has to go through a router or layer 3 switch.
Here is the common mistake. Many networks create neat VLANs, then let the core switch route freely between all of them. The diagram looks segmented, but any device can still reach any other, just with one extra hop. Segmentation only becomes a security control when traffic between zones passes through a point that enforces policy: a firewall, or access control lists on the routing device that implement the allowed-flows list.
VLANs also have their own weaknesses if switches are misconfigured, such as attacks that try to hop between VLANs by abusing trunk negotiation or double tagging. Standard switch hardening, like disabling automatic trunk negotiation on user ports and not using the default VLAN for user traffic, closes these off.
The DMZ: a buffer for things the internet must reach
Some systems must accept connections from the internet: the public website, an appointment booking portal, a mail gateway. A demilitarised zone (DMZ) is a segment for exactly these. The firewall allows internet users into the DMZ on specific ports, allows DMZ servers to reach a minimal set of internal services, and blocks everything else.
The logic is that internet-facing servers are the most likely to be compromised. When one is, the attacker lands in a zone that has narrow, monitored paths inward, rather than directly inside the internal network. A well-designed booking portal in the DMZ talks to an internal API on one port, not to the database server on every port. Many cloud architectures express the same idea with public and private subnets.
Microsegmentation: walls around every workload
Traditional segmentation creates a handful of large zones. Inside each zone, everything still trusts everything. Microsegmentation narrows the zone to individual workloads or applications. Policy is enforced close to each server, through host firewalls, hypervisor-level controls, cloud security groups attached to each instance, or network policies in Kubernetes.
Rules are usually expressed in terms of labels rather than IP addresses: “web tier of the booking app may reach the API tier of the booking app on 8443”. When a new server is added with the right labels, it inherits the right policy automatically.
The benefit is fine-grained containment. The cost is complexity. You need an accurate map of application dependencies, and getting that map wrong breaks applications. Most successful projects start in monitoring mode, observing flows for weeks before enforcing anything, and begin with the highest-value systems instead of trying to microsegment the whole estate at once.
Back to the hospital
With basic enforced segmentation, the same phishing email plays out differently. The receptionist’s PC is infected. The ransomware tries to spread to neighbouring workstations, but workstation-to-workstation traffic for file sharing and remote administration is blocked. It tries to reach the backup server, but only the backup software’s dedicated service accounts and ports are allowed from the server zone, not from user PCs. It can reach the billing application on its web port, as any user can, but that alone does not let it encrypt the server. The incident is one PC, not a hospital-wide shutdown.
Segmentation is not a guarantee. An attacker with stolen administrator credentials can use allowed management paths. That is why the management zone deserves the strictest controls of all, with access only through hardened jump hosts and strong authentication.
Segmentation also shrinks compliance scope
Beyond containment, segmentation has a business benefit. Standards such as PCI DSS apply their full requirements to systems that store, process or transmit card data and to systems connected to them. A company that isolates its payment environment properly can limit the assessment to that segment. A company with a flat network may find its entire estate in scope. Well-known breaches, such as the 2013 Target incident, which began with credentials stolen from a refrigeration and HVAC vendor, illustrate what happens when third-party access paths are not separated from payment systems.
Written by the RP Strativa Team. The hospital and its network are illustrative.
Leave a Reply