Configuration Guidance

How EdgeSec Engine Works

The built-in protection rules of EdgeSec help you defend against common web application attacks, including XSS attacks, SQL injection, crawlers, and web shells. You can customize protection rules to let EdgeSec better protect your website services using these custom rules. Figure 1 shows how EdgeSec engine built-in protection rules work. Figure 2 shows the detection sequence of user-defined rules.

Figure 1 EdgeSec engine detection process

Figure 2 Priorities of custom protection rules

Response actions

Pass: The current request is unconditionally permitted after a protection rule is matched.
Block: The current request is blocked after a rule is matched.
CAPTCHA: The system will perform human-machine verification after a rule is matched.
Redirect: The system will notify you to redirect the request after a rule is matched.
Log: Only attack information is recorded after a rule is matched.
Mask: The system will anonymize sensitive information after a rule is matched.

Protection Rule Configuration Methods

EdgeSec provides the following customized configuration methods to simplify the configuration process. Select a proper configuration method to meet your service requirements.

This method is recommended when you have few domain name services or have different configuration rules for domain name services.

After a domain name is added, EdgeSec automatically associates a protection policy with the domain name, and protection rules configured for the domain name are also added to the protection policy by default. If there are domain names applicable to the protection policy, you can directly add them to the policy. For details, see Applying a Policy to Your Website.

Where to configure
1. In the navigation pane on the left, choose Website Settings.
2. In the Policy column of the row containing the target domain name, click the number to go to the Policies page.
  Figure 3 Website list

Protection rules you can configure on the rule configuration page

**Table 1** Configurable protection rules
Protection Rule	Description	Reference
Basic Web Protection	With an extensive reputation database, EdgeSec defends against Open Web Application Security Project (OWASP) top 10 threats, and detects and blocks threats, such as malicious scanners, IP addresses, and web shells.	Configuring Basic Protection Rules to Defend Against Common Web Attacks
CC Attack Protection	CC attack protection rules can be customized to restrict access to a specific URL on your website based on a unique IP address, mitigating CC attacks.	Configuring CC Attack Protection Rules to Defend Against CC Attacks
Precise Protection	You can customize protection rules by combining HTTP headers, cookies, URLs, request parameters, and client IP addresses.	Configuring a Precise Protection Rule
Blacklist and Whitelist	You can configure blacklist and whitelist rules to block, log only, or allow access requests from specified IP addresses.	Configuring IP Address Blacklist and Whitelist Rules to Block Specified IP Addresses
Known Attack Source	If EdgeSec blocks a malicious request by IP address, Cookie, or Params, you can configure a known attack source rule to let EdgeSec automatically block all requests from the attack source for a blocking duration set in the known attack source rule.	Configuring a Known Attack Source Rule
Geolocation Access Control	You can customize these rules to allow or block requests from a specific country or region.	Configuring Geolocation Access Control Rules to Block Requests from Specific Locations
Anti-Crawler	This function dynamically analyzes website service models and accurately identifies crawler behavior based on data risk control and bot identification systems, such as JS Challenge.	Configuring Anti-Crawler Rules
Global protection whitelist rules	You can configure these rules to let EdgeSec ignore certain rules for specific requests.	Configuring a Global Whitelist Rule to Ignore False Positives
Data Masking	You can configure data masking rules to prevent sensitive data such as passwords from being displayed in event logs.	Configuring a Data Masking Rule