Configuring Information Leakage Prevention Rules to Protect Sensitive Information from Leakage

Prerequisites

You have added your website to a policy.

Constraints

• This function is not supported by the professional edition.
• It takes several minutes for a new rule to take effect. After the rule takes effect, protection events triggered by the rule will be displayed on the Events page.

Configuring an Information Leakage Prevention Rule

1. Log in to the management console.
2. Click in the upper left corner of the management console and select a region or project.
3. Click in the upper left corner of the page and choose Security > Web Application Firewall.
4. In the navigation pane on the left, choose Policies.
5. Click the name of the target policy to go to the protection configuration page.
6. Click the Information Leakage Prevention configuration area and toggle it on or off if needed.
   • : enabled.
   • : disabled.

7. In the upper left corner above the Information Leakage Prevention rule list, click Add Rule.
8. In the dialog box displayed, add an information leakage prevention rule by referring to Table 1.

   Information leakage prevention rules prevent sensitive information (such as ID numbers, phone numbers, and email addresses) from being disclosed. This type of rule can also block specified HTTP status codes.

   Sensitive information filtering: Configure rules to mask sensitive information, such as phone numbers and ID numbers, from web pages. For example, you can set the following protection rules to mask sensitive information, such as ID numbers, phone numbers, and email addresses:

   Figure 1 Sensitive information leakage
   
   Response code interception: An error page of a specific HTTP response code may contain sensitive information. You can configure rules to block such error pages to prevent such information from being leaked out. For example, you can set the following rule to block error pages of specified HTTP response codes 404, 502, and 503.

   Figure 2 Blocking response codes
   

   Table 1 Rule parameters

   Parameter	Description	Example Value
   Path	A part of the URL that does not include the domain name. The URL can contain sensitive information (such as ID numbers, phone numbers, and email addresses) or a blocked error code. Prefix match: Only the prefix of the path to be entered must match that of the path to be protected. If the path to be protected is /admin, 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. NOTE: The path supports prefix and exact matches only. Regular expressions are not supported. The path cannot contain two or more consecutive slashes. For example, ///admin. If you enter ///admin, the WAF engine converts /// to /.	/admin*
   Type	Sensitive information filtering Response code interception: Enable WAF to block the specified HTTP response code page.	Sensitive information filtering
   Content	Information to be protected. Options are Identification card, Phone number, and Email.	Identification card
   Rule Description	A brief description of the rule. This parameter is optional.	None

9. Click Confirm. The added information leakage prevention rule is displayed in the list of information leakage prevention rules.

Related Operations

• To disable a rule, click Disable in the Operation column of the rule. The default Rule Status is Enabled.
• To modify a rule, click Modify in the row containing the rule.
• To delete a rule, click Delete in the row containing the rule.

Configuration Example — Masking Sensitive Information

To verify that WAF is protecting your domain name www.example.com against an information leakage prevention rule:

1. Add an information leakage prevention rule.
   Figure 3 Sensitive information leakage
   

2. Enable information leakage prevention.
   Figure 4 Information Leakage Prevention configuration area
   

3. Clear the browser cache and access http://www.example.com/admin/.

   The email address, phone number, and identity number on the returned page are masked.

   Figure 5 Sensitive information masked