The software encryption uses various algorithms with different key lengths. All algorithms meet the U.S. National Institute of Standards and Technology (NIST) Advanced Encryption standard.
RijnDael, by virtue of it being the Advanced Encryption Standard (AES), would be considered the most secure encryption algorithm. However, AES was selected based on a series of requirements of which security level was just one. All candidates for AES met or exceeded the security requirement. Serpent and Twofish ciphers were also AES candidates. Twofish is faster and Serpent is considered more secure.
The following table lists the supported algorithms and their key lengths:
|
Cipher |
Details |
Block Size |
Performance Rating* |
Key Length Options |
|---|---|---|---|---|
|
Blowfish |
|
64 bits |
10 |
128, 256 bits |
|
GOST |
|
64 bits |
8 |
256 bits |
|
AES (Advanced Encryption Standard) or Rijndael |
|
128 bits |
7 |
128, 256 bits |
|
Twofish |
|
128 bits |
5 |
128, 256 bits |
|
Serpent |
|
128 bits |
4 |
128, 256 bits |
|
3-DES (Triple Data Encryption Standard) |
|
64 bits |
1.5 |
192 bits |
* This performance rating is based on performance tests for the number of megabytes that is encrypted per second in a Windows environment with the software. The rating is on a scale of 1-10, 10 being the fastest. Results may vary depending on testing environment.
AES-GCM encryption
Starting with Commvault 11.46 CU60, AES-GCM replaces AES-CBC for data-at-rest encryption and supports 128-bit and 256-bit key lengths.
In addition to encrypting data, AES-GCM uses an authentication tag to verify data integrity during decryption. If the integrity check detects data corruption or tampering, the software rejects decryption instead of returning unverified data.
Existing entities configured with AES-CBC remain supported. Data previously encrypted using AES-CBC remains accessible after upgrading to Commvault 11.46 CU60 or later.
Important
When AES-GCM encryption is enabled on a storage pool, all participating data mover MediaAgents and servers must run Innovation Release 11.46 CU60 or later.
If any participating MediaAgent or server runs an earlier version, the affected jobs fail. The job pending reason (JPR) indicates that the MediaAgent or server must be upgraded to Innovation Release 11.46 CU60 or later.