← Back to news 06.11.2026 Series: Quiet work, part 6

To the ones who delete a firewall rule instead of adding the next one

Quiet work, part 6: the rule set contains a rule with the comment "temporary, project 2021". The project ended long ago, the rule still lets connections through. An admin asks around, switches it off, waits, and then deletes it. Why nobody notices, and why that is exactly the success.

Friday afternoon, the week was quiet. An admin goes through the firewall rule set, line by line, without any ticket asking for it. Rule 214 makes him stop: remote maintenance from outside to a server on the internal network, comment "temporary, project 2021".

The project was completed three years ago, the project lead has left the organisation, the service provider from back then has long been working for other customers. The rule still lets connections through every day.

He asks the business department. Nobody knows what the rule is for, but nobody dares to say it can go. So he switches it off, notes the date and the reason, and waits four weeks. Nobody gets in touch. Then he deletes it.

What happens if nobody does it

Rules are created because someone needs something. They are deleted when someone takes the trouble. That is why a rule set only grows in one direction. After a few years, it contains permissions for systems that no longer exist, for service providers no longer under contract, and for exceptions whose reason has been forgotten.

Each of these rules is an open path that nobody is watching any more. And each one makes the rule set harder to read, until nobody can say for sure what a change will do. Then nothing gets deleted any more, for fear of breaking something.

Where it is required

The Grundschutz++ user catalogue requires in ARCH.5.1 that connections between IT systems are restricted. The previous IT-Grundschutz Kompendium was more specific for firewalls. NET.3.2.A2 sets the principle: clear rules must define which connections are allowed, and all other connections must be blocked by the firewall (allowlist approach). On top of that, the decisions taken, the relevant information and the reasons for the decisions must be documented.

NET.3.2.A14 requires all changes to the rule set to be documented in a traceable way, and NET.3.2.A24 a regular review of the firewall structure for known security problems.

An allowlist is only as good as its oldest line. A rule that allows something nobody needs any more is no longer a permission, it is a leftover.

Why nobody sees it

Whoever creates a rule solves a problem, and someone says thank you. Whoever deletes a rule prevents a problem that never happens. If it works, nobody notices. If it goes wrong, someone calls immediately. That is why deleting is the less popular of the two jobs, and why it takes people who do it anyway, with a question, a waiting period and a note.

To them

To the ones who ask, when they see "temporary", how long it still applies. Who switch a rule off first, then wait, then delete it. And who leave the rule set smaller than they found it.

Sources

BSI, Grundschutz++ user catalogue (German), as of 29 October 2026, ARCH.5.1 restriction and inspection of connections (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.

In the next part: to the ones who keep the phone numbers in the emergency manual up to date. The previous part: To the ones who maintain the record of processing when nobody asks.

All parts of the series

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.