How Do I Handle False Alarms as WAF Blocks Normal Requests to My Website?

Once an attack hits a WAF rule, WAF will respond to the attack immediately according to the protective action (Log only or Block) you configured for the rule and display an event on the Events page.

In the row containing the false alarm event, click Details in the Operation column and view the event details. If you are sure that the event is a false positive, handle it as a false alarm by referring to Table 1. After an event is handled as a false alarm, WAF stops blocking corresponding type of event. No such type of event will be displayed on the Events page and you will no longer receive alarm notifications accordingly.

**Table 1** Handling false alarms
Type of Hit Rule	Hit Rule	Handling Method
WAF built-in protection rules	Basic web protection rules Basic web protection defends against common web attacks, such as SQL injection, XSS attacks, remote buffer overflow attacks, file inclusion, Bash vulnerability exploits, remote command execution, directory traversal, sensitive file access, and command and code injections. Basic web protection also detects web shells and evasion attacks. Feature-based anti-crawler protection Feature-based anti-crawler identifies and blocks crawler behavior from search engines, scanners, script tools, and other crawlers.	In the row containing the attack event, click Handle as False Alarm in the Operation column. For details, see Handling False Alarms.
Custom protection rules	CC attack protection rules Precise protection rules Blacklist and whitelist rules Geolocation access control rules Web tamper protection rules JavaScript anti-crawler protection Information leakage prevention rules Data masking rules	Go to the page displaying the hit rule and delete it.
Other	Invalid access requests NOTE: If either of the following cases, WAF blocks the access request as an invalid request: When form-data is used for POST or PUT requests, the number of parameters in a form exceeds 8,192. The URI contains more than 2,048 parameters. The number of headers exceeds 512.	Allow the blocked requests by referring to Configuring Custom Precise Protection Rules. The Handle as False Alarm button is grayed out for events that are generated against a precise protection rule.