Configuring a Known Attack Source Rule to Block Specific Visitors for a Specified Duration

Prerequisites

• You have added the website you want to protect to WAF or added a protection policy.
  • For cloud CNAME access mode, see Connecting a Website to WAF (Cloud Mode - CNAME Access).
  • For cloud load balancer access mode, see Connecting Your Website to WAF (Cloud Mode - Load Balancer Access).
  • For dedicated mode, see Connecting Your Website to WAF (Dedicated Mode).
• If you use a dedicated WAF instance, ensure that it has been upgraded to the latest version. For details, see Managing Dedicated WAF Engines.

Constraints

• For a known attack source rule to take effect, it must be enabled when you configure basic web protection, precise protection, blacklist, or whitelist protection rules.
  

  For blacklist and whitelist rules, a known attack source with Long-term IP address blocking or Short-term IP address blocking configured cannot be selected.

• Before adding a known attack source rule for malicious requests blocked by Cookie or Params, a traffic identifier must be configured for the corresponding domain name. For more details, see Configuring a Traffic Identifier for a Known Attack Source.
• 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.

Specification Limitations

• You can configure up to six blocking types. Each type can have one known attack source rule configured.
• The maximum time an IP address can be blocked for is 30 minutes.

Configuring a Known Attack Source 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 and choose Web Application Firewall under Security & Compliance.
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. Enable Known Attack Source if needed.
   • : enabled.
   • : disabled.

7. If you add a known attack source for the first time, click Add Known Attack Source Rule. Configure the parameters by referring to Table 1.
   

   You can click Add Rule and add more known attack source rules.

   Figure 1 Configure Known Attack Source Rule
   

   Table 1 Known attack source parameters

   Parameter	Description	Example Value
   Blocking Type	Specifies the blocking type. The options are: Long-term IP address blocking Short-term IP address blocking Long-term Cookie blocking Short-term Cookie blocking Long-term Params blocking Short-term Params blocking NOTICE: For blacklist and whitelist rules, a known attack source with Long-term IP address blocking or Short-term IP address blocking configured cannot be selected.	Long-term IP address blocking
   Blocking Duration (s)	The blocking duration must be an integer and range from: (300, 1800] for long-term blocking (0, 300] for short-term blocking	500
   Rule Description	A brief description of the rule. This parameter is optional.	-

8. Click Save. You can then view the added known attack source rule in the list.

Related Operations

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

Configuration Example - Blocking Known Attack Source Identified by Cookie

Assume that domain name www.example.com has been connected to WAF and a visitor has sent one or more malicious requests through IP address XXX.XXX.248.195. You want to block access requests from this IP address and whose cookie is jsessionid for 10 minutes. Refer to the following steps to configure a rule and verify its effect.

1. On the Website Settings page, click www.example.com to go to its basic information page.
2. In the Traffic Identifier area, configure the cookie in the Session Tag field.
   Figure 2 Traffic Identifier
   

3. Add a known attack source, select Long-term Cookie blocking for Blocking Type, and set block duration to 600 seconds.
   Figure 3 Adding a Cookie-based known attack source rule
   

4. Enable the known attack source protection.
   Figure 4 Known Attack Source configuration area
   

5. Add a blacklist and whitelist rule to block XXX.XXX.248.195. Select Long-term Cookie blocking for Known Attack Source.
   Figure 5 Specifying a known attack source rule
   

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

   When a request from IP address XXX.XXX.248.195, WAF blocks the access. When WAF detects that the cookie of the access request from the IP address is jsessionid, WAF blocks the access request for 10 minutes.

   Figure 6 Block page
   

7. Go to the WAF console. In the navigation pane on the left, choose Events. View the event on the Events page.