Edge Security
  • DDoS and Web Protection
    • Overview
    • DDoS Protection
      • DDoS Protection Overview
      • Exclusive DDoS Protection Usage
      • Configuration of Exclusive DDoS protection Rules
        • Increase DDoS Protection Level
        • Configuration IP blocklist/allowlist
        • Configuration Region Blocking Rule
        • Configuration Port Filtering
        • Configuration Features Filtering
        • Configuration Protocol Blocking Rule
        • Configuration Connections Attack Protection
        • Exclusive DDoS Traffic Alarm
        • Related References
          • DDoS Protection Processing Order
          • Action
          • Related Concepts Introduction
      • Related References
        • DDoS Protection Console Update (2026-01-12)
    • Web Protection
      • Overview
      • Configuring Web Protection Policy
      • Custom rule
      • Rate Limiting
        • Bandwidth Abuse Protection
        • CC attack defense
        • Custom Rate Limiting Rules
      • Hosting Rules
        • Managed rules
        • High-Frequency Scan Protection
      • Exception Rules
      • Managed Custom Rules
      • Web security monitoring alarm
      • Related References
        • Web Protection Request Processing Order
        • Action
        • Match Condition
    • Bot Management
      • Overview
      • AI Crawler Control
      • Bot Intelligent analysis
      • Bot Basic Feature Management
      • Client Reputation
      • Active Detection
      • Custom Bot Rule
      • Client authentication (Beta)
        • Overview
        • Attestation Flow
        • Integration Guidelines
          • Step 1: Configure Authentication Method
          • Step 2: Integrate Client Authentication
            • Browser & WebView Integration
            • iOS Integration
            • iOS Integration
            • Mobile Integration References
          • Step 3: Configure Client Attestation Rules
          • Step 4: Verify Client Attestation
      • Related References
        • Action
    • API Discovery(Beta)

Configuration Protocol Blocking Rule

Function Description

EdgeOne supports one-click blocking of source traffic to the site by protocol type. You can configure ICMP protocol blocking, TCP protocol blocking, UDP protocol blocking, and other protocol blocking. After the configuration is complete, when the attack traffic is detected with related access request, it will be directly truncated.
Note:
This function is only supported when L4 proxy instance is set to Advanced Protection or Ultimate Protection, and configuration is not allowed in all other scenarios.

Usage Scenarios

When your website does not have a specified access protocol, you can block the specified protocol with one-click blocking, and directly filter the access requests of the corresponding protocol during traffic cleaning to prevent the corresponding requests from being transparently transmitted to the origin.
Note:
Due to the connectionless nature of the UDP protocol (unlike TCP, which has a three-way handshake process), it has a natural security flaw. If you do not have UDP business, it is suggested to block the UDP protocol.

Operation Steps

For example, for all business domains under the site example.com, only TCP protocol connections are open to the outside, and other protocol requests are blocked. The operation steps are as follows:
1. Log in to the Tencent Cloud EdgeOne console, enter Service Overview in the left menu bar, and click the site to be configured under Website Security Acceleration.
2. On the site details page, click L4 Proxy > L4 Instance List to access the L4 Proxy List page.
3. Select the L4 proxy instance to be configured and click Protection Policy Configuration.
4. In the protocol blocking card, click on the set to enter the protocol blocking page.



5. On the protocol blocking page, click on the switch

of the required protocol blocking, in this scenario, turn on the ICMP protocol, UDP protocol blocking, and other protocol blocking switches. Once enabled, the rule will take effect immediately, and the corresponding protocol requests will be blocked.