To enhance the security of your publicly accessible Amazon RDS databases, it is recommended to change the endpoint ports of your RDS instances from their default values. Running your database instances on default ports increases the risk of dictionary and brute force attacks. By moving the RDS instances ports to non-default values, an extra layer of protection is added. Therefore, it is important to ensure that your RDS instances are not utilizing the default endpoint port 5432 (PostgreSQL) and to implement port obfuscation as an additional security measure.
To ensure that Amazon RDS is not using the default port 5432, you can take the following remediation steps:
- Connect to the RDS instance using the AWS Management Console, the AWS CLI, or a third-party client tool.
- Check the current port setting for the instance. You can do this by looking at the endpoint information for the instance, which includes the host name and port number.
- If the instance is using the default port, you can modify the port number by modifying the instance settings. In the AWS Management Console, go to the "Configuration" tab for the instance, and look for the "Network & Security" section. Here, you can modify the port number.
- Select a port number that is not commonly used, to avoid conflicts with other applications. You can choose any available port number between 1024 and 65535.
- Save the changes to the instance settings and wait for the changes to take effect. It may take a few minutes for the changes to propagate to all the nodes in the RDS cluster.
- Once the changes are complete, verify that the RDS instance is no longer using the default port by connecting to it using the new port number.
- Update any applications or scripts that rely on connecting to the RDS instance to use the new port number.
- Test the connectivity to the RDS instance from all relevant systems to ensure that the changes have been properly implemented and there are no issues with the new port number.
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.