1. Overview
This document provides an overview of the bug fixes for the Fortanix Data Security Manager (DSM) Accelerator 4.35 release.
2. Bug Fixes
DSM Accelerator Webservice:
Fixed an issue where the DSM Accelerator Webservice could not perform masked detokenization with the application (app) configured with the "Masked Decrypt" permission (JIRA: ES-439).
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, 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 | 21,015/20,724 |
AES 256: GCM Encryption/Decryption | 21,620/21,557 |
AES 256: FPE Encryption/Decryption | 9,447/9,342 |
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 and Decryption | 21,340/21,140 |
AES 256: CFB Encryption/Decryption | 21,423/21,557 |
AES 256: CTR Encryption/Decryption | 21,860/21,544 |
AES 256: OFB Encryption/Decryption | 21,964/21,604 |
AES 256: CCM Encryption/Decryption | 21,476/21,197 |