Please describe the technical details for this pilot.<Enter here> Top-down scheme of interests/work areas: - Service needs and adoption path - Identifying (client) service-specific requirements, scenarios and usage patterns, in terms of use of the HSM platform and its supporting cryptoservice. Could extend towards actual implementation by some services
- Interoperability/usage layer - Access methods and interfaces to be used by the client services with mapping/path towards the fulfillment of service requirements; this layer allows or at least facilitates substitution of underlying solutions, if/when needed.
- HSM platform and its working environment (this could be split in two sub-items)
- Technical features, performance levels and direct interfaces offered by the platform, including the implementations of widely used specs and standards (such as PKCS#11 or KMIP) and platform specific operational functions like import/export of cryptographic materials, access to logs, health check, clear/reset.
- Associated operational procedures, their practicality and suitability for the environment where the platform is deployed, physical/electromagnetic security arrangement.
- Trustworthiness of the HSM platform - How one can attest that the offered platform is secure; preliminary audit/analysis/observations, supporting evidence, what is required or good to have/know, are there some recognised/possible weaknesses, open issues.
| 
