GSEC · Question #379
Which of the following is NOT a recommended best practice for securing Terminal Services and Remote Desktop?
The correct answer is B. Make sure to allow all TCP 3389 traffic through the external firewall. Allowing all TCP 3389 traffic through the external firewall is a security vulnerability, not a best practice, as it exposes RDP to the public internet.
Question
Which of the following is NOT a recommended best practice for securing Terminal Services and Remote Desktop?
Options
- ARequire TLS authentication and data encryption whenever possible.
- BMake sure to allow all TCP 3389 traffic through the external firewall.
- CGroup Policy should be used to lock down the virtual desktops of thin-client users.
- DConsider using IPSec or a VPN in addition to the RDP encryption if you are concerned about
How the community answered
(37 responses)- A5% (2)
- B70% (26)
- C8% (3)
- D16% (6)
Why each option
Allowing all TCP 3389 traffic through the external firewall is a security vulnerability, not a best practice, as it exposes RDP to the public internet.
Requiring TLS authentication and encryption is a well-established best practice that protects RDP sessions from eavesdropping and man-in-the-middle attacks.
Exposing TCP port 3389 (RDP) on the external firewall to all traffic makes the Terminal Services endpoint directly reachable from the internet, dramatically increasing the attack surface for brute-force, credential stuffing, and exploit attacks such as BlueKeep. Best practice is to restrict RDP access to trusted IP ranges, place it behind a VPN or RD Gateway, and never expose it openly on the external firewall.
Using Group Policy to lock down virtual desktops of thin-client users limits the attack surface within sessions, which is a recognized hardening measure.
Layering IPSec or a VPN over RDP encryption provides defense-in-depth for sensitive environments, which is a recommended security practice.
Concept tested: Remote Desktop Protocol (RDP) firewall hardening best practices
Source: https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/harden-remote-desktop-server
Topics
Community Discussion
No community discussion yet for this question.