Insufficient Network Segmentation
Internal networks are not divided into zones with controlled traffic between them, so a compromise of any one system gives an attacker direct network access to critical systems.
| Severity | High |
| CVSS 3.1 | 8 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N Open in the calculator |
| CVSS 4.0 | 5.3 CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N Open in the calculator |
| CWE | CWE-653: Improper Isolation or Compartmentalization |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1210 Exploitation of Remote Services, T1021 Remote Services |
| Category | Insecure Design |
Description
Network segmentation divides a network into zones according to the role and sensitivity of their systems, such as user workstations, servers, management interfaces, databases, payment systems and operational technology, and controls the traffic between them with firewalls or access lists so that each zone can reach only the services it needs. Where the network is flat, or zones exist but the traffic between them is not filtered, every system can reach every other.
An attacker who compromises any single device, for example through phishing, or who connects to the network, can then reach and attack every system directly, including those that hold the most sensitive data or control the infrastructure. A single vulnerability or reused credential anywhere becomes a route to critical systems, and ransomware and other malware can spread across the whole estate. The real effect depends on the weaknesses of the systems that become reachable, but the lack of segmentation removes a layer that would otherwise contain an incident and greatly extends the reach of any initial compromise.
The weakness is identified from the testing position, usually a user network port or a standard workstation, by scanning the organisation's address ranges and finding services that a user network has no need to reach: remote administration protocols such as RDP, SSH and WinRM on servers, database listeners, hypervisor and storage management, out-of-band management interfaces such as iLO, iDRAC and IPMI, network device management, backup systems, or systems in a zone that is meant to be separate. Tests of specific boundaries, such as those around a cardholder data environment, check each permitted path against the documented rules.
Remediation
- Define security zones based on the role and sensitivity of systems, and document the traffic that each needs, with its source, destination, port and business reason.
- Enforce the boundaries with firewalls or access lists that deny traffic by default and allow only the documented flows. Begin with the highest-value assets: management interfaces, domain controllers, databases, backups and any regulated or operational technology environments.
- Put administrative interfaces, out-of-band management and network device management on a dedicated management network, reachable only from privileged access workstations or jump hosts.
- Restrict workstation-to-workstation traffic, for example with host firewalls or private VLANs, since user devices rarely need to talk to each other.
- Log traffic that crosses zone boundaries, and alert on denied attempts to reach sensitive zones.
- Review the rules regularly and test the segmentation after significant changes.
Segmentation is a programme of work rather than a single change, so as an interim measure restrict access to the most sensitive systems with host-based firewalls. Confirm the fix by repeating the scan from user networks and checking that only the documented services are reachable.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.