Internal source zone
A normal internal segment such as LAN, Guest, or SSLVPN starts with more access than intended.
Solutions
Use this page for east-west and boundary review: where policy paths quietly weaken the separation your network diagram says should exist.
Zone view
A normal internal segment such as LAN, Guest, or SSLVPN starts with more access than intended.
The sample report includes policies such as LAN to Guest, LAN to DMZ Access, Guest to DMZ, SSLVPN LAN Access, and IPSEC VPN LAN Access.
That broad path weakens the expected separation between internal zones, servers, guests, or remote-access segments.
ConfigSentry flags the path as Avoid broad east-west segmentation rules so engineers can review the actual policy list.
The remediation focus is to replace broad internal-zone access with dedicated source objects, destination objects, and narrower service scope.
Boundary examples
The sample policy names make it obvious how ordinary-looking internal paths can become broader than intended and undermine zone separation.
Remote-access and VPN-linked internal paths are part of the segmentation story too, especially when they become broader than their original business case.
A fully open or weakly constrained internal policy can undo the boundary design the environment is supposed to rely on.
Why this matters
Architecture diagrams do not prove the policy is still doing the right thing.
ConfigSentry helps engineers review policy paths, objects, services, and logging together so unexpected access is easier to explain.
Next step
Open the sample report if you want to inspect the finding format, or continue into Firewall Rule Review for the broader policy-quality view.