Skip to Content

Forcing RDP to use TLS Encryption

How to force RDP to use TLS Encryption?


Overview: This article provides instructions on how to force Remote Desktop Protocol (RDP) to use TLS encryption.


rd1

Windows Remote Desktop Protocol (RDP) is widely used by system administrators to provide remote operators access to internal systems and servers. In a shocking oversight, this connection does not use strong encryption by default. To force RDP to use TLS Encryption follow below steps

Step 1: Open the Root console

Open the search bar and type "mmc" or run mmc.exe from the Run application. Select the top application, which will open the system console.

rd2

Step 2: Open the Group Policy Editor Snap-in

Open File -> Add/Remove Snap-in and select Global Policy Editor.

rd3

Step 3: Select "Group Policy Editor" and click on "Add"  the selected snap-in.

Step 4: Select the "Local Computer",  this should  be the default and select "Finish" > "Ok"

 

Step 5: Navigate to the RDP Session Security Policies

In the sidebar Navigate to Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services --> Remote Desktop Session Hosts -> Security. Then select "Set client encryption level" and edit that policy.

rd7

Step 6: Require the Highest native Encryption possible

Edit the "Set client encryption level policy".

rd7

Step 7: A better idea -> Force TLS instead

Edit the "Require use of specific security layer for remote (RDP) connections" policy.

rd9