See below for creating a CloudKey for GCP.
To create a CloudKey for GCP
Log in to the Cryptographic Security Platform Vault for Cloud Keys webGUI using an account with Cloud Admin privileges.
- In the top menu bar, click CloudKeys.
Click the CloudKeys tab.
Select the Key Set and Key Ring.
If you do not finish the selections on the CloudKeys page, add them on the Details tab of the Create CloudKey dialog box.
- Select Actions > Create CloudKey.
On the Details tab of the Create CloudKey dialog box, enter the following:
- Key Ring—If you did not finish selecting the Key Set prompts, select the Region here.
- Name—Enter the name for the CloudKey.
- Description—Enter the optional description for the CloudKey.
- Key Management—Choose Customer Managed Key.
- Click Continue.
On the Purpose tab, complete the following:
- Click Continue.
On the Schedule tab, determine the rotation schedule for the CloudKey. This can be one of the following:
- Inherit from Key Set—The CloudKey will use the key set default schedule. If the Key Set schedule changes after you create the CloudKey, the CloudKey schedule will not update.
- Never—The CloudKey will never be rotated.
- Once a year—The CloudKey will be rotated once a year.
- Every 6 months—The CloudKey will rotate every 6 months.
- Every 30 days—The CloudKey will rotate every 30 days.
- Other—The CloudKey will be rotated at the interval you select.
Choose when this CloudKey version should expire. The per-version expiration can be one of the following:
- Never—The CloudKey version will never expire.
- Fixed Date—All CloudKey versions will expire on the date that you set.
- Relative Expiry—Each CloudKey version will expire after the number of days that you set.
Choose when the CloudKey should expire. This can be Never, or you can choose a specific date.
If you selected an expiration date, choose the Expire Action to define what happens to the CloudKey when it expires. This can be one of the following:
Disable—The key will remain in the cloud, but is disabled and cannot be used by any applications.
Delete—The key is disabled in the cloud and cannot be used by any applications. You can set the date for permanent deletion.
Delete from Cloud—Removes the key material from the KMS, and applications can no longer use this key from the cloud. However, the Cryptographic Security Platform Vault retains a copy of the key, which you can upload back to the cloud.
- Click Apply.
Protection Level
Choose whether to protect your key with software or an HSM.
Purpose
This can be one of the following:
- Symmetric encrypt/decrypt
- Asymmetric decrypt
- Asymmetric Sign
- MAC signing/verification
Algorithm
Choose the algorithm that matches the purpose you selected. This can be one of the following:
- For Symmetric encrypt/decrypt:
- Google symmetric key
- For asymmetric decryption:
- 2048-bit RSA - OAEP Padding - SHA1 Digest
- 2048-bit RSA - OAEP Padding - SHA256 Digest
- 3072-bit RSA - OAEP Padding - SHA1 Digest
- 3072-bit RSA - OAEP Padding - SHA256 Digest
- 4096-bit RSA - OAEP Padding - SHA1 Digest
- 4096-bit RSA - OAEP Padding - SHA256 Digest
- 4096-bit RSA - OAEP Padding - SHA512 Digest
- For Asymmetric Sign:
- Elliptic Curve P-256 - SHA256 Digest
- Elliptic Curve P-384 - SHA384 Digest
- 2048 bit RSA - PKCS#1 v1.5 padding - SHA256 Digest
- 3072 bit RSA - PKCS#1 v1.5 padding - SHA256 Digest
- 4096 bit RSA - PKCS#1 v1.5 padding - SHA256 Digest
- 4096 bit RSA - PKCS#1 v1.5 padding - SHA512 Digest
- 2048 bit RSA - PSS Padding - SHA256 Digest
- 3072 bit RSA - PSS Padding - SHA256 Digest
- 4096-bit RSA - PSS Padding - SHA256 Digest
- 4096-bit RSA - PSS Padding - SHA512 Digest
- For MAC signing/verification:
- HMAC - SHA256 Digest