The Version 4.3 comes with the following enhancements:
- Logs to Syslog server. On version 4.3 you can setup one or two Syslog servers where to send the information about Tunnel and Cluster.
- Menu Changes: Two new options added to see the last month logs or last 6 months.
- DNS Resolver timeout reduced to improve response of time of Bypass Proxy when Primary DNS fails or is slow.
- Cosmetic changes on "Show Configuration and Status" menu.
The Version 4.2 comes with the following enhancements:
- Zscalerthree cloud added to to the CSC
The Version 4.1 comes with the following enhancements:
- Watchdog application added. This watchdog will prevent any potential deviation behaviour or memory leak of the process running on the CSCs.
- Bypass proxy allows tunnelling to non standard HTTPS ports. This was requested by several customers using Cloud Services like SAP.
- Egress Bypass Test added to "Configuration and Status" Menu.
The Version 4.0 comes with the following enhancements:
- New! Bypass Proxy functionality : The Bypass Proxy solves the problem when is required to send traffic direct to internet and not via Zscaler ZEN nodes.
The most common case is when destination web site accepts only traffic coming from a specific public IP.
Without the Bypass Proxy, customers where obligated to have an internal proxy or to configure several firewall rules and routes to the destinations required to be bypassed.
The Bypass Proxy simplifies this task: using the Zscaler PAC files servers as repository of your bypasses and automating the task with AWS, you can easily get up to date all your bypasses in all CSC instances.
The Bypass Proxy acts as Web Firewall. It only allows to reach domains hosts defined by the Administrator.
The Version 3.5 comes with the following enhancements:
- New Model: CSC Anywhere One Arm: The purpose of the CSC Anywhere One Arm is to provide a direct replacement of the Web Security Appliance installed on premises. The CSC Anywhere One Arm can be placed on the same subnet than the current appliance and the traffic will be redirected to Zscaler directly.
- Resilient Algorithm: When returning to the Primary ZEN, Resilient Algorithm checks if the Primary ZEN was stable for 15 minutes before to change nodes.
- Timers were adjusted to better support locations with long delays (more than 250 ms) to the ZEN Nodes.
- The CSC is using now three consecutive IPs for the Internal Interface. The first one is the Gateway. The second the VIP Proxy and the Third is reserved for future use.
The Version 3.2 comes with the following enhancements:
- New! Monitoring Tasks Menu: Traceroute and Latency Test. This Test does a MTR (MyTraceRoute) test to Primary & Secondary ZEN and Google DNS. In addition to this, if the tunnel is UP, this test does a MTR test on Reverse from the Zscaler node active to your public IP. This test is similar than the one provided on the Zscaler Analyzer tool with the advantage that has the ability to analyse the reverse path as well.
- New! Monitoring Tasks Menu: Speed Test (Experimental). This test uses a third party tool: speedtest.net . This test provides the Ping delay, Download and Upload Speed.
The Version 3.0 comes with the following enhancements:
- New! "Configuration and Status" Menu. Using this menu, in one shot you will retrieve 25 configuration parameters and will do 14 status checks.
- New! AWS Management. Now, you can manage the CSC Anywhere from AWS as "Managed Instance"
- Added. Shanghai Node was added on the list of Zscaler nodes.
The Version 2.5 comes with the following enhancements:
- ZEN Oslo II added to the configuration
The Version 2.4 comes with the following enhancements:
- Resilient algorithm added to solve the problems when the cloud has intermittent IPSEC problems. See https://trust.zscloud.net/blog/ipsec-based-traffic-forwarding-issue and https://trust.zscloud.net/blog/ipsec-based-traffic-forwarding-issue-0
- VIP Proxy now belong to the same subnet than the Internal Gateway.