01 / The challenge
The challenge
John Miller appears in a deny rule. Yet an earlier rule allows the IT group he belongs to. Without that membership information, the exception appears to protect the access. Linking the policy, directory and evaluation order reveals why it does not have the intended effect.
02 / How SECNOLOGY helps
How SECNOLOGY helps
Connect configuration and identities
Expand objects, network groups and services. Where the policy uses Active Directory groups, also connect access roles, groups and members: a group name becomes a set of users to examine.
Understand the effect of each rule
Compare sources, destinations, services and actions in rule order. Identify a deny already covered by an allow, or a conflict affecting only some members of a group.
Prepare a well-founded change
Reports identify the rules and objects to review. Network and security teams gain a shared basis for deciding whether to move a rule, review a membership or narrow an exception. Any change must be validated before it is applied.
03 / Useful data sources
Useful data sources
- Firewall configuration, objects, services and rule order
- Access roles and groups used by the policy
- Active Directory memberships where rules depend on identities
04 / What you get
What you get
- Shadowed rules and conflicts, including partial ones
- The objects and users affected by each analyzed inconsistency
- A report to prioritize reviews and explain changes
Planning your deployment
Scope depends on the vendor and configuration format. Fortinet and Check Point workflows address specific configurations; analysis involving AD groups requires access to relevant directory information. The evaluation model and policy layers must be considered for each environment.
