Web Application Firewall meaning, in plain words

A WAF is a wall that stops malicious traffic at a site's entrance. How it inspects traffic, why it leaves holes open, and how to avoid blocking real visitors.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

A WAF is a wall that stops malicious traffic at the entrance. The name is short for Web Application Firewall. It inspects the traffic between a website and its users, finds what is malicious, and blocks it. IPA's guide to safe website operation lists a WAF among the mechanisms that inspect traffic to detect or block malicious requests.

How does a WAF work?

Picture a guard at a building's reception desk. The guard checks a visitor's bag, and if something dangerous is inside, does not let the visitor through. A WAF checks the traffic that reaches your site in the same way.

The yardstick is a set of rules prepared beforehand. Traffic whose contents match a rule is blocked, and traffic that does not is passed to the site. The rules describe features seen in known attacks, so when a new attack appears the rules need updating. Because the rules are written from what is already known, a WAF is strongest against familiar patterns and weaker against something new. That is why the rules need regular updates, and why the record of blocked traffic is worth reading.

There are several kinds of WAF: a cloud type placed in front of the site, a plugin type that runs inside the site, and a type that is a physical device. IPA's Web Application Firewall Reader sets out the kinds and features of products and services, the criteria for choosing, and the operating structure needed. The overall picture of entrance defenses, including WAFs, can be found in hacking countermeasures.

Why does a WAF matter?

Because a hole is sometimes found that cannot be fixed at once. Updating an old plugin may break the page, the agency may be out of reach, or the maker may not have released a fixed version yet. IPA's 20 items treat protecting the application with a WAF or similar as one effective measure when a vulnerability cannot be fixed immediately.

A WAF is not all-powerful, though. It does not close the hole. It blocks traffic heading for the hole, so it is no reason to put off updating to the fixed version. Think of it as a way to buy time, not as a repair. OWASP's material also warns that you should test whether attacks get past the rules, and that overly broad rules block legitimate traffic.

Operation after introduction matters too. Look at the record of blocked traffic, check whether anything was blocked by mistake, and correct the rules as needed. IPA's reader also explains the operation needed to detect attacks properly.

What should you check about a WAF?

  1. Whether your site has one, and which kind it is.
  2. Whether it is actually running and its rules are kept current.
  3. Who reads the record of blocked traffic, and how often.
  4. Whether updates are still scheduled, since a WAF does not replace them.

To work out which kind suits your site, contact us.

Related terms

  • Virtual patching: a stopgap that blocks only the traffic aimed at a known hole until the fixed version is out
  • Rate limiting: a limit on how often something can be accessed in a short time

Frequently asked questions

If I add a WAF, is my site safe?

Not necessarily. A WAF inspects traffic and blocks it, and it does not close the holes inside the site. Some attacks get past its rules, so use it together with software updates and a review of settings.

Can a WAF block real customers by mistake?

Yes. When rules are too broad, a false positive occurs and legitimate traffic is judged to be malicious. OWASP also says overly broad rules can block legitimate traffic. After introducing one, adjust the rules while looking at the record of what was blocked.

Can I use a WAF on a WordPress site?

Yes. There are several kinds: a cloud WAF placed in front of the site, and a mechanism that runs at the site's entrance. Our Cyber Shield Guard Pro includes a WAF that runs inside the plugin.

Next step

Whether a WAF is in place on your site is a question we can answer in a consultation: contact us. The free URL check shows only what is visible from outside. Defenses against attacks in general are gathered in hacking countermeasures.

Frequently asked questions

If I add a WAF, is my site safe?

Not necessarily. A WAF inspects traffic and blocks it, and it does not close the holes inside the site. Some attacks get past its rules, so use it together with software updates and a review of settings.

Can a WAF block real customers by mistake?

Yes. When rules are too broad, a false positive occurs and legitimate traffic is judged to be malicious. OWASP also says overly broad rules can block legitimate traffic. After introducing one, adjust the rules while looking at the record of what was blocked.

Can I use a WAF on a WordPress site?

Yes. There are several kinds: a cloud WAF placed in front of the site, and a mechanism that runs at the site's entrance. Our Cyber Shield Guard Pro includes a WAF that runs inside the plugin.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.