Netskope Cloud Exchange Release Notes Version 5.0.0

Netskope Cloud Exchange Release Notes Version 5.0.0

We are excited to announce our Cloud Exchange 5.0.0 updates! Here’s the latest features, fixed issues, and known issues in this release.

New Features and Enhancements


  • Enabled High Availability with Active-Active clustering in Cloud Exchange, allowing deployment with a minimum of 3 nodes.
  • Introduced Cloud Exchange deployment as a virtual machine, supporting various formats including OVA, VMDK, AMI and VHDX. CE as VM feature will remain in BETA for CE v5.0.0.
  • Added Netskope Analytics details into Diagnostic script which will be helpful for troubleshooting.
  • Enhanced throughput and reliability through memory and disk utilization optimization across all modules.
  • Handled data prevention by adding CLS Retry mechanism in CLS Module settings.
  • Added rebranded types like ips, c2 for ctep alert types into CLS-CTO Module’s business rule, UI filters.
  • Added cluster status in Home dashboard for High availability nodes.
  • Added CLS Retry Mechanism Settings in CLS Module Settings.


  • Changed the field name from Total WebTx Sent to External Receiver to Total WebTx Sent to Storage Buckets on the CLS Dashboard to avoid confusion.
  • Changed the field name from Total WebTx Sent to External Receiver to Total WebTx Sent to Storage Buckets on the CLS Dashboard.


  • Eliminated Page size settings in CLS Module Settings, as they are no longer applicable with the introduction of data export endpoints in Netskope CE.
  • Removed Page size Settings under CLS Module Settings.

Fixed Issues in Version 5.0.0

  • Fixed an issue in SSO by adding force authentication option in SSO configuration to handle multiple authentication methods.
  • Fixed an issue in a CTE Exception Rule where tags query is not working as expected.
  • Fixed an issue where self-learned fields are not displayed under match fields in a Duplication rules.
  • Added a Force authentication toggle button in SSO Configuration page.

Known Issues in Version 5.0.0

  • The VM status is showing not ready on Azure portal while deploying VHDX.
  • In the High Availability feature, Load balancer like HA Proxy needs to be configured by customer in order to use SSO feature.
  • In the High Availability feature, IP addresses of VMs will be required in order to setup. Hostname of VMs are not supported.
  • There is no direct upgrade path for CE as a VM from CE v5.0.0 to newer version. You’ll need to set up a new VM using a respective image, and need to follow the backup and restore option.
  • Historical pulling of tasks that are in progress will be lost on a restart of CE containers or reboot of a VM. You’ll need to do a manual sync after restart/reboot.
Share this Doc
In this topic ...