What is a firewall?

A firewall is the guard between a network and the outside world. It inspects the traffic trying to get in and out, and only lets through what the rules allow. For an organisation, it is often the first line of defence against external attacks.

But a firewall does not do everything. It stops unwanted network traffic, not a phishing email that an employee clicks on. Modern firewall technology also does considerably more than open and close ports, and where it is placed in the network determines how much protection it actually provides.

What a firewall does

A firewall works according to a rule base. Every packet that passes through is compared against the rules, which determine whether the traffic is allowed or blocked based on source, destination, port and protocol.

The basic principle of a well-configured firewall is deny by default. Anything that is not explicitly permitted is blocked, rather than the other way round. That way, the organisation only opens the paths that are actually needed and keeps the rest closed. The firewall is therefore a fundamental part of an organisation's IT security.

From packet filter to next generation

Firewalls have evolved in several stages. The first were simple packet filters that only looked at source, destination and port, one packet at a time.

The next step was stateful inspection, where the firewall keeps track of active connections and understands whether a packet belongs to an already approved session. Today's next-generation firewalls, NGFWs, go further. They can look inside the traffic itself, recognise which application is being used and block known attacks on the fly.

What an NGFW sees

A modern firewall does more than open and close ports. It combines several functions in a single device:

  • Deep packet inspection, which examines the content and not just the address information.
  • Application control, which distinguishes between services even when they share the same port.
  • Built-in intrusion prevention, IPS, which stops known attack patterns.
  • URL and content filtering, which blocks malicious or inappropriate websites.

It is these functions that allow an NGFW to catch what a simple port filter misses.

Hardware, software and cloud

A firewall can be a physical device in the server room, software on an individual server or computer, or a service in the cloud. They partly fill different roles.

The network firewall protects the boundary with the internet and between zones, while a host-based firewall protects a single machine. When the organisation moves systems to the cloud, the function follows, as a cloud firewall in front of the cloud services in use.

Where the firewall sits

Placement determines what the firewall can protect. The classic location is at the perimeter, between the internal network and the internet.

But a firewall is also useful inside the network. By dividing the network into zones, for example a DMZ for services accessed from outside, an organisation can prevent an attack from spreading freely once someone has got in. In sensitive environments, organisations go even further and divide the network into many small segments, so that anyone who gets into one part does not automatically reach the rest. This segmentation is part of modern network security and is something that regulations such as the EU's NIS2 Directive highlight.

What a firewall does not protect against

It is easy to think a firewall is enough. It does a lot, but it has clear limitations.

A firewall does not stop an email containing malware that an employee opens, and it rarely helps against threats that are already inside. Nor can it see into encrypted traffic unless it is configured to do so. That is why the firewall is one layer among several, not the whole defence. It works best together with wider cybersecurity measures such as antivirus, updates and trained staff.

The rule base must be maintained

A firewall is not finished once it is installed. The rules grow over time, and old openings that no one needs any more become security holes.

That is why the rule base should be reviewed at regular intervals, so that unnecessary rules are removed and logs are followed up. A firewall with hundreds of forgotten rules gives a false sense of security, because no one knows any longer what is actually open.

Choosing and setting up

Start with what needs to be protected and what the network looks like. A smaller organisation can often manage with an NGFW at the perimeter, while a larger one needs segmentation and several firewalls.

Then make sure someone owns the rule base over time. A firewall is only as good as the rules it runs, and they need to be maintained as carefully as the technology is procured.