Ensure there is no unrestricted inbound access to TCP port 3389 (RDP)

Security & Compliance

TCP port 3389 is used for Remote Desktop Protocol (RDP), a proprietary protocol developed by Microsoft that allows users to connect to a remote computer over a network connection. If this port is open and accessible to the internet without any restrictions, it can be a major security vulnerability as attackers can exploit it to gain unauthorized access to your system.


Here are the steps to remediate the issue of unrestricted inbound access to TCP port 3389 (RDP):

  1. Identify open ports: Identify any open TCP ports in your security groups or network access control lists (ACLs) that allow inbound traffic to port 3389 (RDP).
  2. Restrict access: Restrict access to TCP port 3389 (RDP) by modifying the security group rules and network ACLs to allow inbound traffic only from trusted sources. This can be done by adding specific IP addresses or IP address ranges to the allowed list.
  3. Implement additional security measures: Implement additional security measures such as two-factor authentication and encryption to strengthen the security of RDP connections.
  4. Test and validate: Test your new security group rules and network ACLs to ensure that they are functioning as expected and that only authorized sources are able to access port 3389 (RDP).
  5. Monitor and update: Regularly monitor your security group rules and network ACLs for changes and update them as needed to ensure that your systems are always protected against unauthorized access through TCP port 3389 (RDP).

By following these remediation steps, you can help to ensure that there is no unrestricted inbound access to TCP port 3389 (RDP), which can help to prevent security breaches and protect your sensitive data.

Enforced Resources
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.