Ensure CloudWatch log groups are encrypted with KMS
CloudWatch log groups should be encrypted using customer managed KMS keys for sensitive logs.
Security Impact
Default encryption uses AWS managed keys which lack fine-grained access control.
How to Remediate
Associate a KMS key with log groups: aws logs associate-kms-key --log-group-name LOG_GROUP --kms-key-id KEY_ARN
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 Amazon CloudWatch 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-cloudwatch-2
- Service
- Amazon CloudWatch
- Category
- Encryption
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon CloudWatch Checks
View all checksEnsure CloudWatch log groups have retention configured
Ensure CloudWatch Alarms exist for root account usage
Ensure CloudWatch Alarms exist for unauthorized API calls
Ensure CloudWatch Alarms have SNS notifications configured
Ensure CloudWatch cross-account sharing is properly configured