Cloud Firewall
Cloud Firewall
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Creating a User Group and Granting Permissions
- Checking the Dashboard
- Purchasing and Changing the Specifications of CFW
- Enabling Internet Border Traffic Protection
- Enabling VPC Border Traffic Protection
-
Configuring Access Control Policies to Control Traffic
- Access Control Policy Overview
- Configuring Protection Rules to Block or Allow Traffic
- Adding Blacklist or Whitelist Items to Block or Allow Traffic
- Viewing Protection Information Using the Policy Assistant
- Managing Access Control Policies
- Managing IP Address Groups
- Domain Name Management
- Service Group Management
- Attack Defense
- Viewing Traffic Statistics
- Viewing CFW Protection Logs
- System Management
- Viewing Audit Logs
- Viewing Monitoring Metrics
-
Best Practices
- CFW Best Practice Summary
- Purchasing and Querying CFW via API
- Migrating Security Policies to CFW in Batches
- Configuration Suggestions for Using CFW with WAF, Advanced Anti-DDoS, and CDN
- Allowing Internet Traffic Only to a Specified Port
- Allowing Outbound Traffic from Cloud Resources Only to a Specified Domain Name
- Using CFW to Defend Against Network Attacks
-
API Reference
- Before You Start
- API Overview
- API Calling
-
API
- Domain Name Management
- VPC Protection
- Rule Hit Count
- IPS Switch Management
- East-west Protection
- ACL Rule Management
- Blacklist and Whitelist Management
- Log Query Management
- Protection Mode Management
- Cloud Firewall Information Management
- Service Group Management
- Service Group Member Management
- EIP Management
- Address Group Member Management
- Address Group Management
- Appendix
- Change History
- SDK Reference
-
FAQs
-
About the Product
- Does CFW Support Off-Cloud Servers?
- Can CFW Be Shared Across Accounts?
- What Are the Differences Between CFW and WAF?
- What Are the Differences Between CFW, Security Groups, and Network ACLs?
- How Does CFW Control Access?
- What Are the Priorities of the Protection Settings in CFW?
- Can WAF and CFW Be Deployed Together?
- How Long Are CFW Logs Stored by Default?
- Regions and AZs
- Troubleshooting
-
Network Traffic
- How Do I Calculate the Number of Protected VPCs and the Peak Protection Traffic at the VPC Border?
- How Does CFW Collect Traffic Statistics?
- What Is the Protection Bandwidth Provided by CFW?
- What Do I Do If My Service Traffic Exceeds the Protection Bandwidth?
- What Are the Differences Between the Data Displayed in Traffic Trend Module and the Traffic Analysis Page?
- How Do I Verify the Validity of an Outbound HTTP/HTTPS Domain Protection Rule?
- Billing
-
About the Product
- Videos
On this page
Help Center/
Cloud Firewall/
Best Practices/
Allowing Outbound Traffic from Cloud Resources Only to a Specified Domain Name
Allowing Outbound Traffic from Cloud Resources Only to a Specified Domain Name
Updated on 2024-10-11 GMT+08:00
Application Scenarios
To prevent sensitive data leakage or external attacks, you need to restrict the Internet domain names that can be accessed by cloud resources.
Use CFW to implement refined management and control on cloud resources and allow access traffic from all EIPs to ports 80 and 443 of a specified domain name. (Wildcard domain name *.example.com is used as an example).
Procedure
- Purchase the CFW standard or professional edition. For details, see Purchasing CFW.
- In the navigation pane on the left, click
and choose Security & Compliance > Cloud Firewall. The Dashboard page will be displayed.
- (Optional) If the current account has only one firewall instance, the firewall details page is displayed. If there are multiple firewall instances, click View in the Operation column of a firewall to go to its details page.
- Enable protection for an EIP.
- In the navigation pane, choose Assets > EIPs. The EIPs page is displayed. The EIP information is automatically updated to the list.
- In the row of the EIP, click Enable Protection in the Operation column.
- Configure protection rules.
- In the navigation pane, choose Access Control > Access Policies.
- Click Add Rule. On the Add Rule page, configure protection information and set other parameters as needed.
Configure the following protection rules:
- One of the rule blocks all traffic. The priority is the lowest.
- Direction: Outbound
- Source: Any
- Destination: Any
- Service: Any
- Application: Any
- Protection Action: Block
- The other rule allows the traffic to ports 80 and 443 of *.example.com, as shown in Figure 1. The priority is the highest.
- Direction: Outbound
- Source: Any
- Destination: Select Domain name/domain group and then Application. Select Domain name from the drop-down list and enter *.example.com.
- Service: TCP/1-65535/80 and TCP/1-65535/443
- Application: HTTP and HTTPS
- Action: Allow
- One of the rule blocks all traffic. The priority is the lowest.
- View the rule hits in access control logs.
In the navigation pane, choose Log Audit > Log Query. Click the Access Control Logs tab.
NOTE:
In the rows where Destination IP is a domain name matching example.com, the corresponding Action is Allow. For other traffic, the Action is Block.
References
- For details about how to configure a domain name group, see .
- For details about how to add other protection rules, see the parameter description in Adding a Protection Rule.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.