How to turn on the web application firewall (WAF)

For server administrators · Updated 2026-10-29

On this page
  1. Before you start
  2. Steps
  3. What protect mode does
  4. Good to know
  5. Common questions

The web application firewall recognises attacks on websites: SQL injection, reading server files, command and code injection, script injection, attack tools, and searches for secret files and backdoors. In monitor mode (the default) it only records them. In protect mode it refuses them and blocks addresses that keep attacking.

Before you start

Leave it in monitor mode for a few days first and look at Recent events on the Protection Shield page. If you see events for normal visitors of a site, turn the firewall off for that site before switching to protect.

Steps

  1. In the administrator panel (https://<server>:2087), open Protection Shield (section Security).
  2. Under Web application firewall, set Mode to Protect — refuse attacks and block attackers.
  3. Choose the Sensitivity:
    • Low — block only heavy attacks
    • Normal (the default)
    • High — block after a few attacks
  4. Click Save.

Switching to or from protect mode updates every website's configuration in the background; it takes effect within a minute or two.

What protect mode does

  • Clear attacks are refused before they reach the website, with the error 403. This covers requests for .env, .git/, .htpasswd, wp-config.php copies and vendor/phpunit/, and query strings with SQL UNION SELECT, ../ path tricks, /etc/passwd, php:// wrappers, ${jndi: and <script.
  • Attackers are blocked in the firewall. Every attack adds to the address's score per minute, across all sites: 5 points for SQL injection, command injection, reading server files and attack tools, 3 for script injection and 2 for looking for secrets or backdoors. At 40 (Low), 20 (Normal) or 10 (High) points the address is blocked for Block for (minutes), and for 24 hours when it comes back within a day.
  • Never blocked: this server, addresses on the Firewall allow list and anyone who signed in to the panel in the last day.

Good to know

  • Monitor mode records but never refuses or blocks. The Attacks on websites (24 h) box then says "recorded (monitor mode)".
  • Off stops recording attacks too.
  • Customers can turn the firewall off for one website in their control panel, for an application that sends requests that look like attacks. See turn website protection on or off.

Common questions

A form on a website stopped working after I switched to protect. What now?

Look in Recent events for that domain. If normal requests are refused, ask the customer (or do it yourself in their control panel) to turn the firewall off for that site, or go back to Normal or Low sensitivity.

Someone was blocked by mistake. How do I unblock them?

Click Unblock next to the address under Blocked now on the same page.

Which sensitivity should I choose?

Start with Normal. Choose High if attacks get through in the events list, Low if normal visitors are blocked.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.