Luna USB HSM 7 Firmware 7.9.3
Luna USB HSM 7 firmware version 7.9.3 was released in September 2026.
>Download Luna USB HSM 7 Firmware 7.9.3
CAUTION! Read the Advisory Notes before installing this update, to be aware of important changes that may require your attention.
New Features and Enhancements
This release synchronizes the functionality of the Luna USB HSM 7 with the latest Luna Network HSM 7 and Luna PCIe HSM 7 releases. Luna USB HSM 7 firmware 7.9.3 includes the following new features and enhancements:
Firmware parity and PQC key backup across Luna HSM form factors
The complete key life cycle management can be secured with quantum safe mechanisms:
•generation
•usage
•backup/restore
in a full streamlined process across Luna PCIe HSM 7, Luna Network HSM 7, Luna USB HSM 7, and PQC keys can be backed-up and restored with the Luna Backup HSM 7.
Communication with and between Luna HSMs is also quantum safe.
Requires Luna HSM Client 10.9.4 in order to perform Cloning Protocol version 4 (CPv4) operations with PQC cloning cipher ML-KEM.
Advisory Notes
This section highlights important issues you should be aware of before installing Luna USB HSM 7 firmware version 7.9.2.
Migrate Keys From Luna USB HSM G5 Before Updating to This Version
Luna USB HSM 7 Firmware 7.7.3 or newer in FIPS-approved configuration (HSM policy 12: Allow non-FIPS algorithms or partition policy 43: Allow non-FIPS algorithms set to 0) disallows cloning from a Luna USB HSM G5. Therefore, you must migrate your keys to Luna USB HSM 7 Firmware 7.7.2, before updating to this version.
Requires Luna HSM Client 10.9.2 or Newer
This version of the Luna USB HSM 7 firmware requires Luna HSM Client 10.9.2 or newer.
FIPS Changes in Luna USB HSM 7 Firmware 7.9.2 and Newer
This release synchronizes functionality with the latest release of the Luna HSM firmware. New restrictions have been added to some mechanisms when the HSM or partition is in FIPS approved configuration (HSM policy 12: Allow non-FIPS algorithms or partition policy 43: Allow non-FIPS algorithms set to 0), to comply with FIPS 186-5 Digital Signature Standard (NIST SP 800-186).
RSA Key Pair Generation Mechanisms for FIPS 186-3 Allow 6144- and 8192-Bit Keys
Using the following mechanisms, you can now generate 6144-bit and 8192-bit RSA keypairs in FIPS approved configuration:
>CKM_RSA_FIPS_186_3_AUX_PRIME_KEY_PAIR_GEN
>CKM_RSA_FIPS_186_3_PRIME_KEY_PAIR_GEN
New Partition Policy Allows Signature Verification with ECDSA and RSA
A new partition policy 45: Allow ECDSA/RSA Prehash SigVer enables a prehash operation that allows mechanisms that do not have a hash function to perform verification. With this policy enabled, the following mechanisms are now permitted to perform verification in FIPS approved configuration:
Mechanisms that are now available in FIPS 140 approved configuration
The following mechanisms are now available for use in FIPS 140 approved configuration (formerly FIPS mode):
Mechanisms no longer available in FIPS 140 approved configuration
The following mechanism is now restricted from use in FIPS 140 approved configuration (formerly FIPS mode):
>CKM_EC_MONTGOMERY_KEY_PAIR_GEN
Mechanisms not permitted to sign objects in FIPS 140 approved configuration
The following mechanisms are not permitted to sign objects in FIPS 140 approved configuration:
Mechanisms now check for approved EC curves in FIPS 140 approved configuration
The following mechanisms now verify that the specified EC curve is FIPS-approved, and reject operations that specify non-approved curves:
>CKM_EC_KEY_PAIR_GEN_W_EXTRA_BITS
Allowed Elliptic Curves
| Curve Name | Mechanisms | Curve Field Type | Security Strength | Permitted Operations | ||
|---|---|---|---|---|---|---|
| Sign | Verify | Derive | ||||
| B-233 |
ECDSA, EC key Thales terminology |
Binary Field – GF(2m) | 112-bits | X | X | X |
| B-283 | ECDSA, EC key establishment |
Binary Field – GF(2m) | 128-bits | X | X | X |
| B-409 | ECDSA, EC key establishment |
Binary Field – GF(2m) | 192-bits | X | X | X |
| B-571 | ECDSA, EC key establishment |
Binary Field – GF(2m) | 256-bits | X | X | X |
| K-233 | ECDSA, EC key establishment |
Binary Field – GF(2m) | 112-bits | X | X | X |
| K-283 | ECDSA, EC key establishment |
Binary Field – GF(2m) | 128-bits | X | X | X |
| K-409 | ECDSA, EC key establishment |
Binary Field – GF(2m) | 192-bits | X | X | X |
| K-571 | ECDSA, EC key establishment |
Binary Field – GF(2m) | 256-bits | X | X | X |
| P-244 | ECDSA, EC key establishment |
Prime field – GF(p) | 112-bits | X | X | X |
| P-256 | ECDSA, EC key establishment |
Prime field – GF(p) | 128-bits | X | X | X |
| P-384 | ECDSA, EC key establishment |
Prime field – GF(p) | 192-bits | X | X | X |
| P-521 | ECDSA, EC key establishment |
Prime field – GF(p) | 256-bits | X | X | X |
| Edwards448 | EdDSA |
Prime field – GF(p) | 224-bits | X | X | X |
| Edwards25519 | EdDSA |
Prime field – GF(p) | 128-bits | X | X | X |
| Brainpool P512r1 | ECDSA, EC key establishment |
Prime field – GF(p) | 256-bits | X | X | X |
| Brainpool P512t1 | ECDSA, EC key establishment |
Prime field – GF(p) | 256-bits | X | X | X |
| Brainpool P-384r1 | ECDSA, EC key establishment |
Prime field – GF(p) | 192-bits | X | X | X |
| Brainpool P-384t1 | ECDSA, EC key establishment |
Prime field – GF(p) | 192-bits | X | X | X |
| Brainpool P320r1 | ECDSA, EC key establishment |
Prime field – GF(p) | 160-bits | X | X | X |
| Brainpool P320t1 | ECDSA, EC key establishment |
Prime field – GF(p) | 160-bits | X | X | X |
| secp256k1 | Blockchain | Prime field – GF(p) | 128-bits | X | X | no* |
| Brainpool P-256r1 | ECDSA, EC key establishment |
Prime field – GF(p) | 128-bits | X | X | X |
| Brainpool P-256t1 | ECDSA, EC key establishment |
Prime field – GF(p) | 128-bits | X | X | X |
| Brainpool P-224r1 | ECDSA, EC key establishment |
Prime field – GF(p) | 112-bits | X | X | X |
| Brainpool P-224t1 | ECDSA, EC key establishment |
Prime field – GF(p) | 112-bits | X | X | X |
The above table applies to Luna USB HSM 7 Firmware 7.9.2 and newer.
*The secp256k1 (BIP32) curve cannot be used for ECDH or ECIES derivation in FIPS 140 approved configuration.
Partition Policy 9: Allow DigestKey is Destructive When Turned On
Partition policy 9: Allow DigestKey is set to 0 by default when you update to Luna USB HSM 7 Firmware 7.9.3 or newer, and it is destructive when changed from 0 to 1. If you were using C_DigestKey with Luna USB HSM 7 Firmware 7.7.2, and you need to continue using it, you must back up the contents of your application partition and restore them after changing the policy. Refer to Partition Backup and Restore.
FIPS Changes in Luna USB HSM 7 Firmware 7.7.3 and Newer
New restrictions have been added to some mechanisms when the HSM or partition is in FIPS approved configuration (HSM policy 12: Allow non-FIPS algorithms or partition policy 43: Allow non-FIPS algorithms set to 0), to comply with NIST SP800-131a Rev2 and SP800-56B Rev2, published in March 2019.
Mechanisms no longer available in FIPS approved configuration
The following mechanisms are no longer available in FIPS approved configuration:
>CKM_EC_MONTGOMERY_KEY_PAIR_GEN
NOTE If you need to generate FIPS-compliant domain parameters for this mechanism, use CKM_DSA_PARAMETER_GEN with modulus length 2048 or 3072.
DES/DES3 encryption not permitted using ECIES mechanisms
The following mechanisms are not permitted to encrypt in FIPS approved configuration (decrypt operations are permitted):
HMAC mechanisms not permitted to sign using DES3 keys
The following mechanisms are not permitted to sign objects with a DES3 key in FIPS approved configuration (verify operations are permitted):
Mechanisms now check for approved EC curves in FIPS mode
The following mechanisms now verify that the specified EC curve is FIPS-approved, and reject operations that specify non-approved curves:
>CKM_EC_KEY_PAIR_GEN_W_EXTRA_BITS
CKM_RSA_PKCS not permitted to decrypt/unwrap objects
To comply with FIPS 140-3 requirements, RSA-based key transport schemes that use only PKCS#1-v1.5 padding are disallowed. Therefore, CKM_RSA_PKCS is now restricted from performing decrypt/unwrap operations.
NOTE When the HSM or partition is in FIPS approved configuration (HSM policy 12: Allow non-FIPS algorithms or partition policy 43: Allow non-FIPS algorithms set to 0), CKM_RSA_PKCS is disabled even if partition policy 33: Allow RSA PKCS mechanism is set to 1.
3DES usage counter has been removed
The 3DES usage counter attribute (CKA_BYTES_REMAINING) has been removed in Luna USB HSM 7 Firmware 7.7.3 and newer, to comply with FIPS 140-3 requirements. This attribute is now ignored on any keys where it is already set.
FIPS Changes in Luna USB HSM 7 Firmware 7.7.2 and Newer
New restrictions have been added to some mechanisms when the HSM or partition is in FIPS approved configuration (HSM policy 12: Allow non-FIPS algorithms or partition policy 43: Allow non-FIPS algorithms set to 0), to comply with FIPS SP800-131a Rev2, published in March 2019. Consider these functional changes when migrating from Luna USB HSM G5.
Mechanisms not permitted to wrap objects in FIPS mode
The following mechanisms are not permitted to wrap objects in FIPS mode (unwrap operations are permitted):
Mechanisms not permitted to sign data in FIPS mode
The following mechanisms are not permitted to sign data in FIPS mode (verify operations are permitted):
Mechanisms approved for use in FIPS mode
The following mechanisms are now approved for use in FIPS mode:
