Skip to main content

Overview

A WAF is deployed to protect a specific web application or set of web applications, and it can be considered a reverse proxy. Proxies generally protect clients, while WAFs protect servers. A WAF can take the form of an appliance, a server plugin, or a filter.

WAFs are a class of firewall that has been in use since web applications were first accessed through web protocols such as HTTP. They can inspect traffic for SQL injection, operating system command injection, and cross-site scripting attacks and prevent inbound attacks. Some detect traffic from malicious URLs. WAFs are also used in content delivery networks and to prevent distributed denial-of-service (DDoS) attacks.

Web application and API protection (WAAP) builds on the WAF, and the WAF is an integral component of API security, bot defense, and DDoS protection. WAAP can be offered as a product suite or as a cloud-based service.

A WAF can be customized to the application it protects. That customization can take significant effort, and it needs to be maintained as the application changes.

Similar Terms

1 term

Frequently Asked Questions

What does WAF stand for?→

WAF stands for web application firewall.

What attacks does a WAF block?→

A WAF's rules generally cover common web attacks such as cross-site scripting (XSS) and SQL injection. WAFs can also inspect traffic for operating system command injection and are used to prevent distributed denial-of-service (DDoS) attacks.

What is the difference between a WAF and a secure web gateway?→

A secure web gateway filters outbound user traffic and protects users from web-based threats, such as links to malicious websites. It is not a replacement for a WAF, which protects websites hosted by the organization from inbound attacks.

Related

Sources

Definitions follow the government and standards body sources listed above. This site is not affiliated with the agencies or organizations cited.