This rule requires enabling default encryption with KMS for S3 buckets.
Rule | S3 bucket default encryption should be enabled with KMS |
Framework | HIPAA |
Severity | ✔ Medium |
Rule Description:
S3 bucket default encryption should be enabled with Key Management Service (KMS) for HIPAA compliance. This rule ensures that all objects stored in the S3 bucket are automatically encrypted using KMS, which helps to protect sensitive data and meet the encryption requirements specified by the Health Insurance Portability and Accountability Act (HIPAA).
Troubleshooting Steps:
If default encryption with KMS is not enabled for the S3 bucket, you may encounter the following issues:
Necessary Codes:
aws s3api put-bucket-encryption --bucket bucket-name --server-side-encryption-configuration '{"Rules": [{"ApplyServerSideEncryptionByDefault": {"SSEAlgorithm": "aws:kms"}}]}'
Note: Replace
bucket-name
with the name of your S3 bucket.Step-by-Step Guide for Remediation:
CLI Command for Remediation:
bucket-name
with the name of your S3 bucket:aws s3api put-bucket-encryption --bucket bucket-name --server-side-encryption-configuration '{"Rules": [{"ApplyServerSideEncryptionByDefault": {"SSEAlgorithm": "aws:kms"}}]}'
Note:
Enabling default encryption with KMS for an existing S3 bucket may result in the re-encryption of existing objects. Please consider this while implementing the remediation steps.
By ensuring default encryption with KMS for S3 buckets as per HIPAA requirements, you can maintain compliance with data encryption standards and protect sensitive data from unauthorized access.