Glossary

WAF

web application firewall

Definition

A web application firewall checks web requests and blocks traffic that matches security rules.

A WAF examines web and API requests. A network firewall controls network connections more broadly; the two protect different boundaries.

A customer may include “WAF” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

A web application firewall (WAF) filters traffic to websites and web APIs. It examines request details, such as addresses, paths, headers or submitted content, and applies rules intended to block unwanted activity. It focuses on web traffic rather than every connection across a business network.

A WAF can help reject requests associated with known attack patterns or enforce limits on specific actions. Its effectiveness depends on the rules, the application's behaviour and whether all relevant traffic passes through it.

For example, a small online shop could use a WAF rule to block suspicious requests targeting its checkout application. If the original server remains directly reachable through an unprotected route, attackers may be able to bypass that filtering.

Rules need maintenance. An overly broad rule can block legitimate customers; an exception added during troubleshooting can leave a gap. A WAF also does not fix the underlying vulnerable code. Assign an owner to review blocked requests and test rule changes. Check that the application cannot be reached around the firewall. Treat it as an additional control while software faults are corrected.

Sources