This section describes how to configure false alarm masking rules.
You can add false alarms to the whitelist and ignore certain rule IDs (for example, skip XSS check for a specified URL).
- Login credentials have been obtained.
- The domain name to be protected has been created.
- Log in to the management console.
- Click in the upper left corner of the management console and select a region or project.
- Choose Domains. The Domains page is displayed (see Figure 1).. In the navigation pane, choose
Figure 1 Domains page
- In the Operation column of the row containing the target domain name, click Configure Policy. The protection configuration page is displayed, as shown in Figure 2.
Figure 2 Protection configuration page
- In the False Alarm Masking configuration area, change Status as needed and then click Save in the upper right corner of the Protection Status list. In the dialog box displayed, click Yes to save the settings. Otherwise, click Cancel. See Figure 3.
Figure 3 False Alarm Masking configuration area
- Click Customize Rule. On the displayed page, click Add Rule in the upper left corner to add a false alarm masking rule. See Figure 4.
If you do not click Save after changing Status in step 5, the Warning dialog box is displayed when you click Customize Rule.
- Click Yes to cancel the previous settings.
- Click No and then Save to save the settings.
Figure 4 Clicking Add Rule
- In the displayed dialog box shown in Figure 5, specify the parameters by referring to Table 1.
Figure 5 Adding a false alarm masking rule
Table 1 Rule parameters
Misreported URL excluding a domain name
- Prefix match: The path ending with * indicates that the path is used as a prefix. For example, if the path to be protected is /admin/test.php or /adminabc, set Path to /admin*.
- Exact match: The path to be entered must match the path to be protected. If the path to be protected is /admin, set Path to /admin.
- The path supports prefix and exact matches only and does not support regular expressions.
- The path cannot contain two or more consecutive slashes. For example, ///admin. If you enter ///admin, the WAF engine converts /// to /.
For example, if the URL to be protected is http://www.example.com/admin, set Path to /admin.
Rule ID of a misreported event in Events whose type is not Custom.
Click Handle False Alarm in the row containing the attack event to obtain the rule ID.
This value consists of six digits and cannot be empty.
- Click OK. If Rule added successfully is displayed in the upper right corner, the rule is added.
To delete the added rule, click Delete in the row containing the target rule.