MEDIUM

Ensure RDS instances use KMS customer managed keys

RDS encryption should use customer managed KMS keys for additional control over key policies and rotation.

Security Impact

AWS managed keys lack fine-grained access control and custom rotation schedules.

How to Remediate

Create a customer managed KMS key and specify it when enabling encryption on RDS instances.

Affected Resources

AWS::RDS::DBInstanceAWS::KMS::Key

Compliance Frameworks

SOC 2PCI-DSSHIPAAFedRAMP

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 Relational Database Service (RDS) 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-rds-3
Service
Relational Database Service (RDS)
Category
Encryption
Severity
MEDIUM

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related Relational Database Service (RDS) Checks

View all checks
aws-rds-1critical

Ensure RDS instances are not publicly accessible

aws-rds-2high

Ensure RDS instances have encryption at rest enabled

aws-rds-4high

Ensure RDS instances have automated backups enabled

aws-rds-5medium

Ensure RDS backup retention is at least 7 days

aws-rds-6medium

Ensure RDS instances have Multi-AZ enabled