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 firewallWeb application firewall
Looks atIP addresses, ports, protocols, sessionsHTTP requests: URLs, headers, parameters, bodies
StopsUnwanted connections, port scans, many intrusionsInjection, XSS, file inclusion, credential stuffing, bad bots
ProtectsWhole networks and serversSpecific websites, APIs and web portals
NeedsRules per network and serviceRules 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

  1. Start in detection mode and watch the logs for a week.
  2. Add exceptions for legitimate patterns (for example rich-text fields) per URL, not globally.
  3. Switch to blocking for the clearest rules first, then the rest.
  4. 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.

Need help designing your network?

Navijin engineers provide free design consultations, bills of materials and quotations for business projects.