14:I[57429,["/_next/static/chunks/1quy3rt9yzpdl.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/392cpo_yabh47.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/252p5oe_wmfp7.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/3d7iw7rwuckjm.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/2y2gkwlhyx4c8.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/129tlyvqsdtp_.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/0vyr7s0ntw562.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/2ujfuc0z417cf.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/2clonc1g8s8i6.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/0uuiqbtac-3k_.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/2i399vj0k8vm_.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48"],"default"] 18:I[27201,["/_next/static/chunks/1quy3rt9yzpdl.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/392cpo_yabh47.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/252p5oe_wmfp7.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/3d7iw7rwuckjm.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/2y2gkwlhyx4c8.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/129tlyvqsdtp_.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48","/_next/static/chunks/0vyr7s0ntw562.js?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48"],"IconMark"] 15:T4267,

Added

Core
Introduced AI Copilot, a built-in intelligent assistant within Cloud Exchange that helps users configure, troubleshoot, and manage their environment through natural conversation, grounded in official Netskope Cloud Exchange documentation. It offers guided, step-by-step walkthrough for common setup tasks as well as free-form conversational support across configuration, dashboards, and user management proactively surfacing recommendations and flagging specific issues before they become problems. Introduced Posture Assessment, an AI powered capability that reviews Cloud Exchange platform logs, either a single log or a broader set, to surface an overall health verdict, a breakdown of risk by category, a timeline of what happened, and prioritized remediation steps, all backed by citations from official Netskope documentation. Instead of manually digging through logs to diagnose an issue, teams get a clear, guided assessment of their environment’s health. Introduced CRE Auto-Mapper, an AI-assisted field mapping capability for Cloud Risk Exchange (CRE) plugin configuration. When setting up a plugin, users previously had to manually map every field, sometimes dozens, to the corresponding platform field, a slow and error-prone process. With one click, CRE Auto-Mapper now suggests accurate field mappings along with the reasoning behind each suggestion, letting users review, adjust, and confirm them before anything is saved, significantly speeding up plugin setup. Enriched AI Copilot’s knowledge base with documentation for several recently introduced Cloud Exchange capabilities including the Universal Schema Builder, CRE Auto-Mapper, Pre-Upgrade Health Check, AWS Secrets Manager, and Posture Assessment, ensuring it can accurately answer questions and provide guidance on this new functionality from day one. Added diagnostics and usage analytics for AI Copilot, giving administrators visibility into how AI features are being used across the organization. A dashboard breaks down token usage by feature and by user, diagnostic reporting captures the same details for faster troubleshooting and support, and AI usage metrics are now also included in the product analytics shared with Netskope, helping guide future improvements to the feature. Introduced Universal Schema Builder, previously, CRE data could only be used to take action within CRE, and CTE data only within CTE. That boundary is now removed. CRE data can be used to share indicators to CTE, and CTE data can trigger actions in CRE. Additionally, the new Unified Mapping capability merges CRE entities with CTE indicators into a single combined view, providing richer context and a single place to drive actions or sharing across both modules. DLP capabilities, including Exact Data Match (EDM) and Custom File Classification (CFC), are now generally available following extensive validation and performance benchmarking. Added support for AWS Secrets Manager as an external vault provider, so credentials across Cloud Exchange, including plugin configs, tenant tokens, and the LLM provider key, can be referenced from AWS Secrets Manager rather than stored in Cloud Exchange’s database. Secrets are resolved automatically at use time, so rotating a credential in AWS is picked up without any changes needed in Cloud Exchange. Added a Pre-Install/Upgrade/Migration Health Check script for Cloud Exchange that validates system prerequisites, connectivity, virtualization support, and VM specifications against the target version and deployment type. Running it upfront helps teams catch configuration or capacity issues before they go for upgrades ensuring for smoother upgrade experience, with a link to relevant documentation provided once the check completes successfully. Added connectivity checks for Docker to the Cloud Exchange setup script, so registry and repository access issues are flagged upfront rather than surfacing mid-installation. Added support for mapping a Source-type action parameter in CRE to multiple record fields at once, instead of just one, so plugins can now receive combined values, such as several identifiers or tags, from a single matched record. Added native support for CIDR notation as dedicated IOC types in CTE, covering both IPv4 and IPv6 CIDR ranges, so indicators can now represent entire IP ranges instead of only single addresses. Added a “Generate Alert” option to CTE indicator sharing actions, letting shared indicators automatically raise a CTO alert, so teams can trigger notification and ticketing workflows directly from threat indicator sharing. CTO alerts generated from CRE business-rule actions now include the full matched record, such as user, device, or custom entity fields, instead of just the plugin, action, and its parameters, giving teams complete context right in the alert. Added support for the Add to DNS Profile action in the Netskope Risk Exchange plugin. It adds domain names to the allowlist or blocklist of an existing or new DNS profile, with Append and Replace operations. This new feature is not a function of the CE version but a key new feature released at the same time. Added support for the Add to Service Profile action in the Netskope Risk Exchange plugin. It adds TCP, UDP or TCP/UDP ports and port ranges to an existing or new custom service profile, with Append and Replace operations. Invalid port values are skipped and reported. This new feature is not a function of the CE version but a key new feature released at the same time. Added support for the Add to Network Profile action in the Netskope Risk Exchange plugin. It adds IP addresses (including CIDR and range values) to an existing or new network profile. This new feature is not a function of the CE version but a key new feature released at the same time.

