Luna HSM Firmware 7.8.4
Luna HSM firmware 7.8.4 was released in December 2023, and is the FIPS-validated firmware version recommended by Thales. It includes bug fixes and improvements.
>Download Luna HSM Firmware 7.8.4 for PCIe HSM
Refer to NIST certificate #4684 for FIPS 140-3 Level 3 certification:
https://csrc.nist.gov/projects/cryptographic-module-validation-program/Certificate/4684
New Features and Enhancements
Luna HSM firmware 7.8.4 includes the following new features and enhancements:
Support for ED448 and Curve448
Crypto agility expands with the addition of support for ed448 and curve448.
Security enhancing crypto changes
To comply with FIPS 140-3 requirements, RSA-based key transport schemes that use only PKCS#1-v1.5 padding are disallowed, notably the mechanism CKM_RSA_PKCS for encrypt/decrypt/wrap/unwrap. Other mechanisms might now prohibit forward operations (new encryption or signing or wrapping,) while continuing to permit others (decrypt/unwrap) to support legacy situations. Refer to the Mechanism pages in the Software Development Kit section of this documentation for specific indications.
Valid Update Paths
You can update the Luna HSM firmware to version 7.8.4 from the following previous versions:
>7.0.1, 7.0.2, 7.0.3, 7.1.0, 7.2.0, 7.3.0, 7.3.3, 7.4.0, 7.4.1, 7.7.0, 7.7.1-20, 7.8.0, 7.8.1, 7.8.2
CAUTION! Do Not Update Directly From Luna HSM Firmware 7.7.2; this update path is not supported.
Advisory Notes
This section highlights important issues you should be aware of before deploying HSM firmware 7.8.4.
Do Not Update Directly From Luna HSM Firmware 7.7.2
Luna HSM Firmware 7.7.2 must not be updated directly to Luna HSM Firmware 7.8.4 or newer, or unexpected problems may occur. If you are updating from Luna HSM Firmware 7.7.2, you must first install
Luna HSM Firmware 7.8.4 or Newer Requires Luna HSM Client 10.7.0 or Newer
Changes in Luna HSM Firmware 7.8.4 and newer require update to
FIPS Changes in Luna HSM Firmware 7.8.4 and Newer
New restrictions have been added to some mechanisms when the HSM is in FIPS mode (HSM policy 12: Allow non-FIPS algorithms set to OFF), to comply with NIST's planned withdrawal of FIPS SP800-67 Rev2 on January 1, 2024.
Mechanisms not permitted to encrypt objects in FIPS mode
The following mechanisms are not permitted to encrypt objects in FIPS mode:
The following encryption mechanisms are no longer available in FIPS mode:
DES3 encryption is blocked in ECIES mechanisms.
HMAC mechanisms are blocked from using a DES3 key for signing.
Mechanisms not permitted to sign objects in FIPS mode
The following mechanisms are not permitted to sign objects in FIPS mode:
CKM_RSA_PKCS not permitted to decrypt/unwrap objects in FIPS mode
CKM_RSA_PKCS is now restricted from performing decrypt/unwrap operations in FIPS mode.
FIPS Changes in Luna HSM Firmware 7.8.0 and Newer
The following mechanism is now restricted from use in FIPS mode:
FIPS Changes in Luna HSM Firmware 7.7.2 and Newer
The following mechanisms have new operation restrictions in FIPS mode:
>CKM_RSA_PKCS: cannot encrypt | Cannot legacy decrypt | Cannot legacy unwrap
>CKM_RSA_PKCS_OAEP: Cannot legacy decrypt | Cannot legacy unwrap
NOTE This page lists FIPS-related changes made since the last FIPS-validated firmware release. For a comprehensive list of changes across all released versions of the Luna HSM firmware, see Changes to FIPS Mode Mechanisms and Operations by Firmware Version. Refer to this section if you are updating from a firmware version that is older than the last FIPS-validated version.
Minimum Password Length is Increased to 8 Characters
Luna HSM Firmware 7.7.2 and newer enforces minimum 8-character passwords and challenge secrets, to comply with FIPS requirements. The previous limit was 7 characters. If you were using a 7-character password prior to upgrading the firmware, that password continues to work. Future password changes will use the new 8-character minimum.
If you have an existing HA group whose member partitions use a 7-character password/challenge secret, you must change all members to use a minimum 8-character password before adding a new member that uses Luna HSM Firmware 7.7.2 or newer.
Partition policy to control the use of DigestKey is added
Partition capability/policy 9: Allow DigestKey is added with Luna HSM Firmware 7.8.0; it controls the possibility of final keys being derived outside of the HSM. The policy defaults to OFF, which is the more secure option. Previously, DigestKey was always allowed, and this new policy provides choice for those who do not need the option, as well as for those who do need it.
NOTE Partition Policy 9 is destructive when switched OFF-to-ON, so have any partition contents backed up before you update HSM firmware. After update from any firmware prior to version 7.8.0, if you require this ability, you can switch the policy ON and then restore your material to the partition and resume using your application.
RSA Keygen Mechanism Remapping on Luna 7.7.1 or Newer Partitions Requires Minimum Luna HSM Client 10.4.0
Luna HSM Firmware 7.7.1 or newer partitions that have been individually set to FIPS mode using the new partition policy 43 require Luna HSM Client 10.4.0 or newer to automatically remap older RSA mechanisms as described in RSA Mechanism Remap for FIPS Compliance.
Special Considerations for Luna HSM Firmware 7.7.0 and Newer
Luna HSM Firmware 7.7.0 introduces new capabilities, features, and other significant changes that affect the operation of the HSM. Due to some of these changes, you must be aware of some special considerations before updating to Luna HSM Firmware 7.7.0 or newer. For more information, refer to Special Considerations for Luna HSM Firmware 7.7.0 and Newer before proceeding with the update.
3DES Usage Counter
For Luna HSM Firmware 7.7.0 and newer, triple-DES keys have a usage counter that limits each key instance to encrypting a maximum of 2^16 8-byte blocks of data when the HSM is in FIPS mode (HSM policy 12: Allow non-FIPS algorithms is set to 0). When the counter runs out for a key instance, that key instance can no longer be used for encryption or wrapping or deriving or signing, but can still be used for decrypting and unwrapping and verifying pre-existing objects.
The CKA_BYTES_REMAINING attribute is available when HSM policy 12: Allow non-FIPS algorithms is set to 0, but cannot be viewed if that policy is set to 1.
The attribute is preserved during backup/restore using a Luna Backup HSM 7; restoring puts the counter back to whatever value it had before backup.
The attribute is not preserved through backup/restore using a Luna Backup HSM G5; restoring sets the counter to like-new state (no usage).
