Ensure KMS key policies are not overly permissive
KMS key policies should not allow broad access. Avoid Principal:* without conditions.
Security Impact
Overly permissive key policies can allow unauthorized encryption/decryption of sensitive data.
How to Remediate
Review key policies and restrict principals to specific IAM roles, users, or AWS services. Add conditions where appropriate.
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-3
- Service
- Key Management Service (KMS)
- Category
- Access Control
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial