doc-exports/docs/wafd/umn/waf_01_0008.html

Configuring Basic Web Protection Rules

After this function is enabled, WAF can defend against common web attacks, such as SQL injections, XSS, remote overflow vulnerabilities, file inclusions, Bash vulnerabilities, remote command execution, directory traversal, sensitive file access, and command/code injections. You can also enable other checks in basic web protection, such as web shell detection, deep inspection against evasion attacks, and header inspection.

Basic web protection has two modes: Block and Log only.

Prerequisites

A website has been added to WAF.

Procedure

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 (Dedicated) under Security.
4. In the navigation pane, choose Website Settings.
5. In the Policy column of the row containing the target website, click the number to go to the policy configuration page.
6. In the Basic Web Protection configuration area, change Status and Mode as needed by referring to Table 1.
   Figure 1 Basic Web Protection configuration area
   

   Table 1 Parameter description

   Parameter	Description
   Status	Status of Basic Web Protection : enabled. : disabled
   Mode	Block: WAF blocks and logs detected attacks. Log only: WAF only logs detected attacks.

7. In the Basic Web Protection configuration area, click Advanced Settings.
8. Click the Protection Status tab, and enable protection types one by one by referring to Table 3. Figure 2 shows an example.
   Figure 2 Basic web protection
   
   1. Set the protection level.

      In the upper part of the page, set Protection Level to Low, Medium, or High. The default value is Medium.

      Table 2 Protection levels

      Protection Level	Description
      Low	WAF only blocks the requests with obvious attack signatures. If a large number of false alarms are reported, Low is recommended.
      Medium	The default level is Medium, which meets a majority of web protection requirements.
      High	At this level, WAF provides the finest granular protection and can intercept attacks with complex bypass features, such as Jolokia cyber attacks, common gateway interface (CGI) vulnerability detection, and Druid SQL injection attacks. To let WAF defend against more attacks but make minimum effect on normal requests, observe your workloads for a period of time first. Then, configure a global protection whitelist rule and select High.

   2. Set the protection type.
      

      By default, General Check is enabled. You can enable other protection types by referring to Table 3.

   Table 3 Protection types

   Type	Description
   General Check	Defends against attacks such as SQL injections, XSS, remote overflow vulnerabilities, file inclusions, Bash vulnerabilities, remote command execution, directory traversal, sensitive file access, and command/code injections. SQL injection attacks are mainly detected based on semantics. NOTE: If you enable General Check, WAF checks your websites based on the built-in rules.
   Webshell Detection	Protects against web shells from upload interface. NOTE: If you enable Webshell Detection, WAF detects web page Trojan horses inserted through the upload interface.
   Deep Inspection	Identifies and blocks evasion attacks, such as the ones that use homomorphic character obfuscation, command injection with deformed wildcard characters, UTF7, data URI scheme, and other techniques. NOTE: If you enable Deep Inspection, WAF detects and defends against evasion attacks in depth.
   Header Inspection	This function is disabled by default. When it is disabled, General Check will check some of the header fields, such as User-Agent, Content-type, Accept-Language, and Cookie. NOTE: If you enable this function, WAF checks all header fields in the requests.

9. Click the Protection Rules tab to view details. For more details about the parameters, see Table 4.
   

   Click to search for a rule by CVE ID, Risk Severity, Application Type, or Protection Type.

   Table 4 Protection rules

   Parameter	Description
   Rule ID	The protection rule ID, which is generated automatically.
   Rule Description	Details of attacks the protection rule is configured for.
   CVE ID	Common Vulnerabilities & Exposures (CVE) ID, which corresponds to the protection rule. For non-CVE vulnerabilities, a double dash (--) is displayed.
   Risk Severity	The severity of the vulnerability, including: High Medium Low
   Application Type	The application type the protection rule is used for.
   Protection Type	The type of the protection rule. WAF can discover SQL injection, command injection, XSS attacks, XML external entity (XXE) injection, Expression Language (EL) Injection, CSRF, SSRF, local file inclusion, remote file inclusion, website Trojans, malicious crawlers, session fixation attacks, deserialization vulnerabilities, remote command execution, information leakage, DoS attacks, source code/data leakage.

Protection Effect

If General Check is enabled and Mode is set to Block for your domain name, to verify WAF is protecting your website (www.example.com) against general check items:

1. Clear the browser cache and enter the domain name in the address box of a browser to check whether the website is accessible.
   • If the website is inaccessible, connect the website domain name to WAF by following the instructions in Step 1: Add a Website to WAF.
   • If the website is accessible, go to Step 2.

2. Clear the browser cache and enter http://www.example.com?id=1%27%20or%201=1 in the address box of the browser to simulate an SQL injection attack.
3. Return to the WAF console. In the navigation pane, choose Events. On the displayed page, view or download events data.

Parent topic: Rule Configuration