Configure Venafi Control Plane Cryptohub integratation

this section covers the following integration configuration tasks create an hsm connector and generate a key enable vebafi key protect generate an hsm private key configure code signing create a connector and generate a key perform the following steps to 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 click \[ ok ] in the create new hsm (cryptoki) connector window, specify a name for the hsm connector for cryptoki dll path , select \[ browse ] and select the {{futurex}} pkcs #11 dll file at the following path c \program files\futurex\fxpkcs11\fxpkcs11 dll select \[ load slots ] select the slot number configured in the fxpkcs11 configuration file (the default is slot 0 ) this is where venafi control plane accesses the encryption keys for user type , leave the default option selected, crypto officer (user) venafi uses the identity configured inside the fxpkcs11 configuration file when connecting to the {{ch}} for pin , enter the {{ch}} identity password configured inside the \<crypto opr pass> tag in the fxpkcs11 cfg file select \[ verify ] if the connection to the {{ch}} is successful, a new permitted keys section populates in the window select \[ new key ] in the create new hsm key window, enter a name and select the type for the key, and select \[ create ] if key creation is successful, the key is now viewable inside the venafi control plane service on the {{ch}} the name of the key is shown in the list of permitted keys in the create new hsm key window if you plan to use venafi codesign protect to store private code signing keys on the {{ch}} , select the allow key storage checkbox here select \[ create ] to save and close the window enable venafi advanced key protect hsm private key generation and venafi code signing certificate private key storage require you to enable venafi advanced key protect perform the following steps to do this 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 ] to proceed perform the following steps to restart the iis, venafi platform, and logging services select the product node select website and then select \[ restart ] in the actions panel select venafi platform and then select \[ restart ] in the actions panel select logging and then select \[ restart ] in the actions panel generate hsm private key venafi trust protection platform uses the {{ch}} for private key generation for ssh keys and certificates venafi control plane uses certificate authority (ca) template objects to manage the certificate life cycle creating one is a prerequisite to hsm key generation see venafi documentation for more information configure the venafi platform policy perform the following steps to configure the venafi platform policy to enable the {{ch}} 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 , perform the following steps select the name of the hsm connector you created for the {{ch}} in the key generation drop down menu select the name of the hsm protected encryption key you created on the {{ch}} select \[ save ] at the bottom of the page generate the certificate perform the following steps to generate the certificate select policy tree in the main menu at the top of the page on the left side menu, 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 a moment, select \[ refresh ] to show the certificate details in the window if you selected provisioning as the management type , associate the certificate with the intended application object configure code signing venafi codesign protect can store private code signing keys in the {{ch}} this section describes the basic steps to configure this functionality for the integration see venafi documentation for more details certificate authority (ca) template objects are used in venafi control plane to manage the certificate lifecycle creating one is a prerequisite to codesign see venafi documentation for more information to use an hsm for key storage, you must enable key storage on the hsm connector assign permissions perform the following steps to 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 create a code signing flow perform the following steps to 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 create an environment template perform the following steps to 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 settings tab of the properties window, 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 enable for rsa and elliptic curve keys open the key storage tab and select the futurex hsm connector , and select \[ add ] enter any optional information in the remaining tabs, and select \[ ok ] create a code signing project perform the following steps to 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 ] create an environment perform the following steps to 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 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 once it is approved approve the project perform the following steps to 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 ] go back to the project, and in the environments tab, you should see a certificate & key in hardware (such as the {{ch}} )