Charts & data

Firewall rule hit counts

How many packets matched each firewall rule over a 24-hour window, listed in rule evaluation order.

Firewall rule hit counts

How many packets matched each firewall rule over a 24-hour window, listed in rule evaluation order.

R10 allow management accessR20 allow name resolutionR30 allow web egressR40 allow site tunnelR50 allow guest egressR60 deny server subnetR70 inspect with IDSR80 deny inbound WANR90 block peer to peerR100 default deny0500k1000k1500kFirewall rule (evaluation order)Packets matched (24 h)
Synthetic documentation data: rule counters are illustrative. A default-deny rule that matches unexpected volume usually means the rules above it are too narrow or a host is misconfigured.
Firewall rule hit counts
Firewall rule (evaluation order)Matched packets
R10 allow management access12.8k packets
R20 allow name resolution486.2k packets
R30 allow web egress1243.9k packets
R40 allow site tunnel98.6k packets
R50 allow guest egress312.5k packets
R60 deny server subnet18.8k packets
R70 inspect with IDS402.2k packets
R80 deny inbound WAN62.1k packets
R90 block peer to peer1.8k packets
R100 default deny24.4k packets

Tags

  • firewall
  • acl
  • security
  • logging

Lessons using this diagram