[5.6] DSM Patch 3 - August 11, 2026

Fortanix Data Security Manager (DSM) 5.6.2930.3502 release provides an overview of resolved issues.

WARNING

• If you want to upgrade Fortanix DSM to version 5.6.2930.3577, your current DSM version must be at least 5.2 Patch 2*.

• Downgrade from 5.6.2930.3577 to any prior version is not supported due to Kubernetes upgrade.

• Upgrading Fortanix DSM to version 5.6.2930.3577 includes an underlying Kubernetes upgrade to version 1.34. As a result, the upgrade process may take longer than usual.

• The fixes included in this patch release may cause a performance degradation and increased operation latency when executing requests from client applications. The impact will vary across operations and cryptographic algorithms.

*The minimum required version is specific to your current major.minor version. You must first upgrade to the required patch level within your current version before proceeding to version 5.6.2930.3577.

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.4 or later, then the HSM Gateway version must also be 5.4 or later. Similarly, if the HSM Gateway version is 5.4 or later, then your Fortanix DSM version must be 5.4 or later.

1. Quality Enhancements

• Updated the BIOS for the Fortanix FX3400 appliances to include the latest Intel microcode and associated firmware updates required for IPU 2026.3 compatibility (JIRA: RODE-473).

• Updated the BIOS to version 11.13.FP01 for Fortanix FX3400 appliances, resolving an issue where installed memory Dual In-line Memory Module (DIMMs) could be incorrectly detected (JIRA: RODE-474).

2. Known Issues

• If a Fortanix DSM software download initiated through a URL (UI or API) is interrupted (for example, due to a page refresh or network issue), retrying the download may fail with:
  Another download is still in progress (HTTP 409).
  The previous attempt may continue to be treated as active, and the state is not cleared automatically (JIRA: PROD-11136).

  Workaround:
  Use alternative methods such as uploading the build from a local file through the DSM UI, using CLI upload, or downloading the build directly on the cluster node (for example, with wget).

• 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.6 release notes.