Upgrade Guide
Upgrade Guide
DLP
10.3
Upgrade Guide
Revision A
© 2025 Forcepoint
Forcepoint and the FORCEPOINT logo are trademarks of Forcepoint.
All other trademarks used in this document are the property of their respective owners.
Every effort has been made to ensure the accuracy of this document. However, Forcepoint
makes no warranties with respect to this documentation and disclaims any implied
warranties of merchantability and fitness for a particular purpose. Forcepoint shall not
be liable for any error or for incidental or consequential damages in connection with the
furnishing, performance, or use of this manual or the examples herein. The information in
this documentation is subject to change without notice.
Forcepoint DLP 10.3 | Upgrade Guide
Contents
1 Preparing to Upgrade Forcepoint DLP..............................................................................................................5
Preparing to Upgrade to Forcepoint DLP 10.3..............................................................................................5
Prepare for upgrade.......................................................................................................................................6
Download and launch the installer................................................................................................................ 7
3
Forcepoint DLP 10.3 | Upgrade Guide
4
Chapter 1
Preparing to Upgrade Forcepoint
DLP
Contents
Important
To successfully upgrade DLP to v10.3, log on to the installation machine with the same account who
installed the FSM, which has local administrator privileges.
Note
The FSM system may appear unresponsive until the upgrade process is completed.
Steps
1) Unless instructed otherwise by Forcepoint Technical Support, make sure the system is functional prior to the
upgrade.
3) Perform a full backup of the system (including both product and infrastructure backups, as described in the
appropriate version of the Backup and Restore FAQ).
4) If fingerprinting tasks are running, stop the fingerprinting and disable the scheduler.
5) Ensure that any supplemental fingerprint repositories are fully synchronized with the primary repository.
Check for synchronization in the system log.
6) Log on to the management console to make sure all settings are deployed successfully. (If the Deploy button
is highlighted, click it.)
7) If administrators have removed applications from the product’s predefined endpoint application groups, make
a list of the changes. Application groups are restored after the upgrade, the applications will need to be
removed again. Custom user-defined groups are unaffected.
8) Disable User Account Control (UAC) and Data Execution Prevention (DEP) settings, and make sure that no
Software Restriction Policies will block the installation. The UAC settings can be re-enabled following the
upgrade.
9) Make sure that at least the Visual C++ version 2022 (or later) Runtime Libraries are installed on the
management server. Download the Visual C++ Redistributable for Visual Studio from Microsoft.
Note
The speed and success of the upgrade process are affected by many factors, including:
■ Number of online incidents
■ Size of the forensics folder
■ Number of policies or rules in use
■ User directory import size
■ Whether GPO restrictions are enforced on the server in domain membership scenarios
■ Hardware specification
Steps
1) Navigate to [Link] and log in.
5) Click Forcepoint Security Manager for DLP v10.3 from the Installers list.
6) On the Product Installer page, click the Download link near the bottom of the page.
7) When the installer has downloaded successfully, double-click the file to launch the installer.
It may take several minutes for the installer to unpack files and launch. This is expected behavior.
The installation package detects that earlier versions of the product are installed and automatically starts a
series of wizards.
After upgrade, the system has the same configuration as before the upgrade. The upgrade process does not
allow the option to change configuration or settings.
Start the upgrade process by upgrading the management server. This is critical, because if supplemental servers
or agents are upgraded before the management server, they stop communicating. When the management server is
upgraded first, it continues communicating with the components until they are upgraded.
1) Perform the management server upgrade steps in the order described in the following sections:
a) Upgrade the management infrastructure.
2) Post upgrade of the management server, upgrade supplemental servers and any other server components as
described in following sections:
■ Upgrade supplemental servers and Windows-based agents.
■ Upgrade protectors
■ Upgrade the Forcepoint DLP Protector software.
3) After upgrading the management server and other server components, it is essential to deploy changes. See
section Deploy settings.
4) If you have a DLP Cloud Applications license and are not already connected to Data Protection Service, see
section Data Protection Service before upgrading.
5) If you are using Dynamic Data Protection (Endpoint DLP and Forcepoint Behavioral Analytics), you need to
download the RAP User Manager tool to enable users for Dynamic Data Protection on a DLP system. See the
Forcepoint Dynamic Data Protection Getting Started Guide for more information.
Related concepts
Upgrade the management infrastructure on page 10
Upgrade data security components on the management server on page 11
Related tasks
Complete post-upgrade steps on the management server on page 13
Upgrade supplemental servers and Windows-based agents on page 13
Upgrade the Appliance based Protector on page 15
Upgrade the Forcepoint DLP Protector software on page 15
2) Click Next.
Deploy settings
After upgrading all servers, agents, and appliances to Forcepoint DLP 10.3, deploy changes in the Forcepoint
Security Manager. Endpoints do not require a separate deploy step.
1) Log into the Data Security module of the Forcepoint Security Manager.
3) Click Deploy.
Steps
1) Log on to the management server machine with Administrator permissions.
2) To re-register all other components to the management server, run the appropriate installer on each host
machine (see section Upgrade supplemental servers and Windows-based agents).
4) If applications were removed from the predefined endpoint application groups prior to the upgrade, go to the
Main > >Resources > Endpoint Application Groups page and remove them again.
Related tasks
Upgrade supplemental servers and Windows-based agents on page 13
Steps
1) Launch the Forcepoint Security Installer, Forcepoint Infrastructure. The software is detected, and the
upgrade wizard appears.
3) Complete the upgrade process by deploying changes in the Forcepoint Security Manager. As a best practice,
finish upgrading all components, then log into the Forcepoint Security Manager and deploy all of the changes
at once.
Note
Wait until the upgrade process is completed. It takes time for downloading the information
necessary for resolving source and destination resources such as people, computers, and
printers. Routing traffic through the system before completing the upgrade process may cause
Potential false positives and File-system discovery problems, where the discovery starts but
immediately fails.
Upgrade protectors
There are two types of Protectors:
■ Appliance-based Protector
■ Forcepoint DLP Protector software
Protectors can be upgraded from v8.9.x and later.
Steps
1) Navigate to [Link] and log in.
5) Click Forcepoint DLP Appliance Upgrade Script from 8.9.x or 9.0.0 or 10.0.0, 10.1.0, or 10.2.0 to 10.3.0
from the Installers list.
6) On the Product Installer page, click the Download link near the bottom of the page.
8) Copy the resulting file, protector-update-103-yyyy, to the directory /tmp directory. Here, yyyy is the latest
build number, such as 103-3456.
Steps
1) Enter the following command:
chmod +x /tmp/protector-update-103-yyyy
3) Answer Y on the “Are you sure?” question, and complete the wizard, accepting the defaults.
5) Deploy changes to complete the upgrade process. See section Deploy settings.
Note
Wait until the upgrade process is completed. It takes time to download the information
necessary for resolving source and destination resources such as people, computers, and
printers. Routing traffic through the system before completing the upgrade process may result in
false positives.
Related concepts
Deploy settings on page 12
Steps
1) Navigate to [Link] and log in.
a) Click Downloads in the menu bar at the top of the page.
d) Select Forcepoint DLP Network appliance software package (Protector) in the list of installers.
e) On the Product Installer page, click the Download link near the bottom of the page.
2) Log in to the installation machine as root and copy the installation file into the Protector’s /tmp directory.
4) Execute ForcepointDLP103ApplianceSoftwarePackage
Pre-migration requirements
Before migrating the Protector from CentOS7 to RHEL8, complete the pre-migration requirements in this section.
Steps
1) Stop all traffic from the customer side to the Protector.
4) Replace the IP Address and the hostname of the RHEL8 machine with the IP Address and the hostname of
the Protector with CentOS7.
6) Before installing the Protector, follow the Pre-installation requirements mentioned in Forcepoint DLP
Installation guide.
Post-migration steps
After migrating the protector, perform the following steps.
Steps
1) Keep the replaced CentOS7 machine turned off or delete it.
Note
This section is only applicable to the Linux system.
Steps
1) Go to %DSS_HOME%\policies_store\policies\config_files\
3) If the following snippet is present in the [Link] file, then delete the snippet from the file.
<fileType id="291">
<!-- XML_FMT -->
<textExtractors>
</textExtractors>
<binaryExtractors>
<name>XML</name>
</binaryExtractors>
<metadataExtractors/>
</fileType>
6) Make a ‘fake deploy’ by changing the severity of one of the rules and click No on the Deployment Needed
screen.
7) Then select the original severity of this rule and click Yes on the Deployment Needed screen to deploy the
changes.
To get the updated content related to the enabled Rules/Policies after upgrading, the Policies/Rules need to re-
added.
There are 2 ways to add the updated Policies/Rules:
■ Removing the existing Policies/Rules and re-adding it to FSM (Forcepoint Security Manager).
■ Adding the Policy/Rule again.
In order to avoid Policy/Rule override, the re-added and updated Policy/Rule will appear in the FSM with the
addition of its version, e.g. "<Policy Name>_1"
If you are not yet connected to the Data Protection Service, you must connect using a Data Protection Service
JSON configuration file. Request this file from Forcepoint Technical Support before upgrading to Forcepoint DLP
10.3.
To support cloud channels, DLP Cloud Applications must be activated. For more information, see Forcepoint DLP
Administrator Help.
Steps
1) Click Select File, and in the dialog box that appears, click Choose File. Browse to the JSON file you
received from Forcepoint, and then click OK.
The file is uploaded to the server, and the information begins to appear in the Connection area of the Data
Protection Service tab.
2) Click Connect to establish the connection with the Data Protection Service:
b) Check the incident report to make sure incidents are analyzed by Data Protection Service and not any
other system component.
Note
As part of the integration with the Forcepoint Web Security Cloud, URL categories can now be
imported from the Forcepoint Web Security Cloud Portal. See Forcepoint DLP Administrator
Help for more information.
Error handling
■ If Data Protection Service shows the status “Failed to connect”, the module is temporarily unavailable. Click
Connect or Recheck Connection to try to connect again. If the problem continues, contact Forcepoint
Technical Support.
■ If the JSON file is uploaded for the first time, and when you click Connect, the connection fails, the status
shown is “Never connected”. This is because the Forcepoint Security Manager has never successfully
connected to the Data Protection Service. Contact Forcepoint Technical Support for assistance.
■ If you receive the following message in the Data Protection Service Status area:
This service is not connected to Forcepoint CASB. Incident reporting and policy enforcement will be affected for
cloud channels. See “Explain this page” for more information.
This means that there is a connection issue, and DLP Cloud API and Cloud Data Discovery channels will not
enforce DLP policies, and the DLP Cloud Proxy channel might not report incidents to the Forcepoint Security
Manager. See Forcepoint DLP Administrator Help, “Error handling” section for more information.
Steps
1) To analyze structured data: Run a full scan (manually or by scheduler).
2) To analyze unstructured data, you must recreate the fingerprinting database (FPNE files) as follows:
a) Go to the DLP installation folder %DSS_HOME%
For details on specific maintenance releases, refer to the corresponding release notes in the table.