Core

Introduced AI Copilot, a built-in
intelligent assistant within Cloud Exchange that helps users configure, troubleshoot, and
manage their environment through natural conversation, grounded in official Netskope Cloud
Exchange documentation.
- It offers guided,
  step-by-step walkthrough for common setup tasks as well as free-form conversational
  support across configuration, dashboards, and user management proactively
  surfacing recommendations and flagging specific issues before they become problems.
Introduced Posture Assessment, an
AI powered capability that reviews Cloud Exchange platform logs, either a single log or a
broader set, to surface an overall health verdict, a breakdown of risk by category, a
timeline of what happened, and prioritized remediation steps, all backed by citations from
official Netskope documentation.
- Instead of manually
  digging through logs to diagnose an issue, teams get a clear, guided assessment of
  their environment’s health.
Introduced CRE Auto-Mapper, an
AI-assisted field mapping capability for Cloud Risk Exchange (CRE) plugin configuration.
- When setting up a plugin,
  users previously had to manually map every field, sometimes dozens, to the
  corresponding platform field, a slow and error-prone process.
- With one click, CRE Auto-Mapper now
  suggests accurate field mappings along with the reasoning behind each suggestion,
  letting users review, adjust, and confirm them before anything is saved,
  significantly speeding up plugin setup.
Enriched AI Copilot’s knowledge
base with documentation for several recently introduced Cloud Exchange capabilities
including the Universal Schema Builder, CRE Auto-Mapper, Pre-Upgrade Health Check, AWS Secrets
Manager, and Posture Assessment, ensuring it can accurately answer questions and provide
guidance on this new functionality from day one.
Added diagnostics and usage
analytics for AI Copilot, giving administrators visibility into how AI features are being
used across the organization.
- A dashboard breaks down
  token usage by feature and by user, diagnostic reporting captures the same details
  for faster troubleshooting and support, and AI usage metrics are now also included
  in the product analytics shared with Netskope, helping guide future improvements to
  the feature.
Introduced Universal Schema
Builder, previously, CRE
data could only be used to take action within CRE, and CTE data only within
CTE.
- That boundary is now
  removed. CRE data
  can be used to share indicators to CTE, and CTE data can trigger actions in CRE.
- Additionally, the new
  Unified Mapping capability merges CRE entities with CTE indicators into a
  single combined view, providing richer context and a single place to drive actions
  or sharing across both modules.
DLP capabilities,
including Exact Data Match (EDM) and Custom File Classification (CFC), are now generally
available following extensive validation and performance benchmarking.
Added support for AWS Secrets
Manager as an external vault provider, so credentials across Cloud Exchange, including
plugin configs, tenant tokens, and the LLM provider key, can be referenced from AWS Secrets
Manager rather than stored in Cloud Exchange’s database.
- Secrets are resolved
  automatically at use time, so rotating a credential in AWS is picked up without any
  changes needed in Cloud Exchange.
