Configure Venafi TPP to use the Vectera Plus

perform the tasks in this section to integrate the venafi trust protection platform (tpp) with a {{futurex}} {{vectera}} hsm for data encryption, key generation, and key storage 1 | create an hsm connector and generate an hsm protected encryption key open the venafi configuration console application select the connectors node select \[ create hsm connector ] in the actions panel enter the local master admin username and password and select \[ ok ] in the create new hsm (cryptoki) connector window, for name , enter any name for the hsm connector for cryptoki dll path , select \[ browse ] and locate the following path to the {{futurex}} pkcs #11 dll file c \program files\futurex\fxpkcs11\fxpkcs11 dll select \[ load slots ] select the slot number configured in your {{futurex}} pkcs #11 configuration file (the default is slot 0 ) this is where tpp accesses the encryption keys for user type , leave the default option selected, crypto officer (user) venafi uses the identity configured in the {{futurex}} pkcs #11 file to connect to the {{vectera}} for pin , enter the password for the identity configured in the {{futurex}} pkcs #11 file select \[ verify ] if the connection to the hsm succeeds, a new permitted keys section displays select \[ new key ] in the create new hsm key window, enter a name and select the type for the key then, select \[ create ] if you plan to use venafi codesign protect to store private code signing keys in the {{vectera}} select the allow key storage checkbox select \[ create ] to save and close the window 2 | enable venafi advanced key protect you need venafi advanced key protect to generate hsm private keys in addition, venafi code signing certificate private key storage requires you to enable the feature to enable venafi advanced key protect, perform the following steps open the venafi configuration console application select \[ enable venafi advanced key protect ] in the actions panel enter the local master admin username and password and select \[ ok ] review the information in the following dialog, and select \[ enable ] if you want to proceed perform the following steps to restart the iis , venafi platform , and logging services select the product node select website and select \[ restart ] in the actions panel select venafi platform and select \[ restart ] in the actions panel select logging and select \[ restart ] in the actions panel 3 | generate an hsm private key venafi trust protection platform uses the {{vectera}} hsm to generate private keys for ssh keys and certificates you must create a certificate authority (ca) template object in venafi tpp to manage the certificate life cycle and generate an hsm key see venafi documentation for more information perform the following tasks the enable key generation and create a certificate a | configure the venafi platform policy to enable the vectera plus for hsm key generation log in to the admin console https //\[ip address of venafi tpp]/vedadmin select policy tree in the main menu at the top of the page in the policy certificate window, go to the certificate tab under other information select the name of the hsm connector you created for the {{vectera}} in the key generation drop down menu select the name of the hsm protected encryption key you created on the {{vectera}} hsm select \[ save ] at the bottom of the page b | generate the certificate select policy tree in the main menu at the top of the page on the left hand side of the page, select \[ add ] under the policy drop down menu and select certificates > certificate under general information , enter the required information, and for management type , select provisioning or enrollment under csr handling , leave service generated csr selected for csr generation and leave generate key/csr on application set to no under subject dn , enter the required information under private key , select the key algorithm to use and the desired key strength in bits under other information , search for and select the previously configured ca template select \[ save ] select the newly generated certificate from the policy tree the certificate status should be ok select \[ renew now ] the certificate status changes to queued for renewal after about a minute, select \[ refresh ] the certificate details appear in the window opyionally, if you selected provisioning for management type , associate the certificate to the intended application object 4 | configure code signing venafi codesign protect can store private code signing keys in the {{vectera}} hsm this section describes the basic steps to configure this functionality for the integration see venafi documentation for more details venafi tpp uses certificate authority (ca) template objects to manage the certificate life cycle you must create one to use code signing see venafi documentation for more information to use the {{vectera}} for key storage, you must enable key storage on the hsm connector a | assign permissions to a code signing administrator open the venafi configuration console application select the system roles node select \[ add codesign protect administrator ] in the actions panel select a user to grant codesign protect administrator permissions b | create a code signing flow open the venafi configuration console application under the code signing node, select custom flows select \[ add new code signing flow ] in the actions panel enter a name for the code signing flow select the newly created code signing flow and add an approver through the actions panel c | create an environment template for the code signing project open the venafi configuration console application under the code signing node, select environment templates select certificate in the actions panel under add single template enter a name for the code signing environment template and select \[ create ] in the properties window, within the settings tab, enter a description and select a certificate container and signing flow go to the certificate authority tab and select a ca template , and select \[ add ] go to the keys tab and select which key sizes to allow for rsa and elliptic curve keys go to the key storage tab and select the futurex hsm connector then, select \[ add ] enter any optional information in the remaining tabs, and select \[ ok ] d | create a new code signing project log in to aperture https //\[ip address of venafi tpp]/aperture/codesign select projects in the main menu at the top of the page select \[ create project ] enter a project name and description select \[ create ] e | create an environment for the project with a new hsm private key and certificate inside the newly created code signing project, go to the environments tab and select add environment > certificate & key enter the environment name select the environment template that you created for this code signing project for creation type , select create new the key storage location should now list the futurex hsm connector enter any other necessary information for the certificate select \[ save ] select \[ submit for approval ] to generate a new certificate and private key after you approve it in the next step f | approve the project log in to aperture https //\[ip address of venafi tpp]/aperture/codesign select approvals in the main menu at the top of the page under pending approvals , select the project creation request you just submitted select \[ approve ] you should see a message similar to approval processed successfully go back to the project, and on the environments tab, make sure you see that a certificate & key were created in hardware (such as the {{vectera}} )