Ensure Redshift clusters are not using default master username
Default master username 'awsuser' is well-known and commonly targeted in brute-force attacks. Custom usernames add a layer of obscurity.
Security Impact
Default usernames are commonly targeted in automated attacks, increasing the risk of unauthorized access.
How to Remediate
Use a custom master username when creating Redshift clusters instead of accepting the default 'awsuser'.
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 Security Best Practices compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-redshift-7
- Service
- Amazon Redshift
- Category
- Access Control
- 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