Added a
Pre-Install/Upgrade/Migration Health Check script for Cloud Exchange that validates system
prerequisites, connectivity, virtualization support, and VM specifications against the
target version and deployment type.
- Running it upfront helps
  teams catch configuration or capacity issues before they go for upgrades ensuring
  for smoother upgrade experience, with a link to relevant documentation provided once
  the check completes successfully.
Added connectivity checks for
Docker to the Cloud Exchange setup script, so registry and repository access issues are
flagged upfront rather than surfacing mid-installation.
Added support for mapping a
Source-type action parameter in CRE to multiple record fields at once, instead of just
one, so plugins can now receive combined values, such as several identifiers or tags, from a
single matched record.
Added native support for CIDR notation as
dedicated IOC types in CTE, covering both IPv4 and IPv6 CIDR ranges, so indicators can
now represent entire IP ranges instead of only single addresses.
Added a “Generate Alert” option
to CTE indicator sharing
actions, letting shared indicators automatically raise a CTO alert, so teams can trigger
notification and ticketing workflows directly from threat indicator sharing.
CTO alerts generated from CRE business-rule actions now
include the full matched record, such as user, device, or custom entity fields, instead of
just the plugin, action, and its parameters, giving teams complete context right in the
alert.
Added support for the Add to DNS
Profile action in the Netskope Risk Exchange plugin.
- It adds domain names to
  the allowlist or blocklist of an existing or new DNS profile, with Append and
  Replace operations.
- This new feature is not a
  function of the CE version but
  a key new feature released at the same time.
Added support for the Add to
Service Profile action in the Netskope Risk Exchange plugin.
- It adds TCP, UDP or
  TCP/UDP ports and
  port ranges to an existing or new custom service profile, with Append and Replace
  operations.
- Invalid port values are
  skipped and reported.
- This new feature is not a
  function of the CE
  version but a key new feature released at the same time.
Added support for the Add to
Network Profile action in the Netskope Risk Exchange plugin.
- It adds IP addresses
  (including CIDR and
  range values) to an existing or new network profile.
- This new feature is not a
  function of the CE
  version but a key new feature released at the same time.

Changed

Core	UI
Applied security patches by upgrading urllib3 (1.26.19 → 2.7.0), numpy (2.2.5 → 2.5.2), and gunicorn (23.0.0 → 26.2.0) to their latest supported versions, replacing versions that were reaching end-of-life, to maintain security and compatibility. Upgraded the bundled certifi package version (2025.4.26 → 2026.10.19) and Nginx version (1.28.0 → 1.30.3) as part of ongoing security hardening. Upgraded the base operating system for Cloud Exchange as a VM (OVA, AMI, Azure Image, VHDX) to Ubuntu 24.04, now the minimum supported OS version. Customers running Cloud Exchange as a VM should upgrade their underlying OS from Ubuntu 22.04 to Ubuntu 24.04 to stay on a supported, secure foundation. Upgraded the minimum required Python version for Cloud Exchange from 3.11 to 3.12, for both the host OS and the backend service, aligning with the default Python version bundled with Ubuntu 24.04 for better long-term support and compatibility. Upgraded MongoDB from version 8.0.18 to 8.3.4 with the latest security updates and stability improvements. Upgraded RabbitMQ from version 4.2.2 to 4.3.2, which includes RabbitMQ’s shift to Khepri-based metadata storage for improved reliability. When a plugin update affects an existing configuration, whether triggered by upload or a repository sync, Cloud Exchange now displays any upgrade notes provided by the plugin directly in the configuration update dialog, such as new required fields or configuration changes introduced in the new version. This gives administrators clear guidance on what to review while reconciling the configuration, instead of discovering issues only after running into an error. Updated how the global “Generate Alerts” setting interacts with the per-action “Generate Alerts” toggle in CTO and CRE. The global setting now consistently governs alert generation across both modules: when it’s disabled, no alerts are generated regardless of an individual action’s local toggle, and the local toggle becomes read-only with a message directing users to enable the global setting first. When the global setting is enabled, new actions default to generating alerts, while existing actions continue to follow their own local toggle. This makes alert behavior predictable and consistent between CTE and CRE.	Removed the deprecated Netskope WebTx plugin reference from the CLS module product tour and replaced it with the AWS and Azure Log Streaming plugins. The CLS module tour now reflects currently supported plugins.

