[5.4] Patch 2 - December 12, 2025

Fortanix Data Security Manager (DSM) 5.4.2899.3349 release provides an overview of general improvements and resolved issues. 

This release is superseded by the February 27, 2026, release.

WARNING

• If you want to upgrade Fortanix DSM to version 5.4.2899.3349, your current DSM version must be at least 5.0 Patch 4.

• Downgrade from 5.4.2899.3349 to any prior version is not supported due to Kernel upgrades.

NOTE

• The Fortanix DSM cluster upgrade must be done with Fortanix Support on call. Please reach out to Fortanix support if you are planning an upgrade.

• The customer's BIOS version must be checked by Fortanix Support before the Fortanix DSM software upgrade. If required, the BIOS version should be upgraded to the latest version and verified by Fortanix Support for a smooth upgrade.

• If your Fortanix DSM version is 5.2 or later, then the HSM Gateway version must also be 5.2 or later. Similarly, if the HSM Gateway version is 5.2 or later, then your Fortanix DSM version must be 5.2 or later.

1.0 Improvements

• This release improves the performance for the FX3400 nodes (JIRA: PROD-8881).

2.0 Bug Fixes

• Fixed an issue where the CANCEL KEY DELETION IN OCI banner for an OCI virtual key continued to appear in Fortanix DSM even after the deletion was canceled in the OCI console and keys were synced in DSM (JIRA: PROD-10856).

• Fixed an issue where intermittent downtime occurred during upgrade from Fortanix DSM version 5.0 to 5.4 in 3-node clusters (DC2+1) with External Load Balancer when Kubernetes (k8s) upgrades ran in parallel on two nodes located in the same data center (JIRA: RODE-345).

• Fixed an issue where during upgrades to Fortanix DSM versions 5.0 or 5.2, users belonging to custom sudo groups (groups other than the system’s default administrator sudo group) could lose sudo access after upgrade (JIRA: ES-573).

• Fixed an issue where the Fortanix DSM dashboard loaded slowly due to inefficient retrieval of compressed audit log account statistics (JIRA: PROD-10884).

3.0 Known Issues

• On VMware nodes, /etc/resolv.conf may be cleared after a reboot, resulting in missing nameserver entries. Although the /etc/network/interfaces configuration is correct, any manual updates to /etc/resolv.conf are overwritten after a reboot or when the CoreDNS pod restarts (JIRA: RODE-373).

  Workaround:

  Perform the following steps:

  1. Run sudo apt purge netplan.io.

  2. If the file is removed or CoreDNS continues to have issues, manually update the nameserver entries in /etc/resolv.conf.

  3. Restart networking: sudo systemctl restart networking.

  4. Delete the CoreDNS pods to allow them to restart.

For a complete list of new features, enhancements to existing features, other improvements, bug fixes, and known issues, refer to the full description of the DSM 5.4 release notes.

4.0. Fortanix Data Security Manager Performance Statistics

NOTE

• Performance testing indicates that the updated kernel introduces performance degradation in AES-related cryptographic operations.

• The Fortanix engineering team is actively investigating this issue and evaluating potential mitigations. At this time, performance benchmark results against Fortanix 4.x releases should not be directly compared to results against 5.x releases.

• The numbers provided below are for 1-node S3 clusters; for multiple nodes, these numbers can be multiplied by the number of nodes added.

4.1 Series 3

4.2 Series 3 JCE