1. Overview
This article provides an overview of the new features and resolved issues in the Fortanix Data Security Manager (DSM) Accelerator 5.4 release.
2. New Features
DSM Accelerator Webservice:
Added support for combined authentication for inbound application (app) connections in Fortanix DSM Accelerator Webservice, requiring both a TLS client certificate and an in-band credential in REST API requests (JIRA: PM-556).
For more information, refer to the DSM Accelerator Webservice Developer Guide.Fortanix DSM Accelerator Webservice now supports batch APIs (
crypto/v1/keys/batch) to perform encryption and decryption operations using key names (JIRA: PM-487).
For more information, refer to the DSM Accelerator Webservice Developer Guide.Fixed the issue where the Mutual Transport Layer Security (mTLS) client in Fortanix DSM Accelerator Webservice ignored the custom CA file specified using the
--ca-file <CA-FILE>command-line option or theCA_FILEenvironment variable during certificate verification (JIRA: ES-559).
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 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 | 20,647/20,595 |
AES 256: GCM Encryption/Decryption | 22,088/21,656 |
AES 256: FPE Encryption/Decryption | 9,427/9,381 |
3.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 | 22,078/21,757 |
AES 256: CFB Encryption/Decryption | 22,124/21,584 |
AES 256: CTR Encryption/Decryption | 22,150/21,592 |
AES 256: OFB Encryption/Decryption | 22,011/21,666 |
AES 256: CCM Encryption/Decryption | 22,154/21,558 |