Trellix File and Removable Media Protection (FRP) 5.7.0 on-premises is now available.
This release introduces key enhancements to removable media administration by enabling multi-language media messages within a single policy and providing write access to BitLocker To Go encrypted media. Additionally, it strengthens cryptographic compliance with FIPS 140-3 and delivers ongoing quality and reliability improvements.
This release includes new features, enhancements, and resolved issues.
-
Key features and enhancements
-
Transition to FIPS 140-3 compliance: FRP updates its cryptographic framework to FIPS 140-3, enabling customers to seamlessly maintain compliance and streamline secure deployments. This update ensures validated cryptography after FIPS 140-2 certificate expirations. For FIPS mode installation details, refer to the FRP 5.7.x Installation Guide.
-
Write access for BitLocker To Go encrypted media: When offsite encryption enforcement is active, a new option grants write access to BitLocker To Go encrypted removable media. This reduces warning pop-ups and access restrictions for these devices.
-
Localized removable media messages within a single policy: Administrators can now configure media insertion and recovery messages in multiple languages within a single Removable Media policy. This removes the need for duplicate policies and simplifies policy assignment across global environments.
-
Transition to FIPS 140-3 compliance: FRP updates its cryptographic framework to FIPS 140-3, enabling customers to seamlessly maintain compliance and streamline secure deployments. This update ensures validated cryptography after FIPS 140-2 certificate expirations. For FIPS mode installation details, refer to the FRP 5.7.x Installation Guide.
- Resolved issues: For details of the issues fixed in this release, see the Release Notes.
Upgrade impact and considerations
- System reboot: Endpoints require a system restart to activate the updated driver.
- Service restarts: The Trellix Agent service restarts automatically during installation.
- ePolicy Orchestrator (ePO) connectivity: Trellix ePO connectivity might be interrupted briefly during the service restart.
- Service name change: The endpoint service name has changed. Update any dependent custom scripts or integrations accordingly.
See the following documentation for additional information and detailed instructions.