Core

Applied security patches by upgrading urllib3 (1.26.19 → 2.7.0), numpy (2.2.5 → 2.5.2), and gunicorn (23.0.0 → 26.2.0) to their latest supported versions, replacing versions that were reaching end-of-life, to maintain security and compatibility.
- Upgraded the bundled certifi package version (2025.4.26 → 2026.10.19) and Nginx version (1.28.0 → 1.30.3) as part of ongoing security hardening.
Upgraded the base operating system for Cloud Exchange as a VM (OVA, AMI, Azure Image, VHDX) to Ubuntu 24.04, now the minimum supported OS version.
- Customers running Cloud Exchange as a VM should upgrade their underlying OS from Ubuntu 22.04 to Ubuntu 24.04 to stay on a supported, secure foundation.
Upgraded the minimum required Python version for Cloud Exchange from 3.11 to 3.12, for both the host OS and the backend service, aligning with the default Python version bundled with Ubuntu 24.04 for better long-term support and compatibility.
Upgraded MongoDB from version 8.0.18 to 8.3.4 with the latest security updates and stability improvements.
Upgraded RabbitMQ from version 4.2.2 to 4.3.2, which includes RabbitMQ’s shift to Khepri-based metadata storage for improved reliability.
When a plugin update affects an existing configuration, whether triggered by upload or a repository sync, Cloud Exchange now displays any upgrade notes provided by the plugin directly in the configuration update dialog, such as new required fields or configuration changes introduced in the new version.
- This gives administrators clear guidance on what to review while reconciling the configuration, instead of discovering issues only after running into an error.
Updated how the global “Generate Alerts” setting interacts with the per-action “Generate Alerts” toggle in CTO and CRE.
- The global setting now consistently governs alert generation across both modules: when it’s disabled, no alerts are generated regardless of an individual action’s local toggle, and the local toggle becomes read-only with a message directing users to enable the global setting first.
- When the global setting is enabled, new actions default to generating alerts, while existing actions continue to follow their own local toggle.
- This makes alert behavior predictable and consistent between CTE and CRE.

Removed the deprecated Netskope WebTx plugin reference from the CLS module product tour and replaced it with the AWS and Azure Log Streaming plugins.
- The CLS module tour now reflects currently supported plugins.

16:T21c4,

