CyberArk privilege account security solution integrates with SmartKey service to enhance the security and availability of encryption keys. The document contains the necessary information to deploy SmartKey service with the CyberArk Enterprise Password Vault (EPV®) solution.
CyberArk Privileged Account Security Solution is an enterprise class, unified platform that allows organizations to manage and secure all privileged accounts. The solution secures credentials, including passwords and SSH keys, controls access to these accounts, and isolates and records privileged sessions that may assist with audit¬ing and forensics analysis. SmartKey delivers unified HSM and Key Management capabilities to securely generate, store, and use cryptographic keys and certificates.
The combined solution of SmartKey and CyberArk EPV, delivers enhanced security and availability for encryption keys used to access safes or files within the CyberArk solution to ensure confi¬dentiality, integrity, and availability of critical enterprise data. SmartKey leverages Runtime Encryption™ and Intel® SGX in a FIPS compliant HSM to deliver deterministic security for encryption keys. The joint solution maximizes the security of encryption keys used to protect enterprise credentials and passwords to help guard against threats exploiting insider privileges.
For new deployments, please review the SmartKey installation guide for pre-requisites and deployment procedures. Once complete, you can review the instructions for getting started: http://support.smartkey.io/smartkey/getting-started.html.
SmartKey Configuration for CyberArk
Sign up for SmartKey service
SmartKey is accessible from the browser at https://www.smartkey.io. Sign up as a user on this site.
Create an account
Use your credentials to login to SmartKey. Here, you can create a new account or accept an invitation to join another account. After entering an account, you can view and manage groups, users, applications, and security objects belonging to the account.
If you have a newly-created account, use the following steps to add your first group and application to SmartKey.
Add a group
A group is a collection of security objects created by and accessible by users and applications which belong to the group. The user who creates a group automatically gets assigned the role of the group administrator. You can add more users to the group in the role of administrators or auditors. You can also add applications to the group to enable the applications to create and use security objects in that group.
To add a group, you may specify:
- The title of the group (required).
- A short description for the group (required).
- Users in your account as members.
- Applications in your account to add to the group so that they can use the security objects in the group.
Add an application corresponding to EPV
An application can use SmartKey to generate, store, and use security objects, such as cryptographic keys, certificates, or an arbitrary secret. Examples of applications include web servers, PKI servers, key vaults, etc. An application can interact with SmartKey using the REST APIs or using the PKCS#11, JCE, or CNG providers.
EPV integrates with SmartKey using the PKCS#11 interface.
To add an application, you may specify:
- Name of the application (required).
- A short description for the application.
- Choose API Key as the form of authentication.
- Select the group created in the previous step for this application.
Download KMS Windows Client and configure it
The SmartKey client for Windows 64-bit can be downloaded from http://support.smartkey.io/smartkey/resources.html.
SmartKeyKmsClient.msi installs the SmartKey PKCS#11 library.
The SmartKey URL needs to be configured for the PKCS#11 DLL to communicate with. This is done by running the fol¬lowing command:
C:\Program Files\Fortanix\KmsClient\FortanixKmsClientConfig. exe machine –api-endpoint https://api.amer.smartkey.io.
The PKCS#11 DLL gets installed in
C:\Program Files\Fortanix\KmsClient\FortanixKmsPkcs11.dll. The path to this file needs to be configured in the CyberArk EPV software in the next steps.
CyberArk EPV configuration
The following steps describe the configuration that needs to be done at CyberArk EPV to use SmartKey.
For network access, add the following line to your windows host file on
<IP Address> smartkey.<your-domain>.com
Add the following line to the file
C:\Program Files (x86)\PrivateArk\Server\dbparm.ini
Restart the Vault using the PrivateArk Server.
Configure path to PKCS#11 DLL
Browse and open the following file
C:\Program Files (x86)\PrivateArk\Server\dbparm.ini
At the bottom of the file, add the following lines:
[HSM] PKCS11ProviderPath=”C:\Program Files\Fortanix\KmsClient\FortanixKmsPkcs11.dll”
dbparm.ini file and close it.
Configure PKCS#11 PIN
Run the following command to configure the PIN for SmartKey. The program CAVaultManager is located at
C:\Program Files (x86)\PrivateArk\Server.
CAVaultManager SecureSecretFiles /SecretType HSM /Secret <hsmpincode>
The “hsmpincode” corresponds to the API key for the application generated. CyberArk restricts the length of the “hsmpincode” to 50 characters, so using the API Key as the parameter for “/Secret” throws an error. The workaround for this is to create a file
C:\tmp\apikey.txt with the contents:
api_key = “FEL/ME…j+bt7”
file://C:\tmp\apikey.txt as the “hsmpincode”. Open
dbparm.ini to verify that HSMPinCode parameter was added with the encrypted value of the PIN.
Generate a new key in SmartKey
The following instructions assume the CyberArk Vault is already hardened.
- Stop the vault.
- Generate a new Operator Key in the HSM:
CAVaultManger GenerateKeyOnHSM /ServerKey
Record the HSM slot number returned by the command (HSM#2 in the example)
- Verify that the new key has been generated in SmartKey. To do this, login to the web interface of SmartKey using your user credentials, and go to the groups tab. Click on the group created in Section 4.3 to see a detailed view of objects in the group. Go to the security objects tab for the group, and find the new security object created by CyberArk EPV. Click on the security object to see the detailed view for the security object. On the bottom right, there should be an audit log stating that the key was created by the CyberArk EPV application at a specified time.
Make sure the master key is in the CD, then use the ChangeServerKeys command to re-encrypt the vault with the new key:
ChangeServerKeys C:\DemoOperatorKeys\ C:\DemoOperatorKeys\VaultEmergency.pass HSM#2
If successfully executed, the vault is now encrypted with the new key that was generated in the HSM. Modify the the ServerKey in the
Start the Vault service using the PrivateArk Server.