Ensure CloudTrail logs are encrypted with KMS
CloudTrail logs should be encrypted using AWS KMS customer managed keys for additional access control and auditability.
Security Impact
Unencrypted logs or logs encrypted with S3 SSE lack the access controls and audit trail provided by KMS.
How to Remediate
Configure CloudTrail to use a KMS key: aws cloudtrail update-trail --name TRAIL_NAME --kms-key-id KMS_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 AWS CloudTrail 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 CIS AWS v1.5.0, CIS AWS v2.0, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-cloudtrail-3
- Service
- AWS CloudTrail
- Category
- Encryption
- Severity
- HIGH
- CIS Benchmark
- 3.7
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS CloudTrail Checks
View all checksEnsure CloudTrail is enabled in all regions
Ensure CloudTrail log file validation is enabled
Ensure CloudTrail S3 bucket is not publicly accessible
Ensure CloudTrail logs are delivered to CloudWatch Logs
Ensure S3 bucket access logging is enabled for CloudTrail bucket