A pharmaceutical research firm must encrypt clinical trial data stored in Amazon S3. The firm's compliance policy mandates that encryption keys must be generated and stored on dedicated, single-tenant hardware security modules (HSMs) directly controlled by the firm's security team. However, the firm still wants to leverage the automated, seamless server-side encryption features of Amazon S3 without custom application-side coding. Which of the following approaches meets these requirements?
- Configure AWS Key Management Service (KMS) with a custom key store backed by an AWS CloudHSM cluster, and use those keys for S3 server-side encryption (SSE-KMS).Cevap
- BEncrypt the data on the client side using the AWS CloudHSM client software before uploading it to Amazon S3.
- CUse AWS Key Management Service (KMS) with default AWS managed keys (SSE-KMS), and configure AWS CloudTrail to copy the keys to a CloudHSM cluster for single-tenant backup.
- DEnable Amazon S3 server-side encryption with customer-provided keys (SSE-C) and have AWS automatically manage the lifecycle of the keys inside AWS KMS.
Cevap
Configure AWS Key Management Service (KMS) with a custom key store backed by an AWS CloudHSM cluster, and use those keys for S3 server-side encryption (SSE-KMS).
The correct approach is to configure AWS Key Management Service (KMS) with a custom key store backed by an AWS CloudHSM cluster, and use those keys for S3 server-side encryption (SSE-KMS). This allows the customer to maintain sole ownership and control of the keys in a dedicated, single-tenant HSM cluster (AWS CloudHSM) while still allowing Amazon S3 to perform transparent server-side encryption via KMS integrations.
Adım Adım Çözüm
Anahtar Kavram
AWS KMS Custom Key Stores