Why Symantec is using an older version of JRE within the DLP product.

Products

• Data Loss Prevention

Issue/Introduction

Some customers expect to move to the latest version of the JRE product (N) or (N-1).
The version of JRE that comes with the Symantec DLP installer is older than N or N-1.
Is there any reason why DLP comes with a JRE version that is so out of date?

 

Resolution

DLP release 16.0 ships with OpenJRE 1.8.0_322 by default.
DLP release 16.0.1 ships with OpenJRE 1.8.0_352 by default.
DLP release 16.0.2 ships with OpenJRE 1.8.0_402 by default.
DLP release 16.1 ships with OpenJRE 1.8.0_422 by default.
DLP release 25.1 ships with OpenJRE 21.0.4 by default.
DLP release 26.1 ships with OpenJRE 21.0.9 by default.

As long as we are supporting the DLP release in use we will continue to support the JRE version that it was shipped with.
All testing and certification done on each release was only with the JRE version we supplied at the time, we cannot foresee all future JRE vulnerabilities that might appear at a later date. 

You can upgrade the JRE version to the supported OpenJRE if required, for details see How to upgrade JRE (Java Runtime Environment) on DLP Enforce and Detection Servers.

We now use a version of OpenJRE from https://adoptopenjdk.net/, you can find more details in the following guides:

Steps to update the JRE in DLP 16.0

Steps to Update the JRE in DLP 16.0.1

Steps to Update the JRE in DLP 16.0.2

Steps to Update the JRE in DLP 16.1

Steps to update the JRE in DLP 25.1

Steps to update the JRE in DLP 26.1

 

Additional Information