Skip to content

WAF

QuantCDN WAF is an optional extra that needs to be enabled for your account. To begin you will need to contact support and request WAF enablement for your organisation.

The WAF inspects requests on proxy rules only, which are the requests that reach an application. Static content is not inspected, because no application handles it.

Once your account has WAF enabled, turn it on in the editor of each proxy rule that reaches an application.

  1. In the project, go to Traffic > Rules.
  2. Open the actions menu of the proxy rule and choose Edit, or select New rule and choose the Proxy action.
  3. Scroll to Web Application Firewall and turn on Web Application Firewall (WAF).
  4. Set WAF mode and Paranoia level, then select Update rule (or Create rule).

For the full rollout, see Configure WAF.

General settings for the WAF.

Setting Default Description
WAF mode Report only Report only logs hits and blocks nothing. Block blocks requests with a 403
Paranoia level 1 - Low (recommended) How strict the WAF will be when analysing traffic: 1 - Low, 2 - Medium, 3 - High or 4 - Extreme
Setting Default Description
Allow rule IDs WAF rule IDs that are excluded. Use it to tune the WAF for your application
Allow IPs IP addresses that bypass the WAF checks
Block IPs An IP blocklist that will always be rejected by the WAF
Block User-Agents User agent blocklist
Block referers HTTP referer blocklist
Block ASNs AS number blocklist

Lists of well-known bad actors that can be optionally turned on.

Setting Default Description
Known bad bots Off Turn on the bot blocklist
Known bad referers Off Turn on the referer blocklist
Known bad IPs Off Turn on the IP blocklist
AI crawlers Off Block AI crawlers

Enable Project Honeypot integration for the WAF

Setting Default Description
HTTP:BL (Project Honey Pot) Off Turn on Project Honey Pot. Then enter your HTTP:BL API key
Block suspicious Block IPs that project honeypot determines as suspicious
Block harvesters Block any request that is determined to come from a data harvester
Block spammers Block spam IPs
Block search engines Block requests that are marked as coming from search engines

To better protect your application, the WAF can be configured to provide rate limits to request IPs. The rate limiting protects against burst IP traffic, the request rate needs to be sustained over a short period to trigger.

Setting Default Description
Mode Disabled Disabled, Report, Block or Bot Challenge
Requests/second 10 The number of requests that are required to trigger the rate limit
Cooldown (seconds) 30 Number of seconds a client’s IP address will be restricted

When the rate limit is reached the WAF will respond with a 429 status code.

Setting Default Description
Mode Disabled Disabled, Report, Block or Bot Challenge
Header name The name of the header used to group requests
Requests/second 5 The number of requests per second a client needs to make in the window
Cooldown (seconds) 30 Number of seconds a blocked client will be restricted for

WAF hit rate limiting (auto-ban on repeated violations) restricts an IP address that triggers WAF rules again and again.

Setting Default Description
Mode Disabled Disabled, Report, Block or Bot Challenge
Hits threshold 10 The number of WAF hits that trigger the limit
Within minutes 5 The window in which the hits are counted
Cooldown (seconds) 300 Number of seconds the IP address will be restricted for

QuantWAF can trigger notifications to a nominated Slack channel when a block or rate limit rule is triggered.

Setting Default Description
WAF Slack webhook Your application’s incoming webhook from Slack
Min RPM to notify Only notify when hits exceed this rate per minute

Please see the Slack documentation for creating a webhook.