Managing the IBM Guardium Key Lifecycle Manager master key
Use the IBM Guardium Key Lifecycle Manager graphical user interface or a REST interface to set a master key and then move the master key to a different repository according to your organization needs.
Before you begin
About this task
- JCEKS
Java Cryptography Extension Keystore
(JCEKS) is the default master keystore.- HSM
- Configure
Hardware Security Module
(HSM) to store the master key. For more information, see Integrating HSM with IBM Guardium Key Lifecycle Manager. - UKO
- Configure
Unified Key Orchestrator
(UKO) to store the master key. For more information, see Unified Key Orchestrator usage in IBM Guardium Key Lifecycle Manager.
After you create the first server certificate or key, a AES 256-bit
master key
is generated in the IBM Guardium Key Lifecycle Manager server. When you
set the keystore for the first time by using graphical user interface or Master Key REST Service, a
new master key is created. All the cryptographic data that was encrypted with the earlier master key
is reencrypted with the new master key.
When you move the master key from one repository (source) to another repository (destination), IBM Guardium Key Lifecycle Manager automatically uses the master key from the destination repository for encryption. When you move the master key from JCEKS to HSM or UKO, the JCEKS key repository is deleted. However, when you move the master key from HSM or UKO to JCEKS, the master key in HSM or UKO is not deleted.
You can also use the REST services to manage the master key. For more information, see Master key management REST services.