WAF

About 6 min

The WAF inspects request content and blocks attacks such as SQL injection and cross-site scripting. The basic WAF is included in every plan and is on by default.

RequestWAF exceptionPath prefix · Parameter nameWAFSQL injection · XSSOrigin
GET /?id=x' OR 'a'='aSQL injection · log only
Logged
GET /index
Allowed
GET /s?q=<script>XSS · log only
Logged
POST /editor/saveException: this path is not inspected
Allowed
Basic WAFIn every plan, on by default
New sitesObserve for a few days first, then switch to Block
False positivesUse an exception, don't turn the WAF off
Observe only records and fetches from the origin as usual; Block stops requests directly; false positives get an exception

Switch and modes

Go to Security Center › Protection settings › WAF:

  • WAF main switch: when off, the whole site is no longer inspected; not recommended for long.
  • Observe: only records hits and fetches from the origin as usual; good for the first few days to see whether there are false positives.
  • Block: blocks suspicious requests directly.
Console · WAF Settings
WAF settings
Tip Run a new site in "Observe" for a few days, confirm in the attack log that normal business isn't blocked, then switch to "Block".

When a request can't be fully inspected

When the request body is too large or has too many parameters or headers, the WAF tries to inspect the rest later; anything still left uninspected is handled as configured (allow or block). Sites that accept large uploads should watch this setting.

Handle false positives with exceptions

For a false positive, use a "WAF exception" instead of turning the WAF off.

  • Path prefix only: nothing under that path is inspected.
  • Path prefix plus parameter name: only those parameters are skipped; the rest under the path is still inspected.

Basic and Plus

The basic WAF uses built-in rules that are updated with each release. With WAF Plus and WAF Rules Update you get deeper inspection, hourly rule updates and a high-risk IP database; see Paid features.

Replay-guard paths and custom leak-detection regexes in WAF Plus are checked on save the same way as CC custom rules: a regex that matches anything (including empty content) or may backtrack out of control is rejected with the reason shown.

Get started

Try the live demo

Open the live demo, or contact us for a quote and the install command