- Más nuevo
- Más votos
- Más comentarios
The guidance for securing the cluster signing key pertains to backups downloaded to a FIPS-validated on-premises HSM or token in your possession. This is a capability of the HSM which we have not yet released, but may in the future.
The backups we take today are not customer-downloadable backups. They can only be restored to authentic HSMs in the AWS cloud, in your account. You do not need to provide your cluster private key to authenticate these restores. A detailed description of encryption and restore of service-managed CloudHSM backups is at https://d1.awsstatic.com/whitepapers/Security/security-of-aws-cloudhsm-backups.pdf.
The private key is only needed when signing the certificate request (CSR) from the CloudHSM. Then you only need the public key to validate the certificate.
This scheme allows the client to check that it connects to the actual HSM and not an unauthorized intermediate (man-in-the-middle).
To some extent, the private key is not needed anymore.
Contenido relevante
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 2 años