Where this offering fits
Entrust HSM selection concerns protected cryptographic key operations for a defined application. Review the required key types, interfaces and assurance evidence before comparing form factors or performance. The selected configuration must fit both the consuming software and the organisation’s custody model; a general portfolio claim is insufficient for procurement approval.
Architecture and rollout decisions
Map signing, encryption or other required operations to supported interfaces and versions. Define administrator roles, key generation, backup and recovery. A non-production evaluation should show the application using protected keys and responding appropriately when the cryptographic service is unavailable. Include replacement and maintenance procedures in the design so security does not depend on a single undocumented administrator or device.
An evaluation scenario for this offering
Run the required operation from a non-production application using test keys held under the proposed custody model. Review who can initialise the device, manage keys and recover access. Exercise the documented service response to a lost HSM connection. The customer should be able to relate the observed result to the exact model, firmware and interface, avoiding an assumption that a certificate or benchmark for a different configuration proves suitability for this application.
Evidence to request for this scope
- Obtain exact model, firmware and relevant certification documentation for the offered configuration.
- Demonstrate application integration using test keys and the intended authentication method.
- Record operator participation and protected recovery procedures without exporting secrets into ordinary project files.