What's new in Forcepoint DSPM 3.4

Snowflake DSPM Connector Support for Structured Data

Customers can discover, scan, classify, and risk-assess structured data in Snowflake's AI Data Cloud through a new dedicated connector.

For detailed information, refer to the Snowflake section.

Multi-proxy Support

Multi proxy support enables each connector to operate with its own dedicated proxy configuration instead of relying on a single global proxy. This allows every connector to meet its individual requirements, security policies, and network routing preferences. For example, the Azure AD connector can use one proxy while the OneDrive connector uses another. Multi‑proxy support is enabled across all cloud‑based and on‑premises connectors.

For detailed information, refer to the Global Settings section.

SMTP Email Service for On‑Premises DSPM Customers

On-Premises DSPM customers can configure their own SMTP service for system email notifications, as an alternative to the existing Mailchimp integration. This gives customers full control over email delivery and aligns with internal compliance requirements.

For detailed information, refer to the Email Configuration section.

iManage On‑Premises Support

DSPM can connect to on-premises iManage deployments for file scanning, trustee discovery, classification, and remediation actions. This extends DSPM's existing iManage Cloud support to cover customers running iManage on-premises - common in legal and professional services firms.

For detailed information, refer to the Registering an app for iManage on-premise section.

Improvements to Detector Syncing, Visibility, and Customization

This release introduces major enhancements to detector management, visibility, and configuration, making it faster and easier to work with AI Mesh classifications.

Automatic Detector Sync

For on‑premises deployments, detectors automatically sync with the deployed AI Mesh. Any changes to the mesh—including custom or regional deployments—are reflected automatically, eliminating the need for QuickStart import or manual detector updates.

For SaaS deployments, detector behavior remains unchanged. Detectors must continue to be imported using QuickStart import, and automatic synchronization is not yet available. Support for auto sync in SaaS environments will be introduced in a future release.

Detector Enablement Behavior (Unchanged)

In 3.4, the change is limited to how detectors are imported (automatic vs. QuickStart import), not their enabled or disabled state. There is no change in detector enablement behaviour in 3.4 compared to 3.3.

Users can see which detector group nodes each detector contributes to. Additionally, on the AI Mesh page, users can see which detector group nodes contribute to specific classification outcomes (tags).

This improved visibility provides a clearer end‑to‑end view of how detectors influence classification results, making it easier to understand and fine‑tune classification behaviour.

Users can create custom detectors by selecting a Mesh detector group node directly, without requiring access to the Mesh manifest JSON or knowledge of detector group node naming conventions. When a node is selected, the detector name prefix is automatically prefilled, ensuring the detector is correctly associated with that node.

This association allows the detector to contribute to the classification outcomes linked to the selected detector group node, which can be verified on the AI Mesh page. This allows users to easily experiment with various custom detectors without depending on Forcepoint field support teams.

For detailed information, refer to the Detectors section.