CKM_RSA_PKCS
NOTE RSA public exponent value e=3 was deprecated, and Luna HSM does not support its use in FIPS 140 configuration. By default, use RSA exponent value 65537 (2^16 + 1) instead, or refer to the FIPS 186-5 Appendix A.1.1 specification for detailed guidance.
See also Impact on Exponents.
Firmware 7.9.0 and Newer Summary
| FIPS approved? | Yes |
| Supported functions | Sign | Verify | Encrypt | Decrypt | Wrap | Unwrap |
| Functions restricted from FIPS use | Cannot wrap | Cannot decrypt | Cannot unwrap | Cannot encrypt | Can verify only if PP45 enabled |
| Minimum key length (bits) | 256 |
| Minimum key length for FIPS use (bits) | 2048 |
| Minimum legacy key length for FIPS use (bits) | 1024 |
| Maximum key length (bits) | 8192 |
| Block size | 0 |
| Digest size | 0 |
| Key types | RSA |
| Algorithms | None |
| Modes | None |
| Flags | None |
NOTE Using Luna HSM Firmware 7.9.0 or newer, signature verification is permitted in FIPS approved configuration, as long as partition policy 45: Allow ECDSA/RSA Prehash SigVer is set to 1 on the partition.
TIP The default setting of partition policy 45 : Allow ECDSA/RSAPrehash SigVer varies according to firmware update status:
HSM Firmware starting at 7.9.0 or newer
•Default is OFF for partitions not in FIPS configuration.
•Default is OFF for partitions in FIPS configuration.
HSM Firmware older than version 7.9.0
For a starting firmware version between 7.7.1 and 7.8.9 updating to 7.9.0 and newer, the Partition Policy 45 behavior follows the FIPS partition policy 43
•Default is ON for partitions not already in FIPS configuration(*)
•Default is OFF for partitions already in FIPS configuration
Starting firmware older than version 7.7.1 did not have FIPS partition policy 43.
When updating to firmware 7.9.0, the Partition Policy 45 behavior follows the HSM-level FIPS policy 12 instead.
•Default is ON if HSM is not in FIPS configuration(*)
•Default is OFF if HSM is in FIPS configuration
(*When older firmware is being updated, this policy defaults to ON in non-FIPS configuration in order to minimize impact for customers updating existing HSMs; your partition behaves, for crypto operation, as it did before update, and action here is needed, only if you wish to change that behavior.)
Firmware 7.8.4-7.8.9 Summary
| FIPS approved? | Yes |
| Supported functions | Sign | Verify | Encrypt | Decrypt | Wrap | Unwrap |
| Functions restricted from FIPS use | Cannot wrap | Cannot decrypt | Cannot unwrap | Cannot encrypt |
| Minimum key length (bits) | 256 |
| Minimum key length for FIPS use (bits) | 2048 |
| Minimum legacy key length for FIPS use (bits) | 1024 |
| Maximum key length (bits) | 8192 |
| Block size | 0 |
| Digest size | 0 |
| Key types | RSA |
| Algorithms | None |
| Modes | None |
| Flags | None |
NOTE
>Using Luna HSM Firmware 7.8.4 and newer, this mechanism is restricted from all wrap/unwrap/encrypt/decrypt operations in FIPS approved configuration. No exceptions are made for decrypt/unwrap operations using larger key sizes. This limited legacy use was permitted under FIPS 140-2; it is no longer approved under FIPS 140-3.
>This mechanism name and RSASSA-PKCS1-v1_5 are referring to the same underlying RSA signature scheme.
Firmware 7.7.2-7.8.2 Summary
| FIPS approved? | Yes |
| Supported functions | Sign | Verify | Encrypt | Decrypt | Wrap | Unwrap |
| Functions restricted from FIPS use | Cannot wrap | Cannot legacy decrypt | Cannot legacy unwrap | Cannot encrypt |
| Minimum key length (bits) | 256 |
| Minimum key length for FIPS use (bits) | 2048 |
| Minimum legacy key length for FIPS use (bits) | 1024 |
| Maximum key length (bits) | 8192 |
| Block size | 0 |
| Digest size | 0 |
| Key types | RSA |
| Algorithms | None |
| Modes | None |
| Flags | None |
NOTE Under Functions restricted from FIPS use, "Cannot legacy decrypt and "Cannot legacy unwrap" means that these operations are restricted with smaller keys (1024-bits, the previous minimum key size for FIPS use), but keys that meet the minimum FIPS size requirement (2048 bits) can still be used for decrypt and unwrap operations.
Firmware 7.7.0-7.7.1 Summary
| FIPS approved? | Yes |
| Supported functions | Sign | Verify | Encrypt | Decrypt | Wrap | Unwrap |
| Functions restricted from FIPS use | Cannot wrap |
| Minimum key length (bits) | 256 |
| Minimum key length for FIPS use (bits) | 2048 |
| Minimum legacy key length for FIPS use (bits) | 1024 |
| Maximum key length (bits) | 8192 |
| Block size | 0 |
| Digest size | 0 |
| Key types | RSA |
| Algorithms | None |
| Modes | None |
| Flags | None |
NOTE To comply with FIPS SP800-131a Rev2 published in March 2019, when the HSM is in FIPS mode, this mechanism is not allowed to wrap objects.
Firmware 7.4.2 and Older Summary
| FIPS approved? | Yes |
| Supported functions | Sign | Verify | Encrypt | Decrypt | Wrap | Unwrap |
| Functions restricted from FIPS use | None |
| Minimum key length (bits) | 256 |
| Minimum key length for FIPS use (bits) | 2048 |
| Minimum legacy key length for FIPS use (bits) | 1024 |
| Maximum key length (bits) | 8192 |
| Block size | 0 |
| Digest size | 0 |
| Key types | RSA |
| Algorithms | None |
| Modes | None |
| Flags | None |
NOTE When the HSM is in FIPS mode, this mechanism cannot be used to sign data using less than 224 bits.
This algorithm must be combined with a FIPS-approved hash algorithm to be FIPS compliant.
