View Policy Rule Usage

View the policy rule hit count data of managed firewalls to monitor rule usage in order to validate rules and keep your rule base organized.
View the number of times a Security, NAT, QoS, Policy Based Forwarding, Decryption, Tunnel Inspection, Application Override, Authentication, or DoS protection rule matches traffic to help keep your firewall policies up to date as your environment and security needs change over time. To prevent attackers from exploiting over-provisioned access, such as when a server is decommissioned or when you no longer need temporary access to a service, use the Rule Usage hit-count data to identify and remove unused rules. The policy rule hit count gives you the information to determine whether a rule is effective for access enforcement. You can reset the rule hit count data to validate an existing rule or to gauge rule usage within a specified period of time. Policy rule hit-count data is not stored on the firewall or Panorama so after you clear the hit count using the reset option, that data is no longer available.
The rule hit-count data is not synchronized across firewalls in an HA deployment so you need to log in to the each firewall to view the policy rule hit count data for each firewall.
Additionally, the policy rule usage feature provides the ability to validate rule additions and rule changes and to monitor the time frame when a rule was used. For example, when you migrate port-based rules to app-based rules, you create an app-based rule above the port-based rule and check for any traffic that matches the port-based rule. After migration, the hit-count data helps you determine whether the port-based rule is safe to remove by confirming whether traffic is matching the app-based rule instead of the port-based rule.
  1. Launch the Web Interface.
  2. Select Policies.
  3. View the policy rule usage for each policy rule:
    • Hit Count—The number of times traffic matched the criteria you defined in the policy rule. Persists through reboot, dataplane restarts, and upgrades unless you manually reset or rename the rule.
    • Last Hit—The most recent timestamp for when traffic matched the rule.
    • First Hit—The first instance when traffic was matched to this rule.
    policy-rule-hit-count-example.png

Related Documentation