Ensure KMS keys are used for EBS encryption
EBS volumes should be encrypted with customer managed KMS keys instead of default aws/ebs keys.
Security Impact
AWS managed keys lack fine-grained access control through key policies.
How to Remediate
Configure EBS default encryption to use a customer managed key. Create new volumes with CMK encryption.
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-4
- 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