question on Remote Desktop Services Security

Question about Remote Desktop Security. Please read it carefully before answering quick and half answers. Thank you.

1. When you have a Server 2008 R2 (standard installation) with Remote Desktop enabled, what is the security risk of making it publically accessible over the internet? Should you never do that or is the security risk limited? I know there have been removed a lot of vulnerabilities in the RDP protocol but I'm not sure what the status is today.

2. If you DO enable it are there any special things you should pay attention to?

4. Is it more advisable to only make the RDweb interface publically available or is that imposing the same security risk?

Thanks for any help in advance.
Stephans2Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Lester_ClaytonConnect With a Mentor Commented:
Yes, there is always a risk, but if you make it so that only network level authentication is allowed, then it's less of a risk.  This means that you have to authenticate to the sever before you can establish the RDP session.  It's as secure as SSL on an FTP server, so unless somebody tries to brute force you, you are probably fine.

RDWeb is also fine to make publicly available.  People will connect to the RDweb using SSL, and only after they are successful, can they launch the .RDP file which will connect them to the session.  Lots of companies use the standard security.

Two tips I can give you however,

If you're using RDWeb, then you might as well also use RD Gateway - RD Gateway will allow you to tunnel RDP sessions through your SSL enabled web server.  You can also impose a lot more security on RD Gateway than you can on a standard RDP session.  It's a bit more complex to set up, but there are many guides available on the net for that.

Another tip is to change the default port for RDP - you can make it so that you either

Make your servers listen on the different port or
Make it so that your Nat router forwards the external port of choosing to the internal port 3389.

To change the port number, open the registry and change the value for HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber to be your new port number.

Be careful that you don't specify a hex value and think it's a decimal value :)
0
 
jrgcomputingCommented:
There is a risk with making a RDP available over the Web. A lot depends on your password policy and how strong your user accounts are.

A safer way would be to set up VPN on demand and use VPN to establish a connection to the local network and then initiate the RDP from there.
0
 
Stephans2Author Commented:
Thank you Lester for your excellent answer.
0
 
TolomirAdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.