Security · 6 min read · 19 November 2026
What Is a Web Application Firewall (WAF)? How It Differs From a Network Firewall
What a web application firewall does, the attacks it stops (SQL injection, XSS, bots), how it differs from a network firewall, deployment options and how to tune it without blocking real users.
A web application firewall (WAF) inspects HTTP and HTTPS requests to websites, APIs and portals, and blocks attacks hidden inside them, such as SQL injection, cross-site scripting and malicious bots. A network firewall decides which connections may reach a server; a WAF decides which requests inside those connections are safe.
WAF vs network firewall
| Network firewall | Web application firewall | |
|---|---|---|
| Looks at | IP addresses, ports, protocols, sessions | HTTP requests: URLs, headers, parameters, bodies |
| Stops | Unwanted connections, port scans, many intrusions | Injection, XSS, file inclusion, credential stuffing, bad bots |
| Protects | Whole networks and servers | Specific websites, APIs and web portals |
| Needs | Rules per network and service | Rules per application, plus TLS inspection |
What a WAF stops
- Injection: SQL, command and template injection in form fields and API parameters.
- Cross-site scripting (XSS): scripts injected into pages other users will load.
- Broken access and path traversal: requests for files and admin paths that should not be public.
- Bots and abuse: credential stuffing, scraping and brute-force logins, with rate limits.
- Known vulnerabilities: virtual patching for a published flaw until the application is updated.
How WAFs are deployed
Most WAFs run as a reverse proxy in front of the web servers: clients connect to the WAF, which forwards clean requests. Other options are a module on the web server itself, or a cloud WAF in front of the whole site. Because most traffic is HTTPS, the WAF terminates TLS with the site's certificate so it can read the requests.
Tuning without blocking real users
- Start in detection mode and watch the logs for a week.
- Add exceptions for legitimate patterns (for example rich-text fields) per URL, not globally.
- Switch to blocking for the clearest rules first, then the rest.
- Send WAF logs to your SIEM, and review blocked requests after every application release.
Navijin is developing NavWAF, a web application firewall for portals and APIs, as part of its security platform.
FAQ
Frequently asked questions
Do I need a WAF if I have a firewall?
If you publish websites, portals or APIs to the internet, yes. A network firewall allows the HTTPS connection; only a WAF looks inside the requests.
What is the OWASP Top 10?
A widely used list of the most critical web application risks. Most WAF rule sets are built to cover it.
Does a WAF slow my website down?
A well-sized WAF adds very little latency. It can even reduce load by blocking bots and caching.
Related
Keep reading
What is a firewall?
Read more →Firewall rules that actually protect you
Read more →SIEM vs SOAR vs XDR
Read more →Private 5G vs Wi-Fi for Enterprises: Which Wireless Technology Fits?
Compare private cellular networks and enterprise Wi-Fi for factories, ports, campuses and warehouses: coverage, mobility, device support, spectrum, cost and when to combine both.
Read more →What Is Port Security on a Switch? Stop Unknown Devices From Connecting
Switch port security explained: limiting MAC addresses per port, sticky learning, violation modes (protect, restrict, shutdown), when to use it and how it compares with 802.1X.
Read more →Warehouse and Logistics Network Design: Scanners, Cameras and Automation
How to design networks for warehouses and logistics centres: Wi-Fi for scanners and vehicles, outdoor yards and docks, CCTV, industrial switches for automation, and resilience.
Read more →Need help designing your network?
Navijin engineers provide free design consultations, bills of materials and quotations for business projects.