Integration with CipherTrust Manager
To integrate Spectrum Scale with the CipherTrust Manager, you need to:
Configuring the CipherTrust Manager
To configure the CipherTrust Manager, you need to perform the following steps:
Add User
Note
Username should be same as the CN (Common Name) specified while creating the client certificate.
In the CipherTrust Manager UI, go to Access Management -> Users and create a new user.
Select the newly created user and then click GROUPS. Further, select the Key Users and Key Admins Group.
Registering a KMIP Client
You can register a KMIP client on the CipherTrust Manager using:
Using Auto-Registration
Create a registration token using the following steps:
Log on to the CipherTrust Manager.
Go to Access Management > Registration Tokens in the sidebar.
Click Create New Registration Token.
Copy the
Registration Token
once it is created.Turn ON Auto Registration using the following steps:
Go to Admin Settings > Interfaces.
Click the ellipsis button corresponding to the kmip interface.
Click Edit.
Under Configure KMIP window, select Auto Registration.
Paste the
Registration Token
.Select the mode as TLS, verify client cert, user name taken from client cert, auth request is optional.
Click Update.
Using Manual Registration
Log on to the CipherTrust Manager.
Go to Products > KMIP.
Create Client Profile using the following steps:
Go to Client Profile and click Add Profile.
Add a Profile Name.
Select CN in Username Location in Certificate.
Click Certificate Details.
Paste the content of
client.csr
.Click Save.
Create Registration Token using the following steps:
Go to Registration Token and click New Registration Token > Begin.
Add a Name Prefix.
Click Select CA.
Select CA type as Local if you are using Local CA or select external if you are using External CA.
Select appropriate CA from dropdown menu and click Select Profile.
Select the Client Profile from dropdown which you have created in the above step.
Click Create Token.
Copy the Token created and click Done.
Note
If you are using External CA then you can select the external CA which was created using openssl and uploaded on the CipherTrust Manager.
Go to Registered Clients and click Add Client.
Specify client name and paste the Registration Token generated in the above step.
Note
If you are using external CA then you need to paste the signed client certificate in the Client Certificate field.
Click Save to save the client certificate.
Configure Interface
Configure a KMIP Interface using the following steps:
Go to Admin Settings > Interfaces.
On the KMIP Interface, click the action button (...) and then click Edit.
Configure KMIP popup opens.
Check Auto Registration option if you are going with Auto Registration or uncheck if you are going with the Manual Registration.
Select the mode as TLS, verify client cert, user name taken from client cert, auth request is optional.
Specify selections for Local CA for Automatic Server Certificate Generation as desired.
Note
Local CA for Automatic Server Certificate Generation should be set to Turn off auto generation from Local CA in case of External CA.
Select the CA according to your preference.
If you are using External CA then select the CA under External Trusted CAs
If you are using Local CA then select the CA under Local Trusted CAs
This step is required if you are using external CA.
Expand the Upload Certificate section:
In the Certificate field, paste the contents of Server Certificate, CA, and Server Key file in the same order. Do not introduce any space or character or symbol between the contents of these files.
Select certificate Format as PEM.
Password field is optional and can be skipped.
Click Update.
Creating Key using API Playground
At the top right corner of the main toolbar, click API to go to the API playground.
Click Authenticate on the top right corner. Specify username and password, then click Post.
Note
The session will be valid for 300 seconds. You can also authenticate later if you are unable to perform the following steps within this time frame.
Go to Keys section in the left sidebar. Click Create - Post.
Specify the following content in the body, and click POST. Specify a value equal to or less than 60 characters.
{ "idSize": 60 }
Here idSize:60 will be set to the ID of the key, which will be further used while configuring the policy file of the Spectrum Scale.
Caution
Specifying a value greater than 60 leads to integration failure. To view the list of possible errors, go to the Troubleshooting section.
Updating the Key Attributes
In the CipherTrust Manager UI, go to Keys and click the Key you have created using API.
Ensure that Exportable option is checked.
Select the user (created above) as the Key Owner.
Click Update.
Configuring the Spectrum Scale
IBM Spectrum Scale connects with the CipherTrust Manager configured using the
RKM.conf
stanza.For more details, refer to the Pre-Integration section.
Create a policy file with any desired name, ex
hsm62
in any of the client node. Paste the following content in this policy file.RULE 'p1' SET POOL 'system' /* one placement rule is required at all times */ RULE 'Encrypt all files in file system with rule E1' SET ENCRYPTION 'E1' WHERE NAME LIKE '%' RULE 'rule1' ENCRYPTION 'E1' IS ALGO 'DEFAULTNISTSP800131A' KEYS('cd1929c52e4b2e5a8047d6e6815cf41df8d4d664bb78b85991ecce5bce56:client')
Note
cd1929c52e4b2e5a8047d6e6815cf41df8d4d664bb78b85991ecce5bce56 is the ID of the key created on the CipherTrust Manager.
client
is the RKM stanza ID in /var/mmfs/etc/RKM.conf.Ensure that the correct key ID and RKM ID are used in the policy. For details regarding the IBM Spectrum Scale policy rules, click here.
Install the encryption policy, using the following command.
/usr/lpp/mmfs/bin/mmchpolicy fs0 hsm62
Note
fs0
is an IBM Spectrum Scale file system that is created during installation and deployment phase of IBM Spectrum Scale.Upon successful encryption, following message is displayed:
Policy 'hsm62' installed and broadcast to all nodes.
If all steps were followed correctly, the integration between CipherTrust Manager and IBM Spectrum Scale will be successful. Both devices can now communicate with each other, and the IBM Spectrum Scale can now encrypt the data present in its nodes using the HSM key.
You can further verify if the integration is successful, using the steps mentioned in Verifying Your Integration.