Help Center/ Cloud Firewall/ User Guide/ Access Control/ Configuring VPC Border Protection Rules/ Configuring Protection Rules to Block or Allow VPC Border Traffic
Updated on 2026-09-23 GMT+08:00
View PDF
Share

Configuring Protection Rules to Block or Allow VPC Border Traffic

Scenario

After protection is enabled with no access control policy configured, CFW allows all traffic by default. You can configure protection rules to allow or block east-west traffic between VPCs, or between a VPC and an IDC. Refined control by private IP address, port, and domain name is supported to meet intranet access control, intrusion prevention, and compliance audit requirements.

This section describes how to configure protection rules for a VPC border firewall.

Protection Rule Description

The protected objects, actions, and application scenarios of protection rules are as follows.

Name

Description

Protected object
  • 5-tuples
  • IP address groups
  • Geographical locations
  • Domain names and domain name groups (layer-4 and layer-7 traffic)
  • Applications

Network type
  • EIP
  • Private IP address

Action
  • If Block is selected, traffic will be blocked.
  • If Allow is selected, traffic will be allowed by protection rules and then checked by IPS.

Scenario
You can configure protection rules in the following scenarios:
CAUTION:

If your IP address is a back-to-source WAF IP address, you are advised to configure a protection rule or the whitelist to allow its access. Exercise caution when configuring a protection rule to block access, which may affect your services.

Specification Limitations

Only the professional edition supports VPC border traffic protection.

Constraints

Type

Description

Quota limit
  • A maximum of 20,000 protection policies (protection rules and blacklist/whitelist rules) can be added to a firewall instance.
  • The restrictions on a single protection rule are as follows:
    • For IPv4, up to 4,000 source and 4,000 destination IP addresses are allowed. For IPv6, up to 2,000 source and 2,000 destination IP addresses are allowed.
    • A maximum of 20 source IP addresses and 20 destination IP addresses can be added.
    • A maximum of 10 source IP address groups and 10 destination IP address groups can be associated.
    • A maximum of 10 services can be added.
    • A maximum of 10 service groups can be associated.
    • Up to 10 application domain names can be added to each protection rule.
    • Up to 8 application domain name groups can be associated with each protection rule.
    • Up to three network domain names can be added to each protection rule.
    • Only one network domain name group can be associated with each protection rule.

Restrictions on domain name protection
  • Domain names in Chinese are not supported.
  • Restrictions on application-layer domain name reference:
    • Each firewall instance can reference up to 60,000 domain names.
    • Each firewall instance can reference up to 1,000 wildcard domain names.
    • Each protection rule can reference up to 20,000 domain names.
    • Each protection rule can reference up to 128 wildcard domain names.

    Calculation: If both rule A and rule B of a firewall reference domain name 1 and domain name group A (containing domain names 2 and 3), then the number of domain names referenced by rule A or rule B is 3, and the number of domain names referenced by the firewall instance is 6.

  • A network domain name group can resolve up to 4,000 IP addresses (depending on the numbers of IP addresses and IP address groups). Each domain name can have a maximum of 1,000 resolution results. If the number of DNS resolution results exceeds this number, domain names may fail to be accessed. For domain names with a large number of resolution results or frequent changes, to protect HTTP or HTTPS traffic, you are advised to use the application domain name group to add policies.

    The total quota available for a network domain name group is calculated as follows: Assume we have a protection rule that has 10 IP addresses and references an IP address group (A) and a network domain name group (B). The IP address group A contains five IP addresses, and the network domain name group B contains 15 domain names. In this case, the total quota available for the network domain name group B = 4,000 (total quota) – 10 (number of IP addresses) – 5 (number of IP address group members) = 3,985.

  • Domain name protection depends on the DNS server you configure. The default DNS server may be unable to resolve complete IP addresses. You are advised to configure DNS resolution if the domain names of your services need to be accessed.

Restrictions on regions

A protection rule with its source or destination set to a region (geographical location) takes effect only for IPv4 protected objects.

Other restrictions
  • CFW does not support application-level gateways (ALGs). If ALG-related services (such as SIP and FTP) are available, you are advised to add a rule to allow the traffic to pass through all the ports of data channels (that is, set Service to Any and Protection Action to Allow).
  • To use CFW persistent connections, enable a bidirectional bypass policy. If you only enable a unidirectional policy, the client will need to re-initiate connections in certain scenarios, such as enabling or disabling protection, and expanding engine capacity. You can also create a service ticket to evaluate the risks of related issues.
  • If NAT 64 protection is enabled and IPv6 access is used, allow traffic from the 198.19.0.0/16 CIDR block to pass through. NAT64 will translate source IP addresses into the CIDR block 198.19.0.0/16 for ACL access control.

Impacts on Services

When configuring a blocking rule, if address translation or proxy is involved, evaluate the impact of blocking IP addresses with caution.

