Generic
Generic KMIP
1 min
the generic kmip service template enables you to deploy {{ch}} with third party applications that support integration with a key management device through kmip but have not yet been officially tested and added to the {{ch}} service management store contact the {{futurex}} support team if you would like to request support for a specific third party application to be added to {{ch}} our dedicated integration engineering team uses the following process to test and document the integration futurex certification process the {{futurex}} certification process is a rigorous and standardized approach to testing and certifying integrations between third party applications and {{futurex}} hsms and key management servers (such as {{k3}} ) the certification process ensures that we fully test and validate third party application integrations in a lab environment before deploying them in a production environment our integration engineering team implements this process so you can be confident that third party applications integrate seamlessly with our hsms and {{k3}} devices, and that all operations result in the expected behavior the certification process involves research, testing, troubleshooting, and certification and is fully documented in individual integration guides by using the following process research the third party application to understand the solution and the protocol it uses to integrate with an hsm or kms device (such as pkcs #11, microsoft cng, jce, openssl engine, or kmip) determine how the third party application uses the hsm or kms device, including its specific functionalities (such as data encryption, key protection, entropy, and so on) install and configure the third party application in a lab environment, where all testing and validation occur establish a connection between the third party application and the {{futurex}} device, which typically involves configuring tls certificates and creating roles and identities that the third party application uses to connect and authenticate to the {{futurex}} device initiate a request from the third party application to the {{futurex}} device, such as generating keys or certificates, encrypting or decrypting data, or other cryptographic functions if errors occur during testing, the integration engineering team diagnoses the issues and takes corrective actions if necessary, the team also documents the errors by creating engineering change requests (ecrs) to ensure all issues are addressed and resolved before certification after making any necessary engineering changes, they perform a new end to end test to ensure that all errors are resolved and that all operations are successful certify the integration by creating an integration guide that covers all necessary prerequisites, configurations required in both the third party application and the {{futurex}} device, and the steps to test the functionality following these steps helps ensure that the integration between the third party application and the {{futurex}} device is ready for use