Ensure KMS keys have descriptive aliases
KMS keys should have descriptive aliases to identify their purpose and associated resources.
Security Impact
Keys without aliases are difficult to identify and manage, leading to potential misuse.
How to Remediate
Create aliases for all customer managed keys following a naming convention: alias/project-environment-purpose.
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 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-kms-8
- Service
- Key Management Service (KMS)
- Category
- Governance
- Severity
- LOW
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free Trial