Ensure KMS keys are not exposed in CloudTrail logs
KMS operations in CloudTrail should not expose sensitive key material or plaintext data.
Security Impact
Exposed key material or plaintext in logs can be accessed by anyone with log access.
How to Remediate
Review CloudTrail logs for KMS operations. Ensure applications do not log plaintext data before 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-14
- Service
- Key Management Service (KMS)
- Category
- Logging
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial