Trellix Data Exchange Layer 6.0.3 addresses known issues, security updates and rebranding changes.
Release details of Trellix Data Exchange Layer 6.0.3
For release dates and build numbers, see Product Release Information in Supported Platforms for Data Exchange Layer Broker (KB90421).
Rating
The rating defines the urgency for installing this update.
This release is recommended for all environments. Apply this update at the earliest convenience.
Product Compatibility
System support
This release supports:
Trellix ePolicy Orchestrator - On-premises — 5.10.0
Trellix Agent Extension — 5.7.8
Trellix Agent — 5.7.8
For complete list of supported operating system and hyper visor see supported platforms for Data Exchange Layer Broker (KB90421).
Upgrade support
You can install this release as a fresh installation or upgrade to it from Trellix Data Exchange Layer version 5.x.x and 6.0.0
Important
This release does not support in-place upgrade using Trellix ePO - On-prem Product deployment for Trellix DXL Broker appliance server version 5.x.x / 6.0.0 to 6.0.3 deployed using DXL Broker Server ISO or OVA and TIE Server ISO or OVA. In this case, you can only upgrade the Trellix DXL Broker Server by setting up a new Trellix DXL Broker server on your choice of supported platform or TIE Server 4.0.0.
However, support for in-place upgrade using Trellix ePO - On-prem Product deployment is provided for Trellix DXL Broker server version 5.x.x /6.0.0 to 6.0.3 installed on Microsoft Windows Server, CentOS, and Red Hat.
For more information, see KB96242 and Trellix Data Exchange Layer Installation Guide.
New or changed
This release provides support for these features.
Rebranding changes- As part of rebranding, you will notice the following changes in the software:
Software Catalog in Trellix ePO - On-prem now displays Trellix Data Exchange Layer.
Brand logo is updated with Trellix logo.
User interface - Color and typeface are updated to provide better user experience.
End User License Agreement and Copyright - The End User License Agreement and Copyright are updated as per legal requirements. Read the agreement for details.
The certificates used to sign our software have been updated. If your enterprise automatically updates root certificates, the software update/installation does not require any additional effort. However, if your enterprise manages root certificate updates manually, you need to install the new intermediate and root certificates. For more information, see KB95499 - REGISTERED - Trellix Solutions Rebranding.
DXL 6.0.3 Appliance (ISO and OVA) ships with MLOS version 3.
DXL 6.0.3 ships with Java version 1.8.0_351.
Upgraded third-party libraries to enhance the security.
Removed features
This release removes support for these features.
This release removes support for operating system MLOS version 2 — This release does not support Trellix DXL Broker server installed on MLOS version 2.
Note
The Trellix DXL broker server 5.x.x and 6.0.0 on MLOS version 2 cannot be upgraded to Trellix DXL Broker server 6.0.3 as it is based on MLOS version 3. see KB96242.
Resolved issues
This release resolves known issues.
Reference | Resolution |
|---|---|
DXLM-4495 | On the Trellix DXL Broker appliance, |
DXLM-7201 | Previously, switching Trellix ePO - SaaS customer account on MVISION Cloud Bridge does not update IAM credentials in Trellix DXL Broker server. This resulted in Trellix DXL Broker server failing to send Trellix EDR traces to new account. This issue is resolved as part of this release. |
DXLM-7040 | When a user visits the Trellix TIE topology page for Trellix DXL connection health check, the Audit log in Trellix ePO - On-prem makes the following incorrect entry: This issue is resolved as part of this release. |
DXLM-7038 | The Audit log in Trellix ePO - On-prem makes the following entry when MVISION Cloud Bridge fails to link IAM account: This issue is resolved as part of this release. |
DXLM-7237 | The filename of IPE logs of DXL 6.0.0 HF5 does not update in chronological order. This issue is resolved as part of this release. |
Known issues
For a list of known issues in this product release, see KB92077.