--- title: "[5.11] DSM - November 16, 2026" slug: "5-11-dsm-november-16-2026" updated: 2026-11-18T11:57:35Z published: 2026-11-18T11:57:35Z canonical: "support.fortanix.com/5-11-dsm-november-16-2026" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fortanix.com/llms.txt > Use this file to discover all available pages before exploring further. # [5.11] DSM - November 16, 2026 Fortanix Data Security Manager (DSM) 5.11 comes with some exciting new features, enhancements, general improvements, and resolved issues. > [!WARNING] > WARNING > > - If you want to upgrade Fortanix DSM to version 5.11, your current DSM version must be at 5.9* or 5.8*. > - Downgrade from 5.11 to any prior version is not supported due to Kubernetes and Kernel upgrades. > > *******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.11.** > [!NOTE] > 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.9 or later, then the HSM Gateway version must also be 5.9 or later. Similarly, if the HSM Gateway version is 5.9 or later, then your Fortanix DSM version must be 5.9 or later. ## 1. New Features - **Added auto-generated CycloneDX-formatted Software Bill of Materials (SBOM)**: Fortanix DSM now provides information about software components, licenses, and known vulnerabilities to help customers assess and manage software supply chain risk **(JIRA: EXTREQ-1679)**. - Added support to configure two additional options in the Fortanix DSM account-level **Quorum approval policy** for user and administrative application (app) management operations **(JIRA: EXTREQ-1365)**. *For more information, refer to* [*Account Quorum Policy*](/v1/docs/fortanix-dsm-account-quorum-policy)*.* - **Manage users**: Inviting users, enabling or disabling users, deleting users, updating group membership, and changing user roles, including assigning custom roles. - **Manage admin apps**: Creating, updating, or deleting administrative apps, including changes to their enabled state, credentials, custom roles, and group membership. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(202).png?sv=2026-02-06&spr=https&st=2026-11-19T02%3A51%3A31Z&se=2026-11-19T03%3A51%3A31Z&sr=b&sp=r&sig=Am9miEnYFzVPQjuUrhiArxNJDiMbt2LrFXxm3nxCgRA%3D) - Added support for generating and importing **SLH-DSA** (Stateless Hash-Based Digital Signature Algorithm) keys under the **Post Quantum Cryptography** section of the **Security Objects** page in the Fortanix DSM UI. This key type includes all 12 parameter sets combining SHA-2 and SHAKE256, security levels of 128, 192, and 256 bits, and fast (f) and small (s) variants **(JIRA: EXTREQ-1569)**. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(203).png?sv=2026-02-06&spr=https&st=2026-11-19T02%3A51%3A31Z&se=2026-11-19T03%3A51%3A31Z&sr=b&sp=r&sig=kEF68PmjLLdZAdCtfIPtsqpY5apG3vAq7Kh9xmYWMS8%3D) ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(204).png?sv=2026-02-06&spr=https&st=2026-11-19T02%3A51%3A31Z&se=2026-11-19T03%3A51%3A31Z&sr=b&sp=r&sig=AzzCNW0cwsce%2BDM72dft03wVt6c8%2BKRQVZ%2FUTlCcVUk%3D) *For more information, refer to* [*Key Lifecycle Management*](/v1/docs/fortanix-data-security-manager-key-lifecycle-management)*.* ## 2. Enhancements - Added support importing and validating X.509 certificates signed using ML-DSA (Module-Lattice-Based Digital Signature Algorithm). The certificate details are now displayed correctly in the DSM user interface (UI) and APIs **(JIRA: EXTREQ-1751)**. - Updated the label from “**Azure Log Ingestion**” to “**Azure Logs Ingestion**” under DSM **Settings** → **Log Management** **(JIRA: ROFR-6109)**. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(205).png?sv=2026-02-06&spr=https&st=2026-11-19T02%3A51%3A31Z&se=2026-11-19T03%3A51%3A31Z&sr=b&sp=r&sig=Qcmwphzs13bgV9FEe%2BiizmMPX8CbhL645dpqO7ikMmY%3D) - Improved error handling for account creation requests involving LDAP users in Fortanix DSM **System Administration** → **Tasks** page. The UI now displays an appropriate error message when account creation fails because the user does not have a password, clarifying why the operation cannot proceed **(JIRA: ROFR-6173)**. ![](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/image(206).png?sv=2026-02-06&spr=https&st=2026-11-19T02%3A51%3A31Z&se=2026-11-19T03%3A51%3A31Z&sr=b&sp=r&sig=gmCOmkUcFbp74hDw80tlMVxP0qFtUIizCyW4aO15lwE%3D) - Improved validation on the Fortanix DSM **System Administration** → **Settings** → **Email** page to prevent saving an empty or incorrectly formatted value in the **“From” for outgoing emails** field **(JIRA: EXTREQ-1375)**. - DSM now supports setting an expiration date on the transient Key Encryption Key (KEK) created in Azure Managed HSM during the Bring Your Own Key (BYOK) workflow. This allows the KEK creation to comply with Azure policies that require keys to have an expiration date, enabling BYOK operations in environments where such policies are enforced **(JIRA: EXTREQ-1766)**. ## 3. API Updates - Added support for configuring a Quorum approval policy for user and administrative app management at the DSM account level, allowing account administrators to require quorum approval for user management and administrative app operations **(JIRA: EXTREQ-1365)**. This enhancement affects the following APIs: - `PATCH /sys/v1/accounts/{acct_id}`: Update Account - `GET /sys/v1/accounts/{acct_id}`: Retrieve Account - `GET /sys/v1/approval_requests/{req_id}`: Retrieve Approval Request - `GET /sys/v1/approval_requests`: List Approval Requests - Added support for the SLH-DSA key type and its standardized parameter sets through the key generation API. Extended the existing Sign and Verify APIs to support Pure SLH-DSA and Pre-hash SLH-DSA signature modes **(JIRA: EXTREQ-1569)**. This enhancement affects the following APIs: - `POST /crypto/v1/keys`: Generate an SLH-DSA key by specifying the `SlhDsa` object type and the `slhdsa.param_set` parameter. - `POST /crypto/v1/keys/sign`: Generate Pure or Pre-hash SLH-DSA signatures using the `mode` parameter. - `POST /crypto/v1/keys/verify`: Verify Pure or Pre-hash SLH-DSA signatures using the corresponding signature mode. - Added support for using Integration Credentials to manage TLS client certificates and private keys in DSM TLS configurations. This enhancement allows TLS configurations to reference Integration Credential objects instead of specifying client certificates and private keys inline **(JIRA: PM-748)**. The following APIs are affected: - `POST /sys/v1/credentials`: Create an Integration Credential for a TLS client key pair. - `PATCH /sys/v1/credentials/{cred_id}`: Update an Integration Credential with TLS client key pair details. - `PATCH /sys/v1/credentials/{cred_id}/rotate`: TLS credential rotation is not supported through this endpoint; update the underlying key and certificate objects and patch the Integration Credential instead. ## 4. Other Improvements - Fortanix DSM now automatically selects the appropriate enclave build based on the underlying hardware platform to optimize cryptographic performance while maintaining the required security protections. Supported platforms include Series 2 appliances, Series 3 appliances, and Azure Confidential VMs (supported DC* variants) **(JIRA: PM-709)**. *For more information, refer to* [*Fortanix DSM Installation Guide*](/v1/docs/fortanix-data-security-manager-installation-guide-on-prem#442-verify-the-selected-enclave-build)*.* - Added support for centralized FSE policy management, allowing multiple FSE encrypted directories across hosts to use shared and centrally managed policies through Fortanix DSM **(JIRA: FSE-718)**. - Implemented minor UI styling and alignment improvements across Fortanix DSM to enhance visual consistency and usability **(JIRA: ROFR-5415)**. ## 5. Integrations and Use Cases - Added support for signing Microsoft Visual Basic for Applications (VBA) projects using the Fortanix CNG Provider in Fortanix DSM **(JIRA: PM-729)**. *For more information, refer to* [*Fortanix DSM with Signing Microsoft Visual Basic for Applications (VBA) Projects*](/v1/docs/fortanix-dsm-with-signing-microsoft-visual-basic-for-applications-vba-projects)*.* - Added support for integrating Fortanix DSM with NetApp ONTAP using NetApp Aggregate Encryption (NAE) to centrally manage aggregate encryption keys over the Key Management Interoperability Protocol (KMIP) **(JIRA: PM-796)**. *For more information, refer to* [*Fortanix DSM with NetApp ONTAP Using NAE*](/v1/docs/fortanix-dsm-with-netapp-ontap-using-nae)*.* ## 6. Client New Features, Improvements, and Bug Fixes - Upgraded KMIP to version 3.0 to support ML-DSA key pair generation, signing, and verification (JIRA: PM-741). - Updated `CKA_PARAMETER_SET` error handling in PKCS#11 to maintain compatibility with OpenSSL during EC key generation **(JIRA: PROD-11791)**. - Fixed HMG Client binary permissions to ensure it has the required executable permission **(JIRA: PROD-11757)**. - Added support for retrieving certificate objects in **X.509** or **Raw** formats through the KMIP **GET** operation **(JIRA: PM-777)**. - Added Ed448 EC Edwards curve support in PKCS#11 for key pair generation, signature generation, and signature verification **(JIRA: PM-759)**. - Added support for the KMIP Extractable attribute to control key extraction permissions **(JIRA: PM-737)**. - Added support for **ML-DSA** key pair generation, signing, signature verification, and key factory operations in the Fortanix JCE provider **(JIRA: PM-633** and **PM-775)**. *For more information, refer to* [*Java Cryptography Extension (JCE) Provider*](/v1/docs/fortanix-dsm-clients-java-cryptography-extension-jce-provider#1318-generate-dsa-keys)*.* - Fixed an issue where sdkms-cli authentication using the `--username` argument failed in DSM 5.10 when using username and password authentication **(JIRA: ES-676)**. ## 7. DSM Accelerator Improvements - Added ML-DSA support in DSM Accelerator Webservice to enable quantum-safe application integration for signature generation and signature verification that aligns with DSM post-quantum cryptography support for exportable keys **(JIRA: PM-705)**. *For more information, refer to* [*DSM Accelerator Webservice Developer Guide*](/v1/docs/dsm-accelerator-webservice-developer-guide#822-signing-and-verification-using-mldsa-keys)*.* ## 8. Quality Enhancements - The third-party software upgrade list can be found [*here*](/v1/docs/list-of-third-party-software-installed-5-11). - Upgraded Kubernetes to version 1.36.2 **(JIRA: RODE-544)**. *For more information, refer to* [*Fortanix Data Security Manager (Release 5.11) Kubernetes Version Upgrade to 1.36 K8s*](/v1/docs/release-5-11-kubernetes-version-upgrade-to-1-36-k8s)*.* - Upgraded Kernel to Linux version 6.8.0-147 **(JIRA: RODE-666)**. ## 9. Security Fixes - Updated the CA certificates package and the certificates bundled in the SGX binary to address the eMudhra intermediate CA certificate compromise **(JIRA: SI-129)**. *For more information, refer to the* [*eMudhra Intermediate CA Compromise advisory*](https://emudhra.we-have-a-problem.com/)*.* - Updated the MbedTLS build configuration to mitigate CVE-2025-66442 by disabling the select-optimize compiler feature when required **(JIRA: PROD-11723)**. - Fixed an issue in DSM sysadmin provisioning that could allow unauthorized sysadmin account creation when database write access and access to the sysadmin API were available **(JIRA: PM-713)**. - Updated the Linux kernel used in DSM and DSM Accelerator Nitro enclaves to 6.6.161 to address [CVE-2026-98432](https://nvd.nist.gov/vuln/detail/cve-2026-98432), a use-after-free vulnerability in the IPv4 TCP networking subsystem that could potentially lead to denial of service (DoS) or remote code execution **(JIRA: SI-131)**. - Updated the DSM Accelerator base images to set the APT `Acquire::Retries` configuration to `0`, addressing CVE-2026-109518 **(JIRA: SI-133)**. ## 10. Known Issues - When synchronizing keys from a non-FIPS-backed group in DSM, the UI may fail to load the Groups, Apps, and Security Objects pages if the source group/ cluster contains an ML-DSA key **(JIRA: ROFR-6196)**. - 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. - When users edit a quorum approval policy configured with multiple reviewers, DSM may display the **Using second factor security key is required to approve requests** check box as unchecked in the **Quorum approval policy** screen, even though multi-factor authentication (MFA) enforcement continues to work as expected **(JIRA: PROD-11444)**. - A Fortanix DSM account, whether normal or system administrator, with the "No Roles Can Login with Password" role selected, may experience issues when attempting to log in using a password. If the users select such an account and enter the SSO credentials, they will be logged out instead of accessing the account **(JIRA: ROFR-4998)**. **Workaround**: The users should log in directly with SSO after the "No Roles Can Login with Password" role is set to access the account. - The **COPY KEY** dialog box does not filter the HSM/External KMS groups as expected when Import key to HSM/External KMS check box is selected, if there are more than 1,000 groups in the account **(JIRA: ROFR-5167)**. - Unable to delete a user who was invited to an account with a "Custom account role" that includes an "All Groups Role" along with group membership assigned explicitly in the invite user workflow if the invited user has not accepted the invitation **(JIRA: PROD-9409)**. **Workaround**: To delete the invited user, contact Fortanix Support or perform the following steps: - If you have already assigned explicit group memberships, perform the following steps to remove them and delete the user: - Change the user's account role to "Account Member". - Remove the group memberships one by one using the user interface. - Delete the user. - The `sudo get_csrs --rotate` workflow does not support changing existing DNS hostnames configured in the service URL or Subject Alternative Name (SAN) entries **(JIRA: PROD-9542)**. This issue occurs when: For example, if the existing service URL hostname is `dsm.fortanix.net`, changing it to a different hostname while using certificate rotation is not supported. **Workaround**: - `get_csrs --rotate` is used to generate CSRs, and - `install_certs --rotate` is used to install certificates where existing DNS/SAN hostnames (single or multiple) are modified or replaced. - Do not use the `--rotate` option when changing existing DNS/SAN hostnames. - If certificate rotation is required with SAN certificates, retain the existing DNS entries and append additional DNS entries instead of replacing or modifying the current ones. - When you run `sudo get_csrs --rotate` command to create a new certificate pair for cluster and UI, it does not remove the old certificate pair from the sdkms pod, resulting in two certificate pairs which can lead to unexpected results **(JIRA: RODE-97)**. - Deleting replica keys in groups with Key undo policies is reversible using the undo operation **(JIRA: PROD-9925)**. **Workaround**: Users should avoid deleting keys that are associated with a key-undo policy. - Unable to perform Kubernetes CA rotation successfully **(JIRA: RODE-62)**. **Workaround**: To perform CA rotation in DSM 5.2 and higher, contact the Fortanix Support team. - When Fortanix DSM contains a large number of objects (for example, ~1000 groups, plugins, apps, and users, and ~11,000 security objects), certain UI pages may load slower than usual **(JIRA: PROD-11135)**. **Workaround**: There is currently no direct workaround. As a mitigation, it is recommended to reduce the number of objects displayed using filters or pagination and use APIs for bulk operations instead of UI navigation in large-scale environments. ## 11. Fortanix Data Security Manager Performance Statistics ### 11.1 Series 3 | **Key Types and Operations** | **Throughput (Operations/second on a 1-node cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBC Encryption/Decryption | 14,669/14,722 | | AES 256: GCM Encryption/Decryption | 14,606/14,692 | | AES 256: FPE Encryption/Decryption | 10,436/10,497 | | AES 256 Key Generation | 2,502 | | | | | RSA 2048 Encryption/Decryption | 12,905/2,568 | | RSA 2048 Key Generation | 45 | | RSA 2048 Sign/Verify | 2,515/13,322 | | RSA 4096 Sign/Verify | 545/10,102 | | | | | EC NISTP256 Key Generation | 1,729 | | EC NISTP256 Sign/Verify | 3,915/2,214 | | EC secP256K1 Key Generation | 1,519 | | EC secP256K1 Sign/Verify | 2,874/1,599 | | | | | Kyber ML-KEM Encapsulation | 2,146 | | Kyber ML-KEM Decapsulation | 2,116 | | | | | LMS Key (Height, Node) | | | L1 5, Node 24 | 163.1 | | L1 5, Node 32 | 129.3 | | L1 10, Node 24 | 5.3 | | L1 10, Node 32 | 4.2 | | | | | BIP32 Key Derive as Transient Hardened Child Key | 1,383 | | BIP32 Sign | 1,383 | | | | | ECDSA: EC SecP256K1 Key Generation | 1,532 | | ECDSA Sign | 1,532 | | | | | Data Security Manager Plugin (Hello world plugin) | 6,564 (invocations/second) | --- ### 11.2 Series 3 JCE | **Key Types and Operations** | **Throughput (Operations/second on a 1-node cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBC Encryption/Decryption | 13,378/13,778 | | AES 256 Key Generation | 2,160 | | | | | RSA 2048 Key Generation | 45 | | RSA 2048 Sign/Verify | 2,047/6,964 | | RSA 4096 Sign/Verify | 532/5,979 | | | | | EC NISTP256 Key Generation | 1,616 | | EC NISTP256 Sign/Verify | 2,925/1,900 | | EC secP256K1 Key Generation | 1,454 | | EC secP256K1 Sign/Verify | 2,311/1,429 | | | | | Data Security Manager Plugin (Hello world plugin) | 6,525 (invocations/second) | --- ### 11.3 Series 2 | **Key Types and Operations** | **Throughput (Operations/second on a 3-node cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBC Encryption/Decryption | 6,649/6,721 | | AES 256: GCM Encryption/Decryption | 6,645/6,682 | | AES 256: FPE Encryption/Decryption | 4,945/4,948 | | AES 256 Key Generation | 1,364 | | | | | RSA 2048 Encryption/Decryption | 5,788/981 | | RSA 2048 Key Generation | 23 | | RSA 2048 Sign/Verify | 986/5,832 | | RSA 4096 Sign/Verify | 300/4,852 | | | | | EC NISTP256 Key Generation | 874 | | EC NISTP256 Sign/Verify | 1,572/886 | | EC secP256K1 Key Generation | 789 | | EC secP256K1 Sign/Verify | 1,257/681 | | | | | Kyber ML-KEM Encapsulation | 1,229 | | Kyber ML-KEM Decapsulation | 1,175 | | | | | LMS Key (Height, Node) | | | L1 5, Node 24 | 137.7 | | L1 5, Node 32 | 111.6 | | L1 10, Node 24 | 4.9 | | L1 10, Node 32 | 3.8 | | | | | BIP32 Key Derive as Transient Hardened Child Key | 616 | | BIP32 Sign | 616 | | | | | ECDSA: EC SecP256K1 Key Generation | 688 | | ECDSA Sign | 688 | | | | | Data Security Manager Plugin (Hello world plugin) | 2,681 (invocations/second) | --- ### 11.4 Azure Standard_DC8s_v3 | **Key Types and Operations** | **Throughput (Operations/second on a 3-node [Standard_DC8s_v3] cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBC Encryption/Decryption | 5,395/5,414 | | AES 256: GCM Encryption/Decryption | 5,379/5,399 | | AES 256: FPE Encryption/Decryption | 4,652/4,634 | | AES 256 Key Generation | 1,793 | | | | | RSA 2048 Encryption/Decryption | 5,121/2,191 | | RSA 2048 Key Generation | 66 | | RSA 2048 Sign/Verify | 2,172/5,155 | | RSA 4096 Sign/Verify | 631/4,935 | | | | | EC NISTP256 Key Generation | 1,358 | | EC NISTP256 Sign/Verify | 2,825/1,893 | | EC secP256K1 Key Generation | 1,171 | | EC secP256K1 Sign/Verify | 2,131/1,322 | | | | | Data Security Manager Plugin (Hello world plugin) | 5,009 (invocations/second) | --- ### 11.5 Series 2 JCE | **Key Types and Operations** | **Throughput (Operations/second on a 3-node cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBC Encryption/Decryption | 6,223/5,801 | | AES 256 Key Generation | 1,300 | | | | | RSA 2048 Key Generation | 24 | | RSA 2048 Sign/Verify | 865/3,125 | | RSA 4096 Sign/Verify | 303/2,823 | | | | | EC NISTP256 Key Generation | 842 | | EC NISTP256 Sign/Verify | 1,305/821 | | EC secP256K1 Key Generation | 761 | | EC secP256K1 Sign/Verify | 1,121/672 | | | | | Data Security Manager Plugin (Hello world plugin) | 2,692 (invocations/second) | --- ### 11.6 Azure Standard DC8 JCE | **Key Types and Operations** | **Throughput (Operations/second on a 3-node [Standard_DC8 JCE] cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBC Encryption/Decryption | 5,348/5,341 | | AES 256 Key Generation | 1,707 | | | | | RSA 2048 Key Generation | 66 | | RSA 2048 Sign/Verify | 1,627/2,925 | | RSA 4096 Sign/Verify | 569/2,790 | | | | | EC NISTP256 Key Generation | 1,363 | | EC NISTP256 Sign/Verify | 1,961/1,475 | | EC secP256K1 Key Generation | 1,133 | | EC secP256K1 Sign/Verify | 1,576/1,100 | | | | | Data Security Manager Plugin (Hello world plugin) | 5,045 (invocations/second) | --- ### 11.7 Series 2 KMIP | **Key Types and Operations** | **Throughput (Operations/second on a 3-node cluster using 100 TLS Connections)** | **Response Time (in milliseconds)** | | --- | --- | --- | | KMIP_KeyExport | 7500 | 13.34 | | KMIP_Encrypt | 8475 | 11.8 | | KMIP_Decrypt | 8450 | 11.85 | ## 12. Fortanix Data Security Manager Accelerator Performance Statistics ### 12.1 Runtime Environment > [!NOTE] > NOTE > > The following table lists the standard recommended runtime environment. You can choose a higher configuration for better performance. > > DSM Accelerator was run in the runtime environment listed below for performance testing. | **Item** | **Specification** | | --- | --- | | Number of Cores | 4 | | CPU | Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz | | RAM | 2 GiB | | VM Type | Standard D4ds v4 Azure VM | | Docker Runtime Configuration | `sudo docker run -d --network host --memory=1g --memory-swap=2g --log-driver json-file --log-opt max-size=100m` | --- ### 12.2 DSM Accelerator Webservice > [!NOTE] > NOTE > > The performance numbers below are captured with a single node; if you need higher performance or throughput, then Fortanix recommends adding multiple nodes. | **Key Types and Operations** | **Throughput (Operations/second on a 1-node cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBC Encryption/Decryption | 19,801/19,625 | | AES 256: GCM Encryption/Decryption | 20,099/19,855 | | AES 256: FPE Encryption/Decryption | 9,271/9,241 | --- ### 12.3 Additional Modes | **Key Types and Operations** | **Throughput (Operations/second on a 1-node cluster re-using a single TLS session)** | | --- | --- | | AES 256: CBCNOPAD Encryption/Decryption | 20,051/19,782 | | AES 256: CFB Encryption/Decryption | 20,183/19,717 | | AES 256: CTR Encryption/Decryption | 20,094/19,829 | | AES 256: OFB Encryption/Decryption | 20,197/19,919 | | AES 256: CCM Encryption/Decryption | 20,025/19,714 | ## 13. Installation To install the DSM Runtime Encryption® SGX (on-prem/Azure) and Software (AWS/Azure) packages, click [*here*](/v1/docs/dsm-installation-packages-on-prem). ## Attachments - [DSM_5.11_Release_Note.pdf](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/DSM_5.11_Release_Note.pdf)