copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2024-05-30 |
rotate, rotate master key, rotate encryption key, rotate root key, rotate keys automatically, key rotation, rewrap data |
hs-crypto |
{{site.data.keyword.attribute-definition-list}}
{: #master-key-rotation-intro}
After you load a master key to your {{site.data.keyword.hscrypto}} instance, you can rotate the master key on demand to meet industry standards and cryptographic best practices. {: shortdesc}
A master key is used to wrap encryption keys that are managed in the service instance. With the master key rotation, you retire the original master key and load a new master key that reencrypts the entire key storage.
When the master key is being rotated, you can still perform some KMS key actions such as listing keys, retrieving key metadata, or deleting keys, but you cannot create or rotate keys. You cannot call either the PKCS #11 API or GREP11 API during the master key rotation. {: note}
{: #how-master-key-rotation-works}
Master key rotation works by securely transferring the value between two types of master key registers in crypto units: new master key register and current master key register. Depending on the approach that you use to initialize your service instance, the rotation process is slightly different.
{: #how-master-key-rotation-works-smard-cards}
Master keys that are created with the Management Utilities can be rotated by using the smart cards, where master key parts are stored. Before you rotate the master key, you need to create the key parts that you are going to use.
You can create a new master key value using either 2 or 3 key parts. To be able to rotate the master key, the current master key registers must be in Valid
state with the same verification pattern and the new master key registers must be Empty
.
You can rotate the master key using the Management Utilities regardless of whether your service instance has recovery crypto units assigned to it or not.
The following flow shows how master key rotation works in this mode:
- Load the new master key register by clicking the Load button in the Trusted Key Entry application. The state of the new master key register is changed from
Empty
toFull uncommitted
. - Commit the new master key value by clicking the Commit button in the Trusted Key Entry application. The new master key register state is changed to
Full committed
. - Reencrypt key storage and activate the new master key by clicking the Rotate button in the Trusted Key Entry application:
- Encryption keys in key storage are decrypted by using the value in the current master key register and then reencrypted by using the value in the new master key register. The rewrapping takes place inside the hardware security module (HSM), so it's secure.
- The new master key is activated and loaded to the current master key register in
Valid
state, and the new master key register is cleared and back toEmpty
state.
The following chart illustrates how the master key register state changes during the master key rotation. For detailed instructions, see Rotating master keys by using smart cards and the Management Utilities.
{: caption="Figure 1. How master key register state changes during master key rotation" caption-side="bottom"}
{: #how-master-key-rotation-works-recovery-crypto-unit}
If your service instance has recovery crypto units assigned to it, apart from using key part files, you can also rotate the master keys using the ibmcloud tke auto-mk-rotate
command. With this command, a random new master key value is generated in one of the recovery crypto units for the service instance and securely moved to the other crypto units in the service instance.
Use the ibmcloud tke auto-mk-rotate
command to rotate the master key only when your service instance has recovery crypto units assigned and PKCS #11 keystores are not enabled in your service instance. Currently, supported regions other than Madrid (eu-es
) are enabled with the recovery crypto units. For more information about the supported regions, see Regions and locations.
{: important}
You don't need to prepare a new master key before the master key rotation. Before you can rotate the master key with the {{site.data.keyword.IBM_notm}} TKE CLI plug-in, all the current master key registers in both operational crypto units and recovery crypto units need to be in Valid
state with the current master key loaded and all the new master key registers needs to be empty.
Comparing to the option where you load a new master key value from your local workstation files, the main difference in this mode is that a new master key value is first randomly generated within a recovery crypto unit and then exported to other crypto units.
The following flow shows how master key rotation works in this mode:
- A new random master key value is generated in the new master key register of a recovery crypto unit assigned to the service instance. The state of the new master key register is changed from
Empty
toFull uncommitted
. - The new master key value is copied to the new master key registers of the crypto units that are assigned to the service instance and other recovery crypto units for the service instance. All the new master key registers now are in
Full uncommitted
state. - The new master key is committed, and all the new master key registers state are changed to
Full committed
. - Key storage is reencrypted. Encryption keys that are managed in the service instance are decrypted using the current master key in the current master key registers and reencrypted using the new master key in the new master key registers.
- The new master key is loaded to the current master key registers of the operational and recovery crypto units for the service instance in
Valid
state, and the new master key registers are cleared and back toEmpty
state.
For detailed instructions on how to rotate master keys by using recovery crypto units, see Rotating master keys by using recovery crypto units.
{: #how-master-key-rotation-works-use-key-part-files}
Master keys that are created from key part files can be rotated by using TKE CLI plug-in. When master keys are rotated, master key parts are stored in files on the local workstation.
Similar to using the Management Utilities, you need to first create the 2 or 3 key parts that you are going to use. To be able to rotate the master key, the current master key registers must be in Valid
state with the same verification pattern and the new master key registers must be Empty
.
You can rotate the master key using TKE CLI plug-in regardless of whether your service instance has recovery crypto units assigned to it or not.
The following flow shows how master key rotation works in this mode:
- Load the new master key register by using the
cryptounit-mk-load
command. The state of the new master key register is changed fromEmpty
toFull uncommitted
. - Commit the new master key value by using the
cryptounit-mk-commit
command. The new master key register state is changed toFull committed
. - Reencrypt key storage and activate the new master key by using the
cryptounit-mk-rotate
command:- Encryption keys in key storage are decrypted by using the value in the current master key register and then reencrypted by using the value in the new master key register. The rewrapping takes place inside the HSM, so it's secure.
- The new master key is activated and loaded to the current master key register in
Valid
state, and the new master key register is cleared and back toEmpty
state.
For detailed instructions, see Rotating master keys by using key part files.
{: #master-key-rotation-next}
For more detailed instructions on options to rotate master keys, see: