Orbit Computer Solutions
Home About Blog Contact Get in touch

What A Firewall Actually Does (Simple Explanation)

What it actually does

A firewall sits at the boundary between two networks, usually between yours and the internet, and decides what is allowed to cross. Every piece of traffic trying to get in or out is checked against a set of rules, and anything that does not match is dropped. A sensible firewall runs on a simple and slightly unfriendly principle: deny everything by default, and only allow the specific things you have chosen to permit.

That is really the whole idea. It is less a wall than a doorman with a guest list. Traffic for the services you actually run, your website answering visitors, your email coming and going, is on the list and waved through. The constant background noise of the internet, the automated scans and probes hunting for a way in, is not on the list, so it never reaches the door. Good monitoring is what turns all that blocked, invisible noise into something someone can actually review.

Why it still matters with everything in the cloud

It is tempting to assume firewalls matter less now that so much lives in the cloud. The opposite is closer to the truth: the boundary has simply moved and multiplied. There is still one around your office network, there are firewalls built into every decent cloud platform, and there is one on every laptop and server worth its salt. Each enforces the same deny-by-default rule in its own corner.

For most small businesses the firewall is the quiet workhorse behind a few things you would notice at once if they stopped: keeping the guest wifi away from the till system, stopping one compromised laptop from reaching everything else, and making sure the only ways into your network are the ones you chose (a VPN is usually one of them). Holding that perimeter is exactly what the UK’s NCSC guidance on network architecture asks for, so for many businesses it is a baseline expectation rather than a nice-to-have.

Where firewalls quietly go wrong

Firewalls rarely fail dramatically. They fail quietly, by being too generous. The classic problems are all the same theme: a rule opened up for a quick test years ago and never closed, a management page left reachable from the internet, a default setting left exactly as it shipped.

None of that shows up as an error. The firewall carries on doing precisely what it was told, which is the point. The value was never in having a firewall, since almost everyone does. It is in someone occasionally checking that its list of who gets in still matches how your business actually works today. If nobody has looked at yours in a long while, that is the part worth changing.