Steps to configure the Futurex PKCS #11 Library with CyberArk Vault

before proceeding with the steps in this section, you must install the cyberark pas solution for instructions on how to install the cyberark pas solution, refer to the cyberark online documentation at the following url https //docs cyberark com/productdoc/onlinehelp/pas/latest/en/content/pas%20inst/installationoverview\ htm after you install and start the cyberark vault, you can generate a new server key on the hsm the server key is the key used to provide access to the vault, much like the actual key of a physical vault you need the server key to start the vault, after which you can remove the key until you need to restart the server when you stop the vault, the information stored in the vault is completely inaccessible without the key configure the vault initially to use an hsm attached to the network, configure the firewall to enable communication to the hsm device in dbparm ini , configure the allownonstandardfwaddresses parameter to open the firewall and permit access to the device, as shown in the following example allownonstandardfwaddresses=\[hsm ip],yes,1024\ inbound/tcp,1024\ outbound/tcp if you use a cloud hsm accessible through the internet (rather than a physical hsm connected to the local network), do not define allownonstandardfwaddresses in the dbparm ini file configure the pkcs #11 provider dll and specify it in the pkcs11providerpath parameter in dbparm ini , as shown in the following example pkcs11providerpath=\<path to pkcs#11 provider dll> save dbparm ini and close it define the pin/passphrase that the vault uses when accessing an hsm from a command line, run the following command, specifying the password of the identity created on the hsm for this integration replace \<hsmpincode> with the password of the identity created on the hsm for this integration cavaultmanager securesecretfiles /secrettype hsm /secret \<hsmpincode> open dbparm ini and ensure you added the hsmpincode parameter with the encrypted value of the pin/passcode restart the privateark server to apply the new firewall rules shut down the privateark server load the server key into the hsm the following process installs and stores the server key on the hsm after you complete this process, storing the server key as a non exportable key on the hsm, the vault can use it generate the server key in the hsm stop the vault server if it is running run the following cavaultmanager command to generate the server key on the hsm cavaultmanager exe generatekeyonhsm /serverkey this command generates a new key for the vault server, stores it in the hsm, and returns the key generation keyword for example hsm#5 each time you create a key generation, the keyword allocated is one number higher than the current server key generation specified in dbparm ini to create additional key generations successfully, you must manually delete the first generation of the server key otherwise, an error occurs if the serverkey parameter in the cavaultmanager command specifies a path instead of an hsm keyword, the first key generation is created (such as hsm#1 ) re encrypt the vault data and metadata with the newly generated keys on the hsm run the following changeserverkeys command to change the encryption keys used for the vault server changeserverkeys pathtokeys pathtoemergencyfile hsmkeyword for example, the following command re encrypts the vault data and metadata with the encryption keys in k \privateark\keys , and the hsm#1 key becomes the server key changeserverkeys k \privateark\keys k \privateark\keys\vaultemergency pass hsm#1 open dbparm ini and specify in the serverkey parameter the value of the key generation version returned by the preceding cavaultmanager command, as shown in the following output example serverkey=hsm#1 start the vault server and ensure you can log onto the vault