• Web Application Firewall

  1. Help Center
  2. Web Application Firewall
  3. User Guide
  4. Rule Configurations
  5. Configuring Data Masking Rules

Configuring Data Masking Rules

This section describes how to configure data masking rules. Data Masking prevents such data as usernames and passwords from being displayed in event logs.


  • Login credentials have been obtained.
  • The domain name to be protected has been created.


  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. Choose Security > Web Application Firewall. In the navigation pane, choose Domains. The Domains page is displayed (see Figure 1).

    Figure 1 Domains page

  4. 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

  5. In the Data 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 Data Masking configuration area

  6. Click Customize Rule. On the displayed page, click Add Rule in the upper left corner to add a data 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

  7. In the displayed dialog box shown in Figure 5, specify the parameters by referring to Table 1.

    Figure 5 Adding a data masking rule
    Table 1 Rule parameters



    Example Value


    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/login.php, set Path to /admin/login.php.

    Masked Field

    A field set to be masked
    • Params: A request parameter
    • Header: A user-defined HTTP header
    • If Masked Field is Params, set Subfield according to your actual needs. If it is set to id, content that matches id is masked.
    • If Masked Field is Header, set Subfield according to your actual needs. If it is set to Accept, content that matches Accept is masked.


    Set the parameter based on Masked Field. The masked field will not be displayed in the log.


    The length of a subfield cannot exceed 2048 bytes. Only digits, letters, underscores (_), and hyphens (-) are allowed.

  8. Click OK.

    • To modify the added rule, click Modify in the row containing the target rule.
    • To delete the added rule, click Delete in the row containing the target rule.