As an encryption administrator, you can:
- Generate your encryption keys directly from the key manager device.
- Upload keys generated from an external crypto management application.
- Upload a wrapped key.
As an encryption administrator, you can:
Notes:
To generate keys:
Note: The Key Alias must:
You can upload an externally generated key in a compatible format. The key must be an AES-256 symmetrical key.
To upload keys:
Anaplan supports generation and export of keys used in asymmetric key encapsulation, or key wrapping, for additional security.
The process is:
Encryption Administrators can generate and export asymmetric keys.
To create and export an asymmetric key:
This step is performed by the customer outside of Anaplan.
Note: If you encounter difficulties importing the asymmetric key into your Hardware Security Module, review the Troubleshoot Wrapped Key Issues section below for some tips on how to address common issues.
To wrap your symmetric key with the asymmetric key:
Information to Enter | Value | Description |
HashAlgo: | SHA256, SHA384, or SHA512 | (Optional) The Hash Padding Algorithm used in the HSM. If not specified, the default is SHA256. |
MaskGenHashAlgo: | SHA256, SHA384, or SHA512 | (Optional) The Mask Generator used in the HSM. If not specified, the default is SHA256. |
Secret: | (The base64 encoded wrapped key) | Your wrapped key. If you have not specified a Hash Padding Algorithm or Mask Generator, then Secret: must be at the top of the page. |
HashAlgo: SHA512
MaskGenHashAlgo: SHA512
Secret: tlPE23P3jlxPHniXYYTr32NP0XY761NYhknIbY0H1s2
yTxDFmIDBJbLJgJzC7PUAh6vgXMw+/FJ1TpZ0chl6SsEenj0WAN
c0qlf9XHI2205g96YZ2A2hBOTn0kGjdY9BLhbNPQZoLFq/LlVFZ
WXQmjSio02oGfQFyFcwNpnmKGlHtZg3zASpaEaOc0Qba2hQBoUS
6aJb5/02fqhzOkAjpVU+NRmaRkS8KY5ObutDtmftwuTvguBNCBq
VF1HVHGKkJz70/mQO4dHoL4T97URyDs2xtGesrJM2GVGv6CENU5
CdukimdZznrq6aIYumvKPMdr/8DBKDVTbQBzVfjBL7Hg==
Note: Anaplan ignores any other content in the wrapped payload.
Encryption administrators can import the wrapped key.
Note: Wrapped keys must not contain carriage returns or new line entries. Before you import your wrapped key, examine the file in a text editor to ensure there are no carriage returns or new line entries in your wrapped key file.
To import the wrapped key:
By default, BYOK exports a plain asymmetric key. Some HSMs expect an asymmetric key formatted for Public Key Cryptography Standards (PCKS)#1. If you get an error indicating your import or key are not readable, try to insert a PCKS#1 header into the exported asymmetric key.
Note: This procedure is designed to work on Linux or MacOS machines. You must have openssl
To troubleshoot the wrapped key issues:
#!/bin/bash
# Convert exported asymmetric key to PKCS1 format
# The command below changes the PUBLIC KEY label
# to display as RSA PUBLIC KEY.
sed -e "s/PUBLIC KEY/RSA PUBLIC KEY/g" $1 > $1.pkcs8.pem
# The command below adds the header to the encrypted key.
openssl rsa -RSAPublicKey_in -in $1.pkcs8.pem -pubout > $1.pkcs1.pem
chmod +x
<script name>
<script file> <asymmetric key file>
sh convertPublicKey.sh myPublicKey.pem
This generates a two pem files. One has a pkcs8.pem suffix and one has a pkcs1.pem suffix. For example, if you convert myPublicKey.pem, the script outputs myPublicKey.pem.pkcs8.pem and myPublicKey.pem.pkcs1.pem.
Import the file with the pkcs1.pem suffix into your HSM.
Disclaimer
We update Anapedia content regularly to provide the most up-to-date instructions.