هذه الصفحة غير متوفرة حاليًا بلغتك المحلية. نحن نعمل جاهدين على إضافة المزيد من اللغات. شاكرين تفهمك ودعمك المستمر لنا.
- 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 a BOT Protection Rule
- 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
- 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
Copied.
Features
DDoS Attack Protection
On the basis of advanced feature identification algorithms, Edge Anti-DDoS of EdgeSec detects traffic in a unified and accurate manner. After identifying attacks, Edge Anti-DDoS can quickly clean the traffic and defend against various heavy-traffic attacks, such as SYN flood, UDP flood, and ICMP flood, ensuring service stability.
The EdgeSec node network is built based on the distributed architecture and intelligently schedules global load balancing. When the attack traffic in a CDN edge site reaches the cleaning threshold, the traffic is scheduled to the nearest AAD equipment room with higher bandwidth to cope with ultra-large DDoS attacks and ensure smooth and stable service access in the case of burst attacks.
CC attack prevention
A CC attack protection rule can limit access to a specific path (URL) of the protected website based on a specific IP address in access requests. EdgeSec can accurately identify and mitigate CC attacks, such as brute-force attacks by exploiting weak passwords. Protective actions of CC attack protection rules include Verification code, Block, and Log only.
Basic Web Protection
Backed by an extensive preset reputation database, EdgeSec defends against the Open Web Application Security Project (OWASP) top 10 threats, vulnerability exploits, web shells, and other threats.
- All-around protection
EdgeSec detects and blocks varied attacks, such as SQL injection, XSS, remote overflow vulnerabilities, file inclusions, Bash vulnerabilities, remote command execution, directory (path) traversal attacks, unauthorized sensitive file access, command/code injections, and XML or Xpath injection attacks.
- Web shell detection
- Precise threat identification
- EdgeSec uses built-in semantic analysis engine and regex engine and supports configuring of blacklist/whitelist rules so that EdgeSec has a low false positives rate.
- EdgeSec can automatically decode common codes no matter how many times they are encoded.
EdgeSec can decode the following types of code: url_encode, Unicode, XML, OCT, hexadecimal, HTML escape, and base64 code, case confusion, JavaScript, shell, and PHP concatenation confusion
- Deep Inspection
EdgeSec 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.
- Header Inspection
- Shiro Decryption Check
EdgeSec uses AES and Base64 to decrypt the rememberMe field in cookies and checks whether this field is attacked.
Anti-Crawler Protection
EdgeSec dynamically analyzes website service models and accurately identifies multiple crawler behaviors based on data risk control and bot identification systems.
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