Core	UI
Fixed an issue where a plugin’s “Failed” run status was not being correctly captured in Cloud Exchange’s product usage analytics reporting. Plugin run status is now accurately reflected in analytics data. Fixed an issue where Cloud Exchange containers would continuously restart on hosts running Linux kernel 6.19 or later, caused by an incompatibility with MongoDB 8.0+. This is a temporary workaround and will be removed once an upstream fix ships in a future MongoDB release (https://jira.mongodb.org/browse/SERVER-131779). Deployments on affected kernels now start up and remain stable. Fixed an issue with Celery and RabbitMQ broker/worker tuning where intermittent network interruptions between Cloud Exchange and its internal task queue could cause background tasks, such as plugin execution, to stall. Cloud Exchange now guards against unsafe task-fetch limits on reconnect and automatically detects and resets stuck task queues, improving reliability in environments with occasional network instability. Fixed an issue where running Run Diagnosis from the Cloud Exchange UI could get stuck indefinitely with the loading indicator spinning, particularly on larger deployments where the process produced a large volume of output. Diagnostic runs now complete reliably and their logs can be downloaded through the UI as expected. Fixed an issue where uploading a custom plugin as a ZIP/TAR file failed with a dependency error, even after its required provider plugin had already been uploaded. Custom plugin uploads with provider dependencies now complete successfully. When a plugin update affects an existing configuration, whether triggered by upload or a repository sync, Cloud Exchange now displays any upgrade notes provided by the plugin directly in the configuration update dialog, such as new required fields or configuration changes introduced in the new version. This gives administrators clear guidance on what to review while reconciling the configuration, instead of discovering issues only after running into an error. Fixed an issue where certain plugin operations, such as retrieving action fields, disabling a plugin, or processing indicator retraction, could read or update the plugin’s stored data without saving those changes to the database. This affected CFC, EDM, CRE, and CTE plugins that rely on stored values, such as file paths, to function correctly. Plugin storage is now consistently synced to the database across all these operations, ensuring plugins work reliably. Fixed an issue with plugin configuration wizards, affecting third-party plugins such as HaloITSM and ServiceNow, where changing a configuration value and proceeding directly to the next step, without saving first, could silently revert to the old value instead of applying the change. As part of this fix, all plugin configuration wizards (ITSM, CFC, EDM, CLS, CTE, and CRE) now also support clicking directly on a step in edit mode to jump to it, with values validated and preserved correctly whether moving forward or backward through the steps. Fixed an issue where sharing indicators to a URL or Destination Profile destination from multiple business rules was incorrectly blocked as a conflicting configuration. Business rules can now share indicators to the same URL or Destination Profile destination across multiple rules without validation errors. Fixed an issue with CTE indicator sharing and retraction statuses that could show inaccurate or inconsistent status values, such as an indicator not showing as “Shared” once successfully shared, or “Retracted” incorrectly applying to indicators that were never shared. Statuses now correctly reflect each indicator’s actual sharing and retraction state. Fixed an issue in the CRE Schema Editor where selecting a normalized field, such as one converted to uppercase and mapped to more than one entity in a plugin, as a Value Map (String/Number) field caused the Cloud Exchange UI to break. Normalized fields can now be used in Value Map configurations without issue. Updated how the global “Generate Alerts” setting interacts with the per-action “Generate Alerts” toggle in CTO and CRE. The global setting now consistently governs alert generation across both modules: when it’s disabled, no alerts are generated regardless of an individual action’s local toggle, and the local toggle becomes read-only with a message directing users to enable the global setting first. When the global setting is enabled, new actions default to generating alerts, while existing actions continue to follow their own local toggle. This makes alert behavior predictable and consistent between CTE and CRE. Fixed an issue in EDM where the “Last Updated At” timestamp did not refresh when a record’s sharing status changed from “Upload Completed” to “Completed.” The timestamp now updates correctly to reflect the latest status change. Fixed an issue in the CFC File Metadata listing where, with a large number of records, navigating between pages could show the same record duplicated across two pages. Pagination now returns a consistent, non-overlapping set of records on every page. Fixed an issue in the DLP Custom File Classification (CFC) module where hash generation was re-triggered for all images during every cycle, even when nothing had changed. Hashing now correctly runs only when an image is actually new or modified, reducing unnecessary processing on large image sets. Fixed a critical issue in CFC where a hash generation failure, such as a disk-full condition or a hashing error, could leave behind an orphaned working directory on disk. Since these leftover files were never cleaned up, repeated failures could accumulate over time and eventually fill the disk entirely, causing MongoDB and Cloud Exchange to stop accepting writes and the UI to become inaccessible. Failed hash generation attempts are now cleaned up automatically, preventing disk space from being consumed by incomplete runs.	Fixed an issue where newly added sharing configurations appeared duplicated on the CTE Shared page. Sharing configurations now display correctly after being added. Fixed an issue in CRE where the Reference section did not correctly display list-type values, showing them improperly instead of as a readable list. Reference section fields now render list values correctly. Fixed an issue in CRE where action parameter values were not retained after a plugin upgrade introduced a new field, causing previously configured values to appear missing. Action parameters now correctly persist across plugin upgrades. Resolved multiple issues on the CRE Business Rule page: Grid view no longer omits rules beyond the tenth entry, sorting by the “Entity” column now functions as expected, and periods entered in rule filter values are no longer incorrectly converted to ampersands. Business rules now display, sort, and save reliably regardless of rule count or filter content. Fixed an issue on the CFC Sharing page where the Customize Columns option did not behave correctly, showing columns such as Actions that should not have been customizable. The Customize Columns option now works as expected on the Sharing page. Fixed an issue when configuring a Linux File Share plugin in CFC where entering an invalid value could cause the form to revert other configuration parameters and directory paths back to their previous values, and a duplicate directory path entry could be silently removed instead of properly flagged. Configuration fields now retain the values entered, with validation errors shown inline without discarding other unrelated input.

Core

Fixed an issue where a plugin’s “Failed” run status was not being correctly captured in Cloud Exchange’s product usage analytics reporting.
- Plugin run status is now accurately reflected in analytics data.
Fixed an issue where Cloud Exchange containers would continuously restart on hosts running Linux kernel 6.19 or later, caused by an incompatibility with MongoDB 8.0+.
- This is a temporary workaround and will be removed once an upstream fix ships in a future MongoDB release (https://jira.mongodb.org/browse/SERVER-131779).
- Deployments on affected kernels now start up and remain stable.
Fixed an issue with Celery and RabbitMQ broker/worker tuning where intermittent network interruptions between Cloud Exchange and its internal task queue could cause background tasks, such as plugin execution, to stall.
- Cloud Exchange now guards against unsafe task-fetch limits on reconnect and automatically detects and resets stuck task queues, improving reliability in environments with occasional network instability.
Fixed an issue where running Run Diagnosis from the Cloud Exchange UI could get stuck indefinitely with the loading indicator spinning, particularly on larger deployments where the process produced a large volume of output.
- Diagnostic runs now complete reliably and their logs can be downloaded through the UI as expected.
Fixed an issue where uploading a custom plugin as a ZIP/TAR file failed with a dependency error, even after its required provider plugin had already been uploaded.
- Custom plugin uploads with provider dependencies now complete successfully.
When a plugin update affects an existing configuration, whether triggered by upload or a repository sync, Cloud Exchange now displays any upgrade notes provided by the plugin directly in the configuration update dialog, such as new required fields or configuration changes introduced in the new version.
- This gives administrators clear guidance on what to review while reconciling the configuration, instead of discovering issues only after running into an error.
Fixed an issue where certain plugin operations, such as retrieving action fields, disabling a plugin, or processing indicator retraction, could read or update the plugin’s stored data without saving those changes to the database.
- This affected CFC, EDM, CRE, and CTE plugins that rely on stored values, such as file paths, to function correctly.
- Plugin storage is now consistently synced to the database across all these operations, ensuring plugins work reliably.
Fixed an issue with plugin configuration wizards, affecting third-party plugins such as HaloITSM and ServiceNow, where changing a configuration value and proceeding directly to the next step, without saving first, could silently revert to the old value instead of applying the change.
- As part of this fix, all plugin configuration wizards (ITSM, CFC, EDM, CLS, CTE, and CRE) now also support clicking directly on a step in edit mode to jump to it, with values validated and preserved correctly whether moving forward or backward through the steps.
Fixed an issue where sharing indicators to a URL or Destination Profile destination from multiple business rules was incorrectly blocked as a conflicting configuration.
- Business rules can now share indicators to the same URL or Destination Profile destination across multiple rules without validation errors.
Fixed an issue with CTE indicator sharing and retraction statuses that could show inaccurate or inconsistent status values, such as an indicator not showing as “Shared” once successfully shared, or “Retracted” incorrectly applying to indicators that were never shared.
- Statuses now correctly reflect each indicator’s actual sharing and retraction state.
Fixed an issue in the CRE Schema Editor where selecting a normalized field, such as one converted to uppercase and mapped to more than one entity in a plugin, as a Value Map (String/Number) field caused the Cloud Exchange UI to break.
- Normalized fields can now be used in Value Map configurations without issue.
Updated how the global “Generate Alerts” setting interacts with the per-action “Generate Alerts” toggle in CTO and CRE.
- The global setting now consistently governs alert generation across both modules: when it’s disabled, no alerts are generated regardless of an individual action’s local toggle, and the local toggle becomes read-only with a message directing users to enable the global setting first.
- When the global setting is enabled, new actions default to generating alerts, while existing actions continue to follow their own local toggle.
- This makes alert behavior predictable and consistent between CTE and CRE.
Fixed an issue in EDM where the “Last Updated At” timestamp did not refresh when a record’s sharing status changed from “Upload Completed” to “Completed.”
- The timestamp now updates correctly to reflect the latest status change.
Fixed an issue in the CFC File Metadata listing where, with a large number of records, navigating between pages could show the same record duplicated across two pages.
- Pagination now returns a consistent, non-overlapping set of records on every page.
Fixed an issue in the DLP Custom File Classification (CFC) module where hash generation was re-triggered for all images during every cycle, even when nothing had changed.
- Hashing now correctly runs only when an image is actually new or modified, reducing unnecessary processing on large image sets.
Fixed a critical issue in CFC where a hash generation failure, such as a disk-full condition or a hashing error, could leave behind an orphaned working directory on disk.
- Since these leftover files were never cleaned up, repeated failures could accumulate over time and eventually fill the disk entirely, causing MongoDB and Cloud Exchange to stop accepting writes and the UI to become inaccessible.
- Failed hash generation attempts are now cleaned up automatically, preventing disk space from being consumed by incomplete runs.

Fixed an issue where newly added sharing configurations appeared duplicated on the CTE Shared page. Sharing configurations now display correctly after being added.
Fixed an issue in CRE where the Reference section did not correctly display list-type values, showing them improperly instead of as a readable list. Reference section fields now render list values correctly.
Fixed an issue in CRE where action parameter values were not retained after a plugin upgrade introduced a new field, causing previously configured values to appear missing.
- Action parameters now correctly persist across plugin upgrades.
Resolved multiple issues on the CRE Business Rule page: Grid view no longer omits rules beyond the tenth entry, sorting by the “Entity” column now functions as expected, and periods entered in rule filter values are no longer incorrectly converted to ampersands.
- Business rules now display, sort, and save reliably regardless of rule count or filter content.
Fixed an issue on the CFC Sharing page where the Customize Columns option did not behave correctly, showing columns such as Actions that should not have been customizable.
- The Customize Columns option now works as expected on the Sharing page.
Fixed an issue when configuring a Linux File Share plugin in CFC where entering an invalid value could cause the form to revert other configuration parameters and directory paths back to their previous values, and a duplicate directory path entry could be silently removed instead of properly flagged.
- Configuration fields now retain the values entered, with validation errors shown inline without discarding other unrelated input.

17:Ta11,

The DLP modules, Custom File Classification (CFC) and Exact Data Match (EDM), are not currently supported on Cloud Exchange as a VM or in HA deployments.
After upgrading from Cloud Exchange 5.x to 7.0.0, AI Copilot may display an outdated proactive DLP module suggestion. As a workaround, enable or disable any module; this re-evaluates the proactive suggestions and discards the outdated one.
Indicators (IOCs) generated from CRE records or the Universal Schema Builder’s unified mapping do not currently support retraction in CTE.
Indicators (IOCs) generated from CRE records or the Universal Schema Builder’s unified mapping are not automatically removed when the originating CRE source plugin is deleted or a record no longer matches.
Cross-module sharing from CRE to CTE does not support changing the field mapping in an existing business rule. As a workaround, create a new business rule with the required field mapping.
With the introduction of native CIDR IOC types, existing IOCs classified as URLs are not automatically reclassified as native IPv4/IPv6 CIDR types. Only newly ingested CIDR indicators are correctly classified.
Fields using the “Append” aggregate strategy, which accumulate multiple values per record, cannot be mapped to a CTE IOC field, since a CTE indicator value must be a single value, not a list. This applies to both classic CRE to CTE business rules and Unified Mapping.
In CFC Manual Upload, duplicate validation is filename-based; the same content uploaded with a different filename is processed as a new file. As a workaround, use a different filename to reprocess the same content.
When the same IOC is shared with multiple destinations or actions, the sharing/retraction status may display as N/A if the IOC is skipped during the latest action execution. In such cases, push retraction is not triggered for the IOC, even if it was successfully shared during a previous execution.
The plugin upgrade dialog will display only mandatory or required fields introduced in the new version. Newly added optional fields must be configured by editing the plugin configuration after the upgrade is complete.
For WebTx-only Log Shipper plugins, the Mapping field in Basic Information is shown and can be selected even though it isn’t used. WebTx data is sent as received, so the selected mapping has no effect on data delivery. Ignore the Mapping field and save with any value.

7:["$","$L14",null,{"url":"new-features-and-enhancements-in-netskope-cloud-exchange-7-0-0","searchParams":"","initialData":{"meta":{"title":"Netskope Cloud Exchange Release Notes Version 7.0.0 - Netskope Technical Documentation","description":"Release Date: Oct 28, 2026 We are excited to announce our release updates! Here’s the new changes, fixed issues, and known issues in this release.","canonical":"https://docs.netskope.com/en/netskope-cloud-exchange-release-notes-version-7-0-0/","robots":"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1","og:locale":"en_US","og:type":"article","og:title":"Netskope Cloud Exchange Release Notes Version 7.0.0 - Netskope Technical Documentation","og:description":"Release Date: Oct 28, 2026 We are excited to announce our release updates! Here’s the new changes, fixed issues, and known issues in this release.","og:url":"https://docs.netskope.com/en/netskope-cloud-exchange-release-notes-version-7-0-0/","og:site_name":"Netskope Technical Documentation","article:publisher":"","article:modified_time":""},"status":200,"post_status":"publish","id":121793,"title":"Netskope Cloud Exchange Release Notes Version 7.0.0","path":"/new-features-and-enhancements-in-netskope-cloud-exchange-7-0-0","last_modified_on":"October 27, 2026","breadcrumbs":[{"id":0,"title":"Home","link":"/"},{"id":34745,"title":"Netskope Cloud Exchange","link":"netskope-cloud-exchange"},{"id":121793,"title":"Netskope Cloud Exchange Release Notes Version 7.0.0","link":"https://docs.netskope.com/en/netskope-cloud-exchange-release-notes-version-7-0-0/","active":"1"}],"type":"release","rn_is_jira":false,"release_note":{"product_id":"34745","sub_title":"7.0.0"},"content":"

Release Date: Oct 28, 2026

We are excited to announce our release updates! Here’s the new changes, fixed issues, and known issues in this release.

","rn_filter":"all","sections":{"new":{"title":"What's New","content":"$15"},"fixed":{"title":"Fixed Issues","content":"$16"},"known":{"title":"Known Issues","content":"$17"}},"warning_message":"","current_user_id":0,"current_user_is_admin":false,"post_author_id":133,"current_user_is_rn_lead":false}}] a:null f:[["$","title","0",{"children":"Netskope Cloud Exchange Release Notes Version 7.0.0 - Netskope Technical Documentation"}],["$","meta","1",{"name":"description","content":"Release Date: Oct 28, 2026 We are excited to announce our release updates! Here’s the new changes, fixed issues, and known issues in this release."}],["$","meta","2",{"name":"robots","content":"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1"}],["$","link","3",{"rel":"canonical","href":"https://docs.netskope.com/en/netskope-cloud-exchange-release-notes-version-7-0-0/"}],["$","meta","4",{"property":"og:title","content":"Netskope Cloud Exchange Release Notes Version 7.0.0 - Netskope Technical Documentation"}],["$","meta","5",{"property":"og:description","content":"Release Date: Oct 28, 2026 We are excited to announce our release updates! Here’s the new changes, fixed issues, and known issues in this release."}],["$","meta","6",{"property":"og:url","content":"https://docs.netskope.com/en/netskope-cloud-exchange-release-notes-version-7-0-0/"}],["$","meta","7",{"property":"og:site_name","content":"Netskope Technical Documentation"}],["$","meta","8",{"property":"og:locale","content":"en_US"}],["$","meta","9",{"property":"og:type","content":"article"}],["$","meta","10",{"name":"twitter:card","content":"summary"}],["$","meta","11",{"name":"twitter:title","content":"Netskope Cloud Exchange Release Notes Version 7.0.0 - Netskope Technical Documentation"}],["$","meta","12",{"name":"twitter:description","content":"Release Date: Oct 28, 2026 We are excited to announce our release updates! Here’s the new changes, fixed issues, and known issues in this release."}],["$","link","13",{"rel":"icon","href":"/_next/static/media/favicon-production.0ugm7_3h94jm2.png?dpl=34b42daf7de27e10d1758af54a2e72f5b78a6c48"}],["$","$L18","14",{}]]