HSM Integration
Typically MPC is seen as an replacement for the traditional HSMs, but sometimes it is beneficial to have both. There are different aspects of the Builder Vault, where an HSM may help satisfy requirements for the solution.
Protecting Data at Rest
When keys are not used, they need to protected - also know as protecting the data at rest. Builder Vault supports this by allowing customers to configure an encryption layer that is used to protect the data that is stored in the database.
The plugin allows to customers to design their own protection that uses just the sort of protections that they require in their system to support company requirements. This protection is done in addition to any protection that is already done in Builder Vault.
Technical examples of how to implement this plugin is described here: custom-encryption-plugin.
Using Enclaves on Phones
While not an HSMs, Secure Enclaves on mobile phones play an important part in protecting keys and other valuable information on mobile phones. Builder Vault allows the calling application to supply an external encryption engine that is based on a secure enclave when running embedded nodes on a Mobile Phone. The general mobile phone set up is documented here: mobile-nodes.
Note that this encryption replaces all encryption done by Builder Vault, so all data must be encrypted, when using this, to be secured while stored on the phone.
Supplying HSM Generated Entropy
In general modern processors have been improved to generate strong entropy when asked for it, but sometimes there is a requirement that entropy must be generated by a certified HSM. In cases like this Builder Vault can be configured to read randomness from an external named pipe.
This allows customers to create a named pipe based on any source of randomness that they like, and supply that to Builder Vault. Technical examples of how to do this using a PKCS #11 compliant HSM are described here: external-random-source.
Updated about 7 hours ago
