← Back to news 07.11.2026

A firewall rule without hits is a candidate, not proof

Hit counters show which firewall rules have let nothing through for months. That is the best starting point for a clean-up, but not a verdict: emergency paths, quarterly jobs and shadowed rules also have zero hits. How to turn the list into a decision.

Yesterday, the Quiet work series was about the ones who delete a firewall rule instead of adding the next one. The practical question behind it: which rules are candidates in the first place? Most firewalls count how often a rule was hit. A rule with zero hits for half a year looks like a clear case.

It often is. But not always.

What zero hits can mean

  • The emergency path. A rule for replication to the alternate data centre or for access by the recovery service provider is only needed in an emergency. Zero hits here means: there was no emergency. Once deleted, it is only missed when there is one.
  • The rare job. Year-end closing, the quarterly report, the transfer to an authority once a year. An observation period of 90 days is too short for such rules.
  • The shadowed rule. If a broader rule further up allows the same traffic, the more specific one below never gets a hit. The problem is then not the unused rule, but the overly broad one above it.
  • The reset counter. Depending on vendor and version, a reboot, an update or a newly installed rule set resets the counters. Zero hits since yesterday says nothing. Before any verdict, clarify since when counting has been going on.
  • No number is not zero. If a device delivers no counters at all, the rule is not unused but unassessed.

What the sources require

The previous IT-Grundschutz Kompendium required the allowlist approach and documented reasons for each rule in NET.3.2.A2, documentation of all rule set changes in NET.3.2.A14 and a regular review of the firewall structure in NET.3.2.A24. The Grundschutz++ user catalogue adds in DET.4.4 that changes to security policies, including their activation or deactivation, should be monitored, and names firewall rules explicitly as an example.

Together, this makes a process, not a delete command: whoever removes a rule needs a reason, documentation and a trail.

From the list to a decision

  • First the period. Since when has the device been counting? For rules with a known annual rhythm, wait at least twelve months.
  • Then the owner. Every rule needs someone who can say what it is for. If there is nobody, that is already a finding.
  • Then the check against the emergency plan. Rules that appear in the recovery plan are not judged by hit count but tested at the next exercise.
  • Then deactivate, do not delete. Switch off, note date and reason, wait for a period. If nobody gets in touch, delete.

How isidaten handles this

In firewall management, isidaten shows, across all active firewalls of a tenant, the rules without hits and the rules whose last hit is older than an adjustable threshold, 90 days by default. Rules for which a device delivers no counters do not count as unused but are listed separately as "no telemetry".

The test question

How many rules on your firewall had not a single hit in the past year, and how many of them are in your emergency plan?

If the second number is unknown, the first is not yet a deletion list.

Sources

BSI, Grundschutz++ user catalogue (German), as of 29 October 2026, DET.4.4 changes to security policies (CC BY-SA 4.0). Previously: IT-Grundschutz Kompendium, Edition 2023, NET.3.2 Firewall (German), requirements NET.3.2.A2, NET.3.2.A14 and NET.3.2.A24.

The Quiet work episode: To the ones who delete a firewall rule instead of adding the next one.

Matching solution isidaten for BSI IT-Grundschutz

Questions about this update?

Talk to us – we are happy to show you this feature in a demo.