An organization wants to enforce encryption at rest for all S3 buckets using AWS Organizations. Which TWO actions should the security team perform to ensure consistent governance?
Trap 1: Enable S3 Block Public Access on all accounts via AWS Organizations.
While enabling S3 Block Public Access is a critical security best practice, it does not enforce encryption at rest. This configuration prevents data leaks to the public internet but does not influence or mandate the encryption status of the objects stored within the S3 buckets.
Trap 2: Use AWS Trusted Advisor to manually audit all buckets for…
Manual auditing via Trusted Advisor is a reactive measure and does not provide enforcement or governance. While it identifies buckets that are currently unencrypted, it does not prevent future occurrences, making it insufficient for an organization-wide mandate requiring strict, automated compliance for all data stored.
Trap 3: Apply a bucket policy to every S3 bucket in the account.
Applying individual bucket policies is operationally expensive and prone to human error, especially in large environments. Governance should be applied at the organizational level using SCPs rather than managing individual resource policies, which can be modified or deleted by users with sufficient IAM permissions.
- A
Create an SCP that denies s3:PutObject if x-amz-server-side-encryption is not present.
This SCP effectively prevents any user or service from uploading data to S3 without specifying server-side encryption. By denying the write action at the account boundary level, you ensure that even if a bucket policy is missing, the data cannot be stored in an unencrypted state.
- B
Enable S3 Block Public Access on all accounts via AWS Organizations.
Why it fails: While enabling S3 Block Public Access is a critical security best practice, it does not enforce encryption at rest. This configuration prevents data leaks to the public internet but does not influence or mandate the encryption status of the objects stored within the S3 buckets.
- C
Deploy an SCP that denies s3:CreateBucket unless the request includes default encryption configuration.
This policy ensures that developers cannot create buckets that lack encryption settings at the time of creation. By controlling the creation process, the security team enforces a 'secure by default' posture across the entire organization, preventing non-compliant infrastructure from ever existing within the environment.
- D
Use AWS Trusted Advisor to manually audit all buckets for encryption status.
Why it fails: Manual auditing via Trusted Advisor is a reactive measure and does not provide enforcement or governance. While it identifies buckets that are currently unencrypted, it does not prevent future occurrences, making it insufficient for an organization-wide mandate requiring strict, automated compliance for all data stored.
- E
Apply a bucket policy to every S3 bucket in the account.
Why it fails: Applying individual bucket policies is operationally expensive and prone to human error, especially in large environments. Governance should be applied at the organizational level using SCPs rather than managing individual resource policies, which can be modified or deleted by users with sufficient IAM permissions.