Configure Venafi TPP to integrate with the KMES Series 3

this section describes the following tasks for integrating venafi tpp (trust protection platform) with the {{k3}} for data encryption, key generation, and key storage create an hsm connector and generate an hsm protected encryption key enable venafi advanced key protect set up hsm private key generation configure code signing create a connector and 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 select \[ ok ] in the create new hsm (cryptoki) connector window, enter any name for the hsm connector in the name field 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 {{k3}} for pin , enter the password for the identity configured in the {{futurex}} pkcs #11 file select \[ verify ] if the connection to the {{k3}} is successful, a new permitted keys section populates in the window select \[ new key ] in the create new hsm key window, enter a key name and select the type for the key select allow key storage checkbox if you plan to use venafi codesign protect to store private code signing keys in the {{k3}} select \[ create ] if key creation is successful, the key is now viewable in the keys menu on the {{k3}} the name of the key displays in the list of permitted key in the create new hsm key window select \[ create ] to save and close the window enable venafi advanced key protect venafi advanced key protect is required for hsm private key generation in addition, venafi code signing certificate private key storage requires you to enable this 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 enable venafi advanced key protect window, and select \[ enable ] to proceed restart the iis service select the product node, select website , and then select \[ restart ] in the actions panel restart the venafi platform service select the product node, select venafi platform , then select \[ restart ] in the actions panel restart the logging service select the product node, select logging , then select \[ restart ] in the actions panel set up hsm private key generation venafi tpp uses the {{k3}} for private key generation for ssh keys and certificates venafi tpp uses certificate authority (ca) template objects to manage the certificate lifecycle creating one is a prerequisite to hsm key generation see venafi documentation for more information perform the following tasks to configure hsm private key generation settings configure the venafi platform policy generate the certificate configure the policy perform the following steps to configure the venafi platform policy to enable the {{k3}} for hsm key generation log in to the admin console https //\[ip address of venafi tpp]/vedadmin select the 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 {{k3}} in the key generation drop down menu under other information , select the name of the hsm protected encryption key you created on the {{k3}} select \[ save ] at the bottom of the page to finish 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 of the page, select \[ add ] under the policy drop down list 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 display in the window if you selected provisioning for management type , associate the certificate with the intended application object configure code signing venafi codesign protect can store private code signing keys in the {{k3}} this section describes the basic steps to configure this functionality for the integration see venafi documentation for more details to take advantage of the codesign project, you must create a ca template object, which venafi tpp uses to manage the certificate lifecycle see venafi documentation for more information to use an hsm for key storage, you must first complete the steps in the set up hsm private key generation section 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 and grant that user 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 a 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 ] on the settings tab of the properties window, enter a description and select a certificate container and signing flow open the certificate authority tab, select a ca template , and select \[ add ] on the keys tab, select which key sizes to allow for rsa and elliptic curve keys on the key storage tab, select the futurex hsm connector and select \[ add ] enter any optional information in the remaining tabs and select \[ ok ] create a new 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 in 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 approval 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 ] navigate back to the project, and under the environments tab you should see that a certificate & key were created in hardware (i e , the {{k3}} )