QuestionQ59

VerifiedData Protection

A company wants to store every object containing sensitive data in an Amazon S3 bucket. The company will use server-side encryption to encrypt the S3 bucket. The company’s operations team manages access to the company’s S3 buckets. The company’s security team manages access to encryption keys.

The company wants to separate the teams’ duties so that a configuration error by only one team cannot compromise the data by granting unauthorized access to plaintext data.

Which solution meets this requirement?

Explanation

SSE-KMS with a customer managed KMS key provides independent authorization controls for object access and key use. Retrieving an SSE-KMS-encrypted S3 object requires access to the object and kms:Decrypt permission on the KMS key. A bucket policy can require SSE-KMS, while a KMS key policy separately limits decryption permissions; therefore, a misconfiguration in only one control plane cannot by itself grant plaintext access. SSE-S3 does not provide a customer-managed KMS key policy, and SSE-C requires customers to provide the key with each request rather than storing it in AWS KMS.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!