Ensure KMS keys are used for S3 bucket encryption
S3 buckets containing sensitive data should use SSE-KMS with customer managed keys.
Security Impact
SSE-S3 and AWS managed KMS keys lack the access control and auditing of customer managed keys.
How to Remediate
Configure S3 bucket default encryption to use SSE-KMS with a customer managed key.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Key Management Service (KMS) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, HIPAA compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-kms-6
- Service
- Key Management Service (KMS)
- Category
- Encryption
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial