Ensure Redshift clusters use AWS Secrets Manager for credential rotation
Storing master credentials in Secrets Manager enables automatic rotation and centralizes credential management.
Security Impact
Hard-coded or static credentials increase risk of unauthorized access if credentials are compromised.
How to Remediate
Store Redshift master credentials in Secrets Manager. Enable automatic rotation with appropriate rotation schedules.
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 Amazon Redshift 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, NIST 800-53, Best Practices compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-redshift-19
- Service
- Amazon Redshift
- Category
- Credential Management
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon Redshift Checks
View all checksEnsure Redshift clusters are not publicly accessible
Ensure Redshift clusters have encryption at rest enabled
Ensure Redshift clusters have encryption in transit enabled
Ensure Redshift clusters have audit logging enabled
Ensure Redshift clusters have automated snapshots configured