1. Overview
This article provides an overview of the resolved issues in the Fortanix Data Security Manager (DSM) Accelerator 4.29 release.
2. Bug Fixes
DSM Accelerator Webservice
Fixed an issue where keys cached in Fortanix DSM Accelerator Webservice for one application (app) could be accessible by another app within the same account (JIRA: PROD-8386).
3. Fortanix Data Security Manager Accelerator Performance Statistics
3.1 Runtime Environment
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 |
|
3.2 DSM Accelerator Webservice
NOTE
The performance numbers below are captured with a single node; if you need higher performance or throughput, then we recommend adding multiple nodes.
Key Types and Operations | Throughput (Operations/second on a 1-node cluster) |
|---|---|
AES 256: CBC Encryption/Decryption | 17,223/17,695 |
AES 256: GCM Encryption/Decryption | 17,159/17,497 |
AES 256: FPE Encryption/Decryption | 5,551/5,574 |
3.3 Additional Modes
Key Types and Operations | Throughput (Operations/second on a 1-node cluster) |
|---|---|
AES 256: CBCNOPAD Encryption/Decryption | 17,577/17,854 |
AES 256: CFB Encryption/Decryption | 17,624/17,973 |
AES 256: CTR Encryption/Decryption | 17,656/18,015 |
AES 256: OFB Encryption/Decryption | 17,712/18,030 |
AES 256: CCM Encryption/Decryption | 17,100/17,618 |