Sensitive Data Platform (SDP) Console 13.6 Release Notes

Release: 13.6

Release Date: 2.9.2026

 

Known Issues

None.

 

Enhancements

  1. Users can begin User Level Remediation activity immediately upon completion of results by target, once its scan is complete without regard to the completion status of all other targets in the scan.

  2. Users can now filter differential scan results. When viewing differential scan results, users can now use a “Search History” drop-down menu to filter results for the following: All Results (default), Scanned Results, Skipped Results

  3. Results performance improved. Processing deferred locations (Deferred Location Query and ProcessSkippedLocations Query) now use their own index for efficiency.

  4. Attachment generation migrated from SearchPersistence to AgentController and refactored.

  5. Spirion Sensitive Data Platform Users can now control when Spirion agents use compression via the UI.

  6. Job status for DataWarehouseRefreshHandler now provides status entries explicitly indicating success or failure.

  7. Improved Kafka resiliency by explicitly controlling how and when Kafka may remove the consumers.

  8. Users can now upload specific files to the Global Ignore List from which File Hash entries are generated for use in pattern matching. This enables users to skip specific files, identified by hash.

  9. Refactored GetPolicies API to make Policy Generation faster and more efficient for customers with large volumes of agents

  10. When creating a scan, users can now select one or more Global Ignore Lists from the “Advanced” scan wizard panel as part of the scan. This optional setting enables users to ignore specific data matches or types of data matches.

  11. You can now add Location entries for a Global Ignore List using pattern matching, which enables you to skip identified sensitive data locations based on name/path

  12. A policy queueing mechanism has been added to Spirion Sensitive Data Platform so that Spirion Agents receive policy updates in a timely manner, optimize timeouts, and reduce overall transaction time.

  13. When creating a custom report, on the “Columns Setup” screen when including “Matches > Data Type Name,” Search API entries are both included in results and available as a search filter.

  14. Generated policies can now be saved so that they can be retrieved asynchronously by the Agent. Multiple agents can now request policies without encountering timeouts, deadlocks, and delays.

  15. Custom sensitive data definitions can now be used with Search API data types.

 

Bug Fixes

  1. Resolved an issue in which workflow attachments generated for distributed search remain in pending state

  2. Recovery method of org00002 databases set to simple instead of transactional

  3. Kafka client in Svc-Ingress upgraded to the newest version

  4. Data Type in Scan Results table can now be populated. Within Report Filters, "Data Type" is now available.

  5. Resolved an issue in which the "Location Details" dialog displays no entries after performing a MIP Label override

  6. Console updated to use crypto-js version 4.2.0 which resolves security vulnerability.

  7. Resolved unmasked sensitive data being returned to console. When configuring what portion of an SSN/CCN match to send to the console configuration is done via agent policy instead of scan policy.

  8. Resolved a 500 error that is thrown when importing custom data types via CSV file.

  9. Resolved an issue for non-admin users who see scan results load, but total match count fail with an error

  10. Resolved an issue in which an API call time out results in the COVERAGE & DATA TYPES tab of the Asset Details page appearing empty

  11. Resolved an issue in which recurring scheduled searches run once and never recur because the task gets deleted as a duplicate task

  12. Resolved an issue in which agents may try to consume a message through shipper that is larger than allowed. This resulted in 413 "MessageSizeTooLarge" errors in IFS logs.

  13. Resolved an issue in which the logic available to Sensitive Data Definitions could not be used to define Custom Search API data types

  14. Resolved an issue in which performing the Generate export function from the Custom Reports page results in a “Failed” status message

  15. Resolved an issue in which MIP labels were not applied to files.

  16. Installation page removed from UI

  17. SearchPersistence retries “consumed message” processing updated to 2 retries, by default, to improve performance

  18. Resolved an issue in which remote distributed scans scheduled to run later instead of immediately results in fewer than all Agents participating in the scan when the scan triggers.