Ensure that your AWS Redshift database clusters are using custom master user names instead of the default master user name (i.e. "awsuser") in order to add an additional layer of defense against non-targeted attacks.
Changing the default master user name for Redshift database clusters represents a basic security measure, therefore it will improve the overall security, however, this measure does not fully protect against attackers that can guess or obtain the database user names using social engineering techniques. To implement advanced Redshift database security, you should restrict the root account only to privileged users, use strong and complex passwords and grant permissions to trusted users only at the database level.
This rule can help you with the following compliance standards:
This rule can help you work with the AWS Well-Architected Framework
This rule resolution is part of the Cloud Conformity Security & Compliance tool for AWS
Using the default master user name to access your Redshift database clusters represent a potential security concern. Changing the master user name ("awsuser") will add an extra layer of security, protecting your publicly accessible Amazon Redshift clusters against hacking.
To determine if your existing Redshift database clusters are using the default master user name, perform the following:
Remediation / Resolution
To change the default master user name for your existing Amazon Redshift database clusters, you must relaunch those clusters with a different master user name and migrate the existing data to the new clusters. To launch the new Redshift database clusters and move the existing data between databases, perform the following:
Unlock the Remediation Steps
Free 30-day Trial
Automatically audit your configurations with Conformity
and gain access to our cloud security platform.
You are auditing:
Redshift Cluster Default Master Username
Risk level: Low