Prerequisites
Please ensure the following requirements are met on the machine with a fully operational Versasec vSEC:CMS.
- Securosys PKCS#11 Provider v1.8.6 or newer, requires Visual C++ Redistributable Packages for Visual Studio 2015
- CloudHSM partition (HSM as a Service) or Primus HSM, firmware v2.8.21 or newer with PKCS#11 API enabled.
1. Versasec vSEC:CMS
A fully operational and licensed Versasec vSEC:CMS is required for this document. Installing and configuring the Versasec vSEC:CMS is not part of this document.
Refer to Versasec - vSEC:CMS Documentation on how to install and configure the Versasec vSEC:CMS.
2. HSM User Configuration
To allow all vSEC:CMS master keys to be copied to the HSM it is necessary to change the Security Configuration of the User Partition to allow the user to import the keys into the Primus HSM, instead of exclusively generating them on the HSM.
To change the Key Import Security Parameter to YES for the User Configuration, please refer to
the Primus HSM User Guide.
Your CloudHSM partition comes preconfigured and does not require any additional configuration (subject to subscription).
3. HSM Setup and Configuration
- Cloud
- On-premises
Securosys CloudHSM allows almost instant HSM operation by selecting and contracting the different services and options. For available service packages and options consult our website Securosys CloudHSM Service and contact Securosys sales.
Ensure the PKCS#11 API is included and activated in your subscription.
For general on-premises Primus HSM hardware, HA Cluster setup and operation in FIPS or Common Criteria certified modes, refer to the corresponding Primus HSM User Guide for details.
Ensure the PKCS#11 API is licensed and activated on your HSM device.