Adding a VPC Border Protection Rule

  1. Enable VPC border firewall protection. For details, see Enabling VPC Border Traffic Protection.
  2. (Optional) To add multiple IP addresses, domain names, and services (protocols, source ports, and destination ports), add their groups first.

  3. In the navigation pane of the CFW console, choose Protection Policies > Access Control > VPC Border Protection Rules. The VPC Border Protection Rules page is displayed.
  1. Add a protection rule.

    On the Protection Rules tab, click Add Rule. Configure protection information.
    Table 1 Adding a VPC border protection rule

    Parameter

    Description

    Name

    Name of a custom protection rule. It must meet the following requirements:

    • It can contain 1 to 255 characters.
    • The name can contain only letters, numbers, underscores (_), and hyphens (-).

    Source
    Set the party that initiates a session.
    • IP Address/IP address group:
      • IP Address: You can set a single IP address, consecutive IP addresses, or an IP address segment.
        • A single IP address, for example, 192.168.10.5
        • Consecutive IP addresses, for example, 192.168.0.2-192.168.0.10
        • Address segment, for example, 192.168.2.0/24
      • IP address group: A collection of IP addresses. For details, see Adding an IP Address Group.
    • Any: any source address

    Destination
    Set the recipient of a session.
    • IP Address/IP address group/Domain name/Domain name group:
      • IP Address: You can set a single IP address, consecutive IP addresses, or an IP address segment.
        • A single IP address, for example, 192.168.10.5
        • Consecutive IP addresses, for example, 192.168.0.2-192.168.0.10
        • Address segment, for example, 192.168.2.0/24
      • IP address group: A collection of IP addresses. For details, see Adding an IP Address Group.
      • Domain Name/Domain Name Group: Domain names or domain groups can be protected.

        Application: One or multiple domain names or wildcard domain names can be protected. The setting applies to application-layer protocols, including HTTP, HTTPS, TLS, SMTPS, and POPs. Domain names are used for matching.

    • Any: any destination address

    Service
    • Service/Service group:
      • Service: Set Protocol, Source Port, and Destination Port.
        • Protocol: The value can be TCP, UDP, or ICMP.
        • Source/Destination Port: If Protocol is set to TCP or UDP, you need to set the port number.

          To specify all the ports of an IP address, set Port to 1-65535.

          You can specify a single port. For example, to manage access on port 22, set Port to 22.

          To set a port range, use a hyphen (-) between the starting and ending ports. For example, to manage access on ports 80 to 443, set Port to 80-443.

      • Service group: A collection of services (protocols, source ports, and destination ports).

        For details about how to add a custom service group, see Adding a Service Group. For details about predefined service groups, see Viewing a Predefined Service Group.

    • Any: any protocol type or port number

    Application
    (Optional) Configure a protection policy for application-layer protocols. This parameter is mandatory when Destination is set to Domain Name/domain Group.
    • If Service is set to Any, all application types are supported.
    • If Service is set to Service and Protocol is set to TCP, TCP applications, such as HTTP and HTTPS, are supported.
    • If Service is set to Service and Protocol is set to UDP, UDP applications, such as DNS and RDP, are supported.

    Select an application-layer protocol based on the value of Protocol under Service. If no protocol is selected, this parameter is set to Any by default.

    Protection Action
    Set the action to be taken when traffic passes through the firewall.
    • Allow: Traffic is forwarded.
    • Block: Traffic is not forwarded.

    Status
    Whether a protection rule is applied immediately.
    • : The policy takes effect immediately after being configured.
    • : The policy is disabled.

    Priority
    Set the priority of the rule. If multiple security policies are configured, the security policies will be matched based on their priorities. Once traffic matches a security policy, it will not be checked against others. Assign priorities carefully. Specific policies should take precedence over general ones.
    • Pin on top: indicates that the priority of the policy is set to the highest.
    • Lower than the selected rule: indicates that the policy priority is lower than a specified rule.

    Schedule Management

    (Optional) Click Schedule Management and configure when the rule is in effect. Select or add a schedule.

    Allow Long Connection

    If only one service is configured in the current protection rule and Protocol is set to TCP or UDP, you can configure the service session aging time (unit: second).

    Long Connection Duration

    If Allow Long Connection is set to Yes, you need to set the persistent connection duration and set hour, minute, and second.

    Tag

    (Optional) Tags are used to identify rules. You can use tags to classify and search for protection rules.

    Description

    (Optional) Usage and application scenario

  2. Click OK to complete the protection rule configuration.

Viewing Protection Rule Hits

After your services run for a period of time, you can view the number of rule hits in the Hits column of the protection rule list.

You can click a number in the Hits column to go to the Access Control Logs tab page and view log details. For details, see Log Query.

Figure 1 Viewing logs

Follow-up Operations

Checking protection outcomes: After your services run for a period of time, you can check the protection rule hits and adjust them in time.

Related Operations/Documents

After adding a protection rule, you can edit, delete, and adjust the priority of the rule in the rule list.

Parent Topic: Configuring VPC Border Protection Rules