Experience Center
Understanding Firewall Capabilities
The Zscaler cloud provides integrated cloud-based next-generation firewall capabilities that allow granular control over your organization's outbound TCP, UDP, and ICMP traffic.
You can configure the following firewall policies:
- Firewall Filtering Policy: Add rules to allow or block specified types of traffic from your network to the internet. You can also specify how the sessions are logged.
- NAT Control Policy: Add rules to perform destination NAT. You can redirect traffic to specific IP addresses or ports.
- DNS Control Policy: Add rules to allow or block DNS requests, redirect requests to a different DNS server, or redirect DNS responses by substituting the IP address in a DNS response with a preconfigured IP address.
- IPS Control Policy: Add rules to control and protect your traffic from intrusion over all ports and protocols using signature-based detection.
Configuring firewall policies requires configuring the four policies in the preceding list as applicable and enabling the firewall for your locations. You might also need to enable IPv6 configuration, create source and destination IP groups, modify network services, create network application groups, and configure custom ports.
Configuring a firewall policy also requires the following:
- An organization must forward its IP traffic from a known location.
- If your organization wants to apply firewall policies at the user level, user authentication and surrogate IP must be enabled. Otherwise, the Zscaler Firewall service applies organization and location policies.
Standard and Advanced Firewall
The following table lists the features and functionalities offered by Standard and Advanced Firewall subscriptions:
Features and Functionalities | Standard Firewall | Advanced Firewall | |
---|---|---|---|
Firewall policies based on the following criteria:
| Supported with limitations:
| Supported | |
Destination NAT: Create rules to redirect your traffic to specific IP addresses and ports within a network using destination NAT. | Supported | Supported | |
FTP Traffic Control: Use configuration settings to manage native FTP traffic and FTP over HTTP traffic. Configure policies to allow access to specific FTP sites. | Supported | Supported | |
DNS Security and Control: Define granular DNS filtering policies to control DNS attributes, requests, and responses. Optimize DNS resolution using Zscaler Trusted DNS Resolver hosted in Zscaler data centers. | Supported (only 64 rules are allowed) | Supported | |
DNS Tunneling: Secure your DNS traffic from DNS tunneling, malicious domains, malware, and phishing attacks. | N/A | Supported | |
IPS Control: Use signature-based IPS to monitor your traffic in real time and protect your network against identified threats over all ports and protocols. | N/A | Supported | |
Non-Standard Traffic Redirection: Identify outbound HTTP, HTTPS, FTP, DNS, RTSP, and PPTP traffic that is destined for non-standard ports and redirect the traffic to the web proxy (secure web gateway) for full web visibility and security. | N/A | Supported | |
Firewall & IPS Dashboards, Insights, and Logs: Analyze your traffic information using customizable dashboards, interactive charts, and real-time logs. | Supported with limitations: Full logging (i.e., detailed logs) is supported only for Block rules; Aggregated logs are supported for Allow rules. Log aggregation happens approximately every 15 minutes. | Supported | |
DNS Dashboards, Insights, and Logs: Analyze your traffic information using customizable dashboards, interactive charts, and real-time logs. | Supported with limitations: Full logging (i.e., detailed logs) is supported only for Block rules; Aggregated logs are supported for Allow rules. Log aggregation happens approximately every 15 minutes. | Supported | |
Miscellaneous: Forwarding Control policy (including Source IP Anchoring) | Supported with limitations: User, group, and department criteria are not supported in the Forwarding Control policy. | Supported |
*Wildcard FQDN support for non-web traffic requires the Zscaler edition that includes parsing of DNS traffic via DNS Control/Security. This capability is available across all new Zscaler editions (2023 editions) and earlier Zscaler editions with Advanced Firewall. Wildcard FQDN match against web traffic (HTTP and TLS/SNI) can function without the need for parsing DNS packets.