Cryptographic algorithms

Introduction

This topic details the implemented restrictions imposed in various firmware modes. It covers different module features, not just algorithms and mechanisms.

For the most part, a blank table cell means "no restriction"; there are a few exceptions to this, for example, flag settings for particular modes. The information is low-level and may need interpreting to answer high-level questions. This topic does not cover higher level APIs like PKCS#11 or JCE.

The document was last updated in June 2024, for v13.5.1/v13.6.3.

Security World mode designation new-world "mode" parameter Description

Unrestricted

The unrestricted Security World mode protects keys with FIPS approved cryptography, but it is not designed to be fully compliant with all the requirements and restrictions of a particular certification standard.

This mode can be used by customers who want their keys securely managed within the FIPS level 3 boundary, but don’t need full compliance with the certification approved modes of operation.

For Solo XC, Solo+ and Edge, the unrestricted mode is compliant with FIPS 140-2 Level 2.

FIPS 140 Level 3

fips-140-level-3

This is the FIPS 140 level 3 approved mode of operation.

Customers needing FIPS 140 Level 3 compliance can use this mode on an HSM with a FIPS validated fw version.

Common Criteria CMTS

common-criteria-cmts

The Common Criteria approved mode of operation for Protection Profile EN 419 221-5 Cryptographic Module for Trust Services.

Customers needing Common Criteria (CC) compliance can use this mode on an HSM with a CC validated fw version.

FIPS information

In a FIPS 140 Level 3 Security World, the nShield HSM only supports FIPS-approved algorithms and key sizes.

  • If you have a FIPS 140 Level 3 Security World and have any protocols that use algorithms not approved by FIPS, you have the following options:

    • If you need to use these non-approved algorithms, you can migrate to a

      • (nShield Connect, Edge, and Solo HSMs) FIPS 140 Level 2 Security World.

      • (nShield 5c and 5s HSMs) Non-FIPS Security World but continue to use hardware and firmware validated for FIPS 140 Level 3.

    • If you have strict FIPS 140 Level 3 requirements, you must replace your protocols to use approved algorithms.

  • If you have a FIPS 140 Level 3 Security World and have existing long-term keys for unapproved algorithms, you have the following options:

    • Migrate to a

      • (nShield Connect, Edge, and Solo HSMs) FIPS 140 Level 2 Security World.

      • (nShield 5c and 5s HSMs) Non-FIPS Security World but continue to use hardware and firmware validated for FIPS 140 Level 3.

    • Replace the keys with approved keys before upgrading to the current firmware. Keys for unapproved algorithms are incompatible with this Security World.

To obtain more details on the specific algorithms that are FIPS approved for use in the HSM, refer to the nShield Security Policy for the particular FIPS CMVP certified nShield product that you are using.

For the FIPS CMVP certificates for nShield products, see https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search. The FIPS CMVP certificate links to the Security Policy.

Compatibility of Security World versions with FIPS

To comply with the latest FIPS cryptographic transitions, Security World v3 was introduced in firmware version 12.50. If an nShield HSM is upgraded to use firmware version 12.50 or later, any v2 Security Worlds using the HSM that were compliant with FIPS 140 Level 3 will no longer be compliant.

You can create a v3 Security World that is compliant with FIPS 140 Level 3 from a host server if you meet the following criteria:

  • The host server is running Security World host-side software version 12.50 or later.

  • The HSM is running firmware version 12.50 or later.

Your solution is only FIPS 140 compliant if you are running the exact firmware version that has been FIPS 140 certified.