Edge Security
  • Overview
  • DDoS Protection
    • DDoS Protection Overview
    • Exclusive DDoS Protection Usage
    • Configuration of Exclusive DDoS protection Rules
      • Increase DDoS Protection Level
      • Exclusive DDoS Traffic Alarm
      • Configuration IP blocklist/allowlist
      • Configuration Region Blocking Rule
      • Configuration Port Filtering
      • Configuration Features Filtering
      • Configuration Protocol Blocking Rule
      • Configuration Connections Attack Protection
      • Related References
        • Action
        • Related Concepts Introduction
  • Web Protection
    • Overview
    • Managed rules
    • CC attack defense
    • Custom rule
    • Custom Rate Limiting Rules
    • Exception Rules
    • Managed Custom Rules
    • Web security monitoring alarm
    • Refer
      • Web Protection Request Processing Order
      • Action
      • Match Condition
  • Bot Management
    • Overview
    • Bot Intelligent analysis
    • Bot Basic Feature Management
    • Client Reputation
    • Active Detection
    • Custom Bot Rule
    • Bot Exception Rule
    • Related References
      • Action
  • Rules Template
  • IP and IP Segment Grouping
  • Origin Protection
  • Custom Response Page
  • Alarm Notification
  • SSL/TLS
    • Overview
    • Deploying/Updating SSL Certificate for A Domain Name
    • Configuring A Free Certificate for A Domain Name
    • HTTPS Configuration
      • Forced HTTPS Access
      • Enabling HSTS
      • SSL/TLS Security Configuration
        • Configuring SSL/TLS Security
        • TLS Versions and Cipher Suites
      • Enabling OCSP Stapling
Docs Overview/
Edge Security/
DDoS Protection/
Configuration of Exclusive DDoS protection Rules/
Configuration Port Filtering/

Configuration Port Filtering

Overview

Port filtering is used to precisely formulate protection strategies by specifying ports and protocols, controlling the ports and protocols that Clients can access EdgeOne. After enabling port filtering, you can customize the combination of protocol Type, source port Range, and destination port Range according to your needs, and set the strategy actions of intercepting, allowing, and continuing protection for the matched rules.
Note：
This function is only supported when L4 proxy is enabled for Exclusive DDoS protection, and Default platform protection and Exclusive DDoS protection for L7 site do not support Configuration.

Usage Scenarios

The origin has UDP business, and UDP reflection attack is filtered through port filtering: If your current origin business has UDP connections and cannot directly block UDP protocol access, you can configure the UDP access port that needs to be intercepted during DDoS washing in port filtering to prevent the transparent transmission of UDP reflection attacks. Common UDP reflection attack ports include: 1-52, 54-161, 389, 1900, 11211.
Wash non-allowed port access sources: When your origin only opens specified ports for access, you can configure the ports that are allowed to be accessed after DDoS washing through port filtering, and directly discard all access connections from other ports to reduce attack penetration.

Directions

For example, for all business domain names under the site example.com, the business only opens TCP protocol ports 110-155 to the outside, and other ports are not allowed to access. The operation steps are as follows:
1. Log in to the EdgeOne console, click on the site list in the left menu bar, click on the site that needs to be configured in the site list, and enter the site details page.
2. On the site details page, click on security protection > DDoS protection to enter the DDoS protection details page.
3. In the L4 proxy protection tab, select the L4 proxy protection instance that needs to be configured, and click on protection Configuration.
4. In the port filtering card, click on set to enter the port filtering page.



5. In the port filtering page, click on Create to create a port filtering rule. In this scenario, create two rules, intercept all protocols and select TCP protocol, fill in the source port Range 1-65535, and fill in the destination port Range 10-155 ports, select different protection actions and fill in the relevant fields, and click Save.



Field
Description
protocol
Optional all, TCP or UDP protocol
source port Range
Refers to the port information of the Client initiating the access, supporting the filling Range: 1-65535
destination port Range
Refers to the destination port information of the Client access, supporting the filling Range: 1-65535
action
Intercept: block the request;
Allow: release the request and no longer match the remaining protection strategies.
Continue protection: release the current request and continue to match the remaining protection strategies.