Testing WAF

This section describes how to connect your domain to WAF on a local PC and then access the site to verify whether WAF works properly.

Before testing WAF, ensure that the protocol, address, and port number used by the origin server of the domain name (for example, www.test.com), and uploaded certificate content and private key if Client Protocol is HTTPS are correct.

Prerequisites

  • Login credentials have been obtained.

  • A domain name without using any other proxy has been created.

Connecting Your Domain to WAF Locally

  1. Obtain the CNAME value.

    1. Log in to the management console.

    2. Click image1 in the upper left corner of the management console and select a region or project.

    3. Choose Security > Web Application Firewall.

    4. In the navigation pane, choose Domains. Figure 1 shows an example.

      **Figure 1** Domains page

      Figure 1 Domains page

      Note

      In the upper part of the domain name list, click Quota details to view the domain name quota.

    5. In the row of the desired domain name, under the Name column, click the domain name you want to test. Figure 2 shows an example.

      **Figure 2** Copying the CNAME value

      Figure 2 Copying the CNAME value

    6. In the CNAME row, click image2 to copy the CNAME value.

  2. Ping the CNAME value and record the corresponding IP address (for example, 192.168.0.1).

  3. Add the domain name and WAF IP address to the hosts file.

    1. Use a text editor, such as Notepad or Notepad++, to open the hosts file. Generally, the hosts file is stored in the C:\Windows\System32\drivers\etc\ directory.

    2. Add the back-to-source IP address of WAF obtained in Step 2 and protected domain name to the hosts file. Figure 3 shows an example.

      **Figure 3** Adding a record

      Figure 3 Adding a record

    3. Save the hosts file and ping the protected domain name on the local PC.

      It is expected that the resolved IP address is the back-to-source IP address of WAF obtained in Step 2. If the resolved IP address is the origin server address, run the ipconfig/flushdns command in the Windows operating system to refresh the DNS cache.

Verifying Whether WAF Forwarding Is Normal

  1. Clear the browser cache and enter the domain name in the address box of a browser to check whether the website can be accessed.

    If the domain name resolves to the back-to-source IP address of WAF and WAF configurations are correct, the website can be accessed.

    **Figure 4** Normal access

    Figure 4 Normal access

  2. Simulate simple web attack commands.

    1. Set the mode of Basic Web Protection to Block. For details, see Enabling Basic Web Protection.

    2. Clear the browser cache, enter http://www.test.com?id=1%20or%201%20=1 in the address box of the browser to simulate an SQL injection attack, and check whether WAF blocks the attack. See Figure 5.

      **Figure 5** Request blocked

      Figure 5 Request blocked

    3. Choose Security > Web Application Firewall. On the displayed page, click Events and view test data on the displayed page. Figure 6 shows an example.

      **Figure 6** Viewing test data

      Figure 6 Viewing test data

last updated: 2024-11-14 08:39 UTC - commit: 6926fd6d97bbd187a6e871c49328e623154a3969