Ensure RDS database master credentials are stored in Secrets Manager
RDS master credentials should be managed by AWS Secrets Manager with automatic rotation.
Security Impact
Manually managed credentials are harder to rotate and may be stored insecurely.
How to Remediate
Use RDS Secrets Manager integration when creating databases, or configure Secrets Manager rotation for existing credentials.
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 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, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-rds-22
- Service
- Relational Database Service (RDS)
- Category
- Credential Management
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Relational Database Service (RDS) Checks
View all checksEnsure RDS instances are not publicly accessible
Ensure RDS instances have encryption at rest enabled
Ensure RDS instances use KMS customer managed keys
Ensure RDS instances have automated backups enabled
Ensure RDS backup retention is at least 7 days