Most business owners know they need a firewall. Fewer realize that the firewall in the office closet does nothing for the company website. The website lives somewhere else, it is open to the whole Internet by design, and anyone can send it anything.
That is the job of a web application firewall, or WAF. It is a filter that sits in front of a website and looks at every request before the site sees it. Here is what it does, what it doesn’t do, and why we put one in front of every website we host.
Why an ordinary firewall isn’t enough
A traditional firewall works like a gate with a guest list. It decides which kinds of traffic may pass: web traffic in, file sharing out, and so on. For an office, that works well.
A website has to let web traffic in, from everyone, all the time. That’s the point of having one. So an ordinary firewall waves every web request through, including the harmful ones. The attack arrives looking exactly like a visitor.
A WAF reads the contents of each request instead. Sophos describes its web server protection as protecting web servers against “application vulnerability exploits, such as cookie, URL, and form manipulation.” In plain terms: it checks what each visitor is actually asking the website to do.
What a WAF looks for
Most attacks on business websites are automated. Programs scan the Internet around the clock, trying the same tricks on every site they find. A WAF recognizes those tricks and turns them away. The most common include:
- SQL injection. Typing database commands into a search box or contact form, hoping the site will run them. A successful attempt can read or change the website’s database, including customer details.
- Cross-site scripting (XSS). Slipping a piece of code into a form or link so that it runs in other visitors’ browsers.
- Path traversal and command attempts. Asking the web server for files it should never hand out, or trying to run commands on it.
- Vulnerability scanners. Tools that probe a site, page by page, to find an out-of-date plugin or an unprotected admin page.
- Malformed requests. Traffic that breaks the rules of the web’s own protocol, which is often a sign of an attack tool rather than a real browser.
What Sophos adds
We use Sophos for our managed IT security, and a Sophos web application firewall protects the websites on our secure web hosting. According to Sophos Firewall’s documentation (checked September 2026), a Sophos WAF protection policy can include:
- Common threat filtering with checks for SQL injection, cross-site scripting, application attacks and protocol violations, at adjustable strictness levels.
- Scanner detection to spot automated tools mapping a site for weaknesses.
- Blocking clients with a bad reputation, using real-time blocklists and location data, so known sources of attacks are turned away early.
- Antivirus scanning of files uploaded to or downloaded from the site.
- Form hardening and cookie signing, which detect when someone has tampered with a web form or a browser cookie on its way back to the site.
- Data leakage protection, which keeps detailed error messages and other sensitive information from being shown to visitors.
- Browser safety headers, such as HTTP Strict Transport Security, which tells browsers to use only encrypted connections to the site.
- Request size limits, so oversized requests can’t be used to overwhelm the site.
Each rule can run in “monitor” mode, which only logs what it would have blocked, or “reject” mode, which blocks it. That matters in practice. A new website is usually watched in monitor mode first, so a legitimate feature isn’t blocked by mistake, then tightened.
What a WAF doesn’t do
A WAF reduces risk a great deal, but it is one layer, not a cure-all. It’s worth being clear about the limits:
- It doesn’t replace updates. If a plugin has a known flaw, the fix is to update or remove it. The WAF buys time and catches common attempts; it doesn’t make old software safe.
- It can’t fix a stolen password. Someone who logs in with a real admin password looks like a real admin. Strong, unique passwords and multi-factor sign-in still matter.
- It doesn’t absorb huge floods of traffic on its own. Large denial-of-service attacks are best stopped further out, by an edge network, before they reach the server.
- It needs tuning. Rules that are too loose let attacks through; rules that are too strict break contact forms and checkouts. Someone has to look at the logs.
Questions to ask about your own website
- Is anything filtering requests before they reach the site, or does every request go straight to it?
- If there is a WAF, is it blocking, or only monitoring?
- Who reviews what it blocks, and who adjusts the rules when something legitimate is caught?
- Is the site’s software, including plugins and themes, kept current as well?
If you’re not sure of the answers, our article Is your website your weakest link? explains how business websites usually get compromised, and what we found on our own websites shows why we stopped assuming someone else was watching.
How FTI helps
Our secure web hosting puts several layers in front of every website: the Cloudflare® global edge network, which absorbs floods of junk traffic and provides encryption, a Sophos web application firewall that inspects each request, isolated environments for each site, and backups kept out of reach. Our team onboards every site, checks it for problems before it moves, and tunes the protection so it blocks attacks without blocking customers. It pairs with our managed IT services, where the same Sophos security protects your office.

