What's new in Agent 5.4.0
Posted on Oct 07, 2026
Forcepoint Data Classification (FDC) 5.4.0 introduces Multi-Config, enabling administrators to maintain multiple named configuration profiles, rather than a single fleet-wide setup, and assign individual endpoints to the profile they need without losing central control or disconnecting those machines from the cluster. Alongside this headline capability, version 5.4.0 delivers a broad set of stability and reliability improvements across Outlook (Classic, New Outlook, and Outlook Web App), mail merge, Microsoft Purview Information Protection (MIP) label handling, and the Dashboard. It resolves both internally identified issues and active customer escalations.
To know more on bug fixes, click here.
New Features and Enhancements
Multi-Config
Multi-Config gives administrators the ability to run multiple configuration profiles across a fleet instead of forcing every endpoint to look and behave identically. This is useful when a subsidiary requires its own branding, a regional office needs messages in a different language, or a specific team requires different rules.
- Named Configurations (Dashboard): Administrators can create, rename, and delete configuration profiles from a single page. One profile is always designated as the Default profile, which is used by any endpoint that does not have an override and cannot be deleted. Any profile can be downloaded as a single file that is ready for deployment to an endpoint. The Dashboard also shows which profile is active on each computer and when it was last changed.
- Override File (config.txt): A single file placed on an endpoint that directs it to use a named profile instead of the Default profile. The file contains only a configuration ID; the cluster remains the source of truth for the actual configuration content. As a result, the endpoint remains synchronized with the selected profile, automatically reverts to the Default profile if the file is missing, invalid, or references an unknown profile, and continues operating offline by using its last known configuration until it reconnects.
For additional details, refer to FDC - Multi-Configuration Details
To watch the demo video, click here
Direct Forcepoint ONE (DSC) IdP integration for DSPM SaaS
DSPMSaaS now authenticates users directly through the Forcepoint ONE (DSC) Identity Provider, removing the previous dependency on Keycloak-based SSO. This is required for running FDC with DSPMSaaS.
For additional details, refer to Onboarding a New Multi-Tenant (MT) Tenant: Agent Credentials and Installer Configuration