Broad rule scope
The sample report shows concrete rules where source, destination, and service are wider than the policy intent suggests.
Solutions
Use this page for policy-level review: broad rule scope, linked object and service expansion, and the evidence engineers need to justify cleanup.
Policy view
What this page is really about
The sample report shows concrete rules where source, destination, and service are wider than the policy intent suggests.
Rule meaning depends on the related address objects and service definitions, so review has to follow those links instead of reading one line in isolation.
The useful output is not just that a rule exists, but why it is risky and what engineers need to narrow or remove safely.
Why this matters
Manual rule review is slow because the real risk often depends on groups, services, interfaces, and business exceptions.
ConfigSentry helps engineers review the policy together with the linked objects, services, and logging behaviour.
Next step
Open the sample report if you want to see the finding format, or continue into Network Segmentation for the east-west boundary view.