Updating the HSM firmware or boot loader
The ProtectServer 3 HSM firmware and boot loader can be upgraded to newer versions by using a secure upgrade facility. This facility will only allow users to upgrade to a firmware or boot loader versions that Thales has distributed as a digitally signed file.
Supported firmware versions
The table below lists all firmware versions that Thales has released for the ProtectServer 3 HSM to date. Unless stated otherwise, the ProtectServer 3 HSM Firmware versions listed below are compatible with all ProtectServer 3 HSM variants.
The firmware versions listed below have been released for ProtectServer 3 HSM deployments that require FIPS 140-2 Level 3 compliance and validation.
Released firmware versions for FIPS 140-2 Level 3 deployments and their FIPS validation status
| Firmware | FIPS validation status |
|---|---|
| 7.02.04 | Validated |
| 7.02.03 | Not validated |
| 7.02.02 | Validated |
| 7.02.01 | Not validated |
| 7.02.00 | Not validated |
| 7.01.02 | Validated |
| 7.01.01 | Validated |
| 7.01.00 | Not validated |
| 7.00.01 | Validated |
| 7.00.00 | Not validated |
The firmware versions listed below have been released for ProtectServer 3 HSM deployments that require FIPS 140-3 Level 3 compliance and validation.
Released firmware versions for FIPS 140-3 Level 3 deployments and their FIPS validation status
| Firmware | FIPS validation status |
|---|---|
| 7.03.01 | Pending |
| 7.03.00 | Not validated |
Supported boot loader versions
The table below lists all boot loader versions that Thales has released for the ProtectServer 3 HSM to date.
Note
Thales recommends using the latest boot loader version.
| Boot loader | FIPS validation status |
|---|---|
| 1.2.1 | Validated |
| 1.2.0 | Validated |
| Boot loader | FIPS validation status |
|---|---|
| 1.2.1 | Pending |
| 1.2.0 | Pending |
Updating the firmware or boot loader
The upgrade procedure can only be performed by the ProtectToolkit-C Administrator using the ctconf command line utility.
Caution
Back up all important user data and keys before proceeding, because if certain security policies are in place, the HSM may perform a soft-tamper before the firmware or boot loader upgrade process begins. This tamper will erase all key and configuration data on the HSM. Refer to Security policies and user roles for more information on security policies.
You cannot downgrade back to an older boot loader version after upgrading.
Prerequisites
Before upgrading the firmware or boot loader:
-
Take note of the current HSM configuration.
-
Close all applications using the HSM.
To update the ProtectServer 3 HSM firmware or boot loader
-
Run the following command from a command prompt, where <filename> refers to the name of a firmware or boot loader upgrade file:
The user is prompted for the Administrator password.
Notification of the upgrade procedure's success or failure will be displayed.
-
Run ctconf -e to view the event log and verify that the firmware or boot loader was upgraded successfully.
Tip
The boot loader and firmware version can also be verified by monitoring the operation of the module upon boot with hsmtrace. For more information, refer to hsmtrace.
Following an upgrade, normal operation of ProtectToolkit-C can be resumed.
