Netskope Cloud Exchange Release Notes Version 5.1.2 - Netskope Technical Documentation

Release Date: July 7, 2025

Core	UI
Support for more granular maintenance window selection for Risk Exchange Actions. Added support for pulling logs from 3rd-party platforms in the Log Shipper module.	Support for more granular maintenance window selection for Risk Exchange Actions, including the ability to specify days of the week.

Core	UI
Updated python version to 3.11. Updated python libraries. Updated MongoDB version to 8.0.6. Updated RabbitMQ version to 4.1.0. Enhanced plugin configuration disable and delete workflow. Cloud Exchange as a VM (OVA and Hyper-V) users will be asked for cteadmin password each time the command is run with the sudo prefix. Log Shipper and Ticket Orchestrator plugin execution workflow to support storing of additional data in the plugin configuration.	CSP headers for more secure access of UI.

Core

Updated python version to 3.11.
Updated python libraries.
Updated MongoDB version to 8.0.6.
Updated RabbitMQ version to 4.1.0.
Enhanced plugin configuration disable and delete workflow.
Cloud Exchange as a VM (OVA and Hyper-V) users will be asked for cteadmin password each time the command is run with the sudo prefix.
Log Shipper and Ticket Orchestrator plugin execution workflow to support storing of additional data in the plugin configuration.

CSP headers for more secure access of UI.

Core	UI
NA	NA

Core	UI
Fixed the workflow when the required approval is disabled for Risk Exchange Actions. Fixed an issue for the Ticket Orchestrator Queue configuration to support all the fields for direct mapping. Fixed the Filtering capability on complex fields through Business rules (like list and nested objects). Fixed Risk Exchange default schema indexes. Fixed setup script to avoid redundant sudo prefix. Fixed the Threat Exchange Sharing configuration update workflow to limit the use of same Netskope targets (like File Hash list and URL list). Fixed a filtering issue for the dlp_incident_id, connection_id, app_session_id, dlp_parent_id, and browser_session_id fields in Business rules. Fixed the length limitation for the maintenance password.	Fixed the Ticket Orchestrator page rendering issue when an alert or event is expanded. Fixed the Risk Exchange Actions update workflow to adapt changes of the plugin Action labels and parameters.

Core

Fixed the workflow when the required approval is disabled for Risk Exchange Actions.
Fixed an issue for the Ticket Orchestrator Queue configuration to support all the fields for direct mapping.
Fixed the Filtering capability on complex fields through Business rules (like list and nested objects).
Fixed Risk Exchange default schema indexes.
Fixed setup script to avoid redundant sudo prefix.
Fixed the Threat Exchange Sharing configuration update workflow to limit the use of same Netskope targets (like File Hash list and URL list).
Fixed a filtering issue for the dlp_incident_id, connection_id, app_session_id, dlp_parent_id, and browser_session_id fields in Business rules.
Fixed the length limitation for the maintenance password.

Fixed the Ticket Orchestrator page rendering issue when an alert or event is expanded.
Fixed the Risk Exchange Actions update workflow to adapt changes of the plugin Action labels and parameters.

Earlier versions of the Netskope ITSM (Ticket Orchestrator) plugin did not support filtering on fields with complex data types, such as lists of strings, dictionaries, or lists of dictionaries in alerts/events. In order to fix this issue, upgrade to the Ticket Orchestrator plugin version 2.2.0 (or the latest version available), included with the Cloud Exchange v5.1.2 onwards.
In case of an action label change for Risk Exchange plugins, user may see the previous label for the configured actions until the actions updated again.
Business rule filtering for the fields value having is not supported.
When the static Risk Exchange action parameters value starts with $, it will be treated as Source type of action parameter only.
Intermittently few of the celery tasks may gets stuck and cause disk pile up. Restarting Cloud Exchange should resolve the issue.
If you migrate from 5.0.1 to 5.1.2, User Risk Exchange and Application Risk Exchange records will be listed in the Risk Exchange module, but they will not be qualified for the actions until the same records are pulled again from the source.