هذه الصفحة غير متوفرة حاليًا بلغتك المحلية. نحن نعمل جاهدين على إضافة المزيد من اللغات. شاكرين تفهمك ودعمك المستمر لنا.
- What's New
- Function Overview
- Service Overview
- Billing
-
User Guide
- Enabling EdgeSec
- Site Acceleration
-
Security Protection
- Connecting a Domain Name to EdgeSec
- Dashboard
- Protection Statistics
-
Protection Policy
- Creating a Protection Policy
- Applying a Policy to Your Website
-
Configuring Protection Policies
- Configuration Guidance
- Configuring Basic Protection Rules to Defend Against Common Web Attacks
- Configuring CC Attack Protection Rules to Defend Against CC Attacks
- Configuring a Precise Protection Rule
- Creating a Reference Table to Configure Protection Metrics In Batches
- Configuring IP Address Blacklist and Whitelist Rules to Block Specified IP Addresses
- Configuring a Known Attack Source Rule
- Configuring Geolocation Access Control Rules to Block Requests from Specific Locations
- Configuring Anti-Crawler Rules
- Configuring a Global Whitelist Rule to Ignore False Positives
- Configuring a Data Masking Rule
- Address Group Management
- System Management
- Permissions Management
- Key Operations Recorded by CTS
- Monitoring
- Best Practices
-
API Reference
- Before You Start
- API Overview
- API Calling
-
API
- Protected Domain Name Management
-
HTTP Protection Policy Management
- This API is used to query the protection policy list.
- This API is used to create a protection policy.
- This API is used to query a protection policy.
- This API is used to update a protection policy.
- This API is used to delete a protection policy.
- This API is used to update domain names a policy applies to.
- This API is used to update a protection policy rule.
- EdgeSec HTTP Protection Rule Management - CC
- HTTP Protection Rule Management - Precise Protection
-
HTTP Protection Rule Management - IP Address Blacklist and Whitelist
- This API is used to query IP address blacklist and whitelist rules.
- This API is used to create an IP address blacklist or whitelist rule.
- This API is used to query an IP address blacklist or whitelist rule.
- This API is used to update an IP address blacklist or whitelist rule.
- This API is used to delete a blacklist or whitelist rule.
-
HTTP Protection Rule Management - Geographical Location
- This API is used to query the geolocation access control rules.
- This API is used to create a geolocation access control rule.
- This API is used to query a geolocation access control rule.
- This API is used to update a geolocation access control rule.
- This API is used to delete a geolocation access control rule.
-
HTTP Protection Rule Management - False Alarm Masking
- This API is used to query false alarm masking rules.
- This API is used to add a false alarm masking rule.
- This API is used to query a false alarm masking rule.
- This API is used to update a false alarm masking rule.
- This API is used to delete a false alarm masking rule.
- This API is used to reset a false alarm masking rule.
- HTTP Protection Rule Management - Attack Penalty
- IP Address Group Management
- Security Overview
- Reference Table Management
- DDoS Statistics
- HTTP Statistics
- DDoS Attack Logs
-
Appendix
- Status Code
- Error Codes
-
Troubleshooting
- EdgeSec.00000005 Invalid Parameter
- EdgeSec.00000013 Concurrent Modification Exception
- EdgeSec.00000014 Only Default Enterprise Project Supported (Not support operation in this enterprise project)
- EdgeSec.00000015 Write Operation Not Supported When All Enterprise Projects Are Selected (All enterprise projects do not support the write operation)
- EdgeSec.00000018 Migration of Resources to Non-Default Enterprise Project Not Supported (This version only supports default enterprise project)
- EdgeSec.00000019 Frozen Resources Cannot Be Migrated to or from an Enterprise Project (frozen cannot create eps tag)
- EdgeSec.00000023 Operation Not Supported by the Current Specifications
- EdgeSec.00000025 Invalid Block Time (Invalid block time)
- EdgeSec.00000026 Invalid Whitelist Rule Type (Invalid rule type)
- EdgeSec.00000027 Invalid CC Rule Condition Length (Invalid cc condition length value)
- EdgeSec.00010001 Invalid IAM Service Project (Failed to get IAM projects)
- EdgeSec.00010005 Insufficient WAF Policy Rule Quota
- EdgeSec.00010006 Blacklist and Whitelist Rules of Edge WAF Exceed the Quota
- EdgeSec.00010007 Insufficient IP Address Group Quota of Edge WAF
- EdgeSec.00010008 Insufficient Edge WAF Certificate Quota
- EdgeSec.00030001 Invalid DDoS Overview Parameters (Illegal Elasticsearch Request)
- EdgeSec.00030003 DDoS Overview Query Type Exception (Statistic Type Error)
- EdgeSec.00030002 DDoS Overview Query Type Exception (Search Error)
- EdgeSec.00040007 No Permission To Operate
- EdgeSec.00040013 Insufficient Top-Level Domain Name Quota
- EdgeSec.00040014 Expansion Resource Quota Has Been Used
- WAF.00022002 Resource Already Exists (Domain Already Exists)
- WAF.00014002 Resource Already Exists
- common.01010003 No Purchase Permission
- Obtaining a Project ID
- SDK Reference
-
FAQs
- About the Product
-
About Functions
- How Does EdgeSec Detect SQL Injection, XSS, and PHP Injection Attacks?
- How Do I Obtain the Real IP Address of a Visitor in EdgeSec?
- How Does EdgeSec Block Requests?
- Do I Need to Enable All Ports When Configuring an EdgeSec Whitelist in a Security Group?
- Why Do Cookies Contain the HWEdgeSecSESID or HWEdgeSecSESTIME field?
- Does Edge Security Support Alarm Notifications for Attacks?
- Regions and AZs
- General Reference
Show all
Copied.
IP Address-based Rate Limiting
Attack Example
Attackers can use several hosts to continuously send HTTP POST requests to website www.example.com. Those malicious requests will use up website resources, such as the website connections and bandwidth. As a result, the website fails to respond normal requests and its competitiveness decreases sharply.
Protective Measures
- Based on the access statistics, check whether a large number of requests are sent from a specific IP address. If yes, it is likely that the website is hit by CC attacks.
- Log in to the management console.
- Click in the upper left corner of the page and choose Content Delivery & Edge Computing > CDN and Security.
- In the navigation pane on the left, choose Website Setting under Edge Security.
- In the Policy column of the row containing the target domain name, click the number of enabled protection rules. On the page displayed, confirm that the status of CC attack protection is enabled () and click Customize Rule.
Figure 1 CC Attack Protection configuration area
- Then, customize a CC attack protection rule. In the upper left corner of the page, click Add Rule. In the displayed dialog box, specify the path and rule name, and set Rate Limit Mode to Per IP address, Rate Limit based on service features, and Protective Action to Verification code to prevent blocking legitimate users.
- Rate Limit Mode: Select Source and then Per IP address to distinguish a single web visitor based on IP addresses.
- Rate Limit: Number of requests allowed from a website visitor in the rate limiting period. The visitor's access request is denied if the limit is reached.
- Protective Action: To prevent legitimate requests from being blocked, select Verification code.
- Verification code: EdgeSec allows requests that trigger the rule as long as your website visitors complete the required verification. Currently, cerification code supports English.
- Block: EdgeSec blocks requests that trigger the rule.
- Log only: EdgeSec only logs requests that trigger the rule.
If the number of access requests exceeds the configured rate limit, the visitors are required to enter a verification code to continue the access.
- Go to the Events page, view details about attack events. For details, see Viewing Events.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot