Firevyzer documentation¶
Firevyzer reviews changes to firewall ACLs and tells you exactly which flows change verdict — every one, concisely summarized, with the rule responsible. No packet-by-packet guessing.
Open the app What is Firevyzer?
Start here¶
-
Getting started
Load a policy, make an edit, and read your first diff in a couple of minutes.
-
Traffic classes
The core idea: one symbolic class stands in for countless flows, and the classes together cover the entire packet space.
-
Supported formats
The ACL wire schema — addresses, protocols, ports, and actions Firevyzer accepts.
Workflows¶
-
Diff by class, with provenance
Diff two policies and get the exact classes whose verdict flips — each tagged with the rule deciding it now and the rule that decided it before.
-
Trace by traffic class
Pin a host, subnet, or port and watch how the policy actually handles it, segment by segment.
-
Firewall health
Find shadowed, redundant, or overly broad rules — and the independent blocks your policy decomposes into.
New to the model?
Everything in Firevyzer is built on traffic classes — concise symbolic sets of packets that partition the whole flow space. Read Traffic classes first and the three workflows will click into place.