Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Web Application Firewall (WAF)?

A web application firewall (WAF) inspects and filters HTTP and HTTPS traffic between users and a web application, blocking common attacks such as SQL injection and cross-site scripting.

Illustration for the cybersecurity term Web Application Firewall (WAF)
Home / Blog / Cybersecurity Terms / What Is a Web Application Firewall (WAF)?
17 November 2026

What Is a Web Application Firewall (WAF)?

What Is a Web Application Firewall (WAF)?

A web application firewall (WAF) is a security control that sits in front of a web application and inspects the HTTP and HTTPS requests sent to it. It looks for patterns associated with attacks, such as SQL injection, cross-site scripting, and path traversal, and blocks or flags malicious requests before they reach the application.

A traditional network firewall decides whether traffic may pass based on IP addresses, ports, and protocols. It would happily allow a request to port 443 that contains a SQL injection payload. A WAF works at the application layer (layer 7) and understands the content of web requests, which is why it can catch what network firewalls miss.

How a WAF Works

A WAF acts as a reverse proxy or filter. Each request is decrypted where necessary, parsed, and evaluated against a set of rules. Depending on the result, the WAF allows the request, blocks it, challenges the client (for example with a CAPTCHA or JavaScript check), or simply logs it for review.

Two security models are used, often together:

Modern WAFs add behavioural analysis, bot detection, rate limiting, API schema validation, and threat intelligence feeds. The open-source OWASP Core Rule Set, used with engines such as ModSecurity and Coraza, is widely deployed and also underpins many commercial products.

Deployment Options

DeploymentDescriptionTypical use
Cloud or CDN-basedTraffic is routed through a provider’s networkPublic websites, DDoS protection, quick deployment
Network applianceHardware or virtual appliance in your data centreHigh-performance, on-premises applications
Host-based or embeddedModule running on the web server or within the applicationFine-grained control, microservices
Cloud platform nativeWAF offered by AWS, Azure, or Google CloudApplications hosted on those platforms

What a WAF Is Good For

Limitations

A WAF is a valuable layer, but it is not a fix for insecure code:

Getting the Most From a WAF

Start in monitoring mode to understand normal traffic, then move to blocking once false positives are under control. Ensure the origin server only accepts traffic from the WAF. Keep rule sets updated, review logs regularly, and integrate alerts with your SIEM. Above all, use the WAF alongside secure development and regular application testing, not instead of them.

At Privia Security, our Web Application Security Services test whether your applications and WAF configurations stand up to real attacks, including common WAF bypass techniques.

FAQ – Frequently Asked Questions

What Is the Difference Between a WAF and a Network Firewall?

A network firewall controls traffic based on IP addresses, ports, and protocols, deciding which connections are allowed. A WAF inspects the content of web requests at the application layer and blocks attacks such as SQL injection and cross-site scripting. Most organisations need both, as they protect against different types of threats.

Does a WAF Replace Secure Coding?

No. A WAF can block many common attacks and provide temporary virtual patches, but it cannot fix business logic flaws, broken access control, or insecure design, and skilled attackers can sometimes bypass its rules. Secure development and regular application testing remain essential, with the WAF serving as an additional layer of protection.

Is a WAF Required for PCI DSS?

PCI DSS version 4.0 requires public-facing web applications to be protected by an automated technical solution that continually detects and prevents web-based attacks, and a WAF is the most common way to meet it. This requirement became mandatory on 31 March 2025. Alternatives exist, but they must provide equivalent protection.

Related Terms

You May Be Interested In These

What Is PrintNightmare?

Cybersecurity Terms

17 November 2026

What Is PrintNightmare?

Read More
What Is MITRE D3FEND?

Cybersecurity Terms

17 November 2026

What Is MITRE D3FEND?

Read More
What Is SharpHound?

Cybersecurity Terms

17 November 2026

What Is SharpHound?

Read More