Email and Cyber Security · #70
Online Firewall Rule Policy Matrix
Reviews the rule base top-down with first-match logic and flags conflicting and risky rules.
- Data is processed in your browser and not sent to a server
- Export: CSV
Tool
What does this tool do?
Rule bases that grow over years accumulate rules that never fire (shadowed) because a broader rule sits above them, duplicate rules and forgotten 'temporary' any-any permits. The tool compares rules by IPv4/IPv6 CIDR, protocol and port range and optionally shows which rule a test packet hits. It does not connect to devices or write anything.
How to use it
- Paste the rules in order as CSV:
id, action, src, dst, proto, port. Address: CIDR, IP or any; port: single, range (1000-2000) or any. - Optionally enter source, destination, protocol and port for a test packet.
- Press Run; download findings as CSV.
Fields
- Rule list (CSV)
- action: allow/permit/accept or deny/drop/reject.
- Test source IP
- Optional.
- Test destination IP
- Test protocol
- Test port
Worked example
| Input | Value |
|---|---|
| Rule list (CSV) | |
| Test source IP | 10.10.8.5 |
| Test destination IP | 10.20.6.15 |
| Test protocol | TCP |
| Test port | 1433 |
Expected result: Rule 20 exposes RDP to any source; 30 duplicates 10; 50 never fires because it is shadowed by the deny in 40; 60 is any-any. The test packet (10.10.8.5 → 10.20.6.15 tcp/1433) is denied by rule 40.
If SQL access is intended, move rule 50 above rule 40; 30 can be deleted. Rule 60 permits all remaining traffic even at the end; remove it or narrow source/destination.
Second scenario
| Input | Value |
|---|---|
| Rule list (CSV) | |
Expected result: In the IPv6 rule base rule 2 opens a 10,001-port range from any source; warning.
Method and assumptions
A rule never matches if an earlier rule fully covers it in source, destination, protocol and port: same action means 'redundant', different action 'shadowed'. Partial overlaps are not reported.
Risky ports (22, 23, 161, 445, 1433, 3306, 3389, 5900) are flagged when the source is any. The test packet is evaluated against the first matching rule from the top.
Using the result and troubleshooting
Remove shadowed rules or move them to the right position; make changes in a maintenance window with a backup. Use the device's own policy analyzer for NAT, application identification and user-based rules.
Limits and common mistakes
- Address/service object groups, zones/interfaces, NAT, schedules and application (L7) matching are not supported; expand objects into CIDRs and ports.
Frequently asked questions
Is there a default deny at the end?
The tool assumes an implicit deny at the end and shows 'no match (implicit deny)' when the test packet fits no rule. Check your device's default behaviour.
Related tools and service
- Subnet Overlap CheckerLists overlaps within the same VRF and deliberate reuse across VRFs separately.
Related service: Firewall Installation and Rule Management