What "TLS encryption" means for an RDP session

When people say RDP is encrypted, they usually mean the session negotiated Transport Layer Security — the same family of cryptography that protects HTTPS websites. In a TLS-secured RDP session, the client and server first agree on encryption parameters and verify identity (via a certificate), then wrap all subsequent traffic — your typed passwords, the pixels of your desktop, clipboard contents, redirected files — in that encrypted channel. Someone capturing packets on the path between you and the server sees volume and timing, but not content.

That "when configured correctly" qualifier does real work, though. RDP's protocol history includes older, weaker options, and servers can be set to negotiate — meaning client and server pick the strongest method they share. Negotiation is convenient, but it also means a single weak setting on either side can drag the whole session down. Understanding the layers is what lets you lock the good one in.

Client your device Server RDP host 1. Agree on TLS 2. Verify certificate 3. Encrypted channel session traffic sealed Eavesdropper sees only scrambled traffic
Fig. 1 — The TLS handshake: agree, verify identity, then seal the session.

The three RDP security layers, ranked

Windows lets the server choose its security layer, and the names are confusingly similar. Here they are in plain terms, from weakest to strongest. RDP Security Layer is the legacy option: encryption is negotiated within the RDP protocol itself, using older cryptography. It exists for compatibility with ancient clients and should not be chosen on any modern server.

Negotiate is the default on most servers: client and server agree on the strongest layer both support, which in practice means TLS whenever both sides are modern. It is fine as long as every client you use is current — but "negotiate" leaves the door ajar for a downgrade if something old ever connects. SSL (TLS 1.0+) — labeled "SSL" for historical reasons — forces TLS and refuses anything weaker. For a server you control, forcing TLS is the correct setting; there is no modern client that cannot speak it.

Security layerWhat it doesVerdict
RDP Security LayerLegacy in-protocol encryption with older cryptographyAvoid — kept only for ancient clients
NegotiateClient and server pick the strongest layer both support (TLS in practice)Acceptable default if all clients are modern
SSL (TLS 1.0+)Requires TLS; refuses weaker methods outrightBest choice — enforce this on servers you control

Where Network Level Authentication fits in

NLA is often mentioned alongside encryption, but it solves a different problem. Encryption protects the content of your session; NLA protects the start of it. With NLA required, the connecting user must authenticate before the server spins up a full session — which shuts down entire classes of pre-authentication attacks and resource-exhaustion tricks that target the logon screen itself.

The two are companions, not alternatives. A session can be TLS-encrypted but still accept unauthenticated connections up to the logon prompt (wasteful and riskier), or NLA-protected but negotiating a weak layer (authenticated but snooped). The hardened configuration is both: force the TLS layer and require NLA. One checkbox-class setting each, and together they close the two most common protocol-level weaknesses.

Certificates: the identity check inside TLS

TLS does two jobs — secrecy and identity — and the certificate handles identity. When your client connects, the server presents a certificate saying "I am this machine"; your client checks it before trusting the encrypted channel. Windows servers generate a self-signed certificate automatically, which encrypts fine but triggers the familiar "the identity of the remote computer cannot be verified" warning, because nothing vouches for the certificate itself.

For a personal server, the practical approach is certificate pinning by habit: on first connect, carefully verify the certificate thumbprint through a trusted channel (your hosting provider's console or welcome email), then let your client remember it. If the warning ever reappears unexpectedly, stop — a changed certificate can mean the server was rebuilt, or it can mean someone is intercepting you. For teams, a certificate from your internal CA or a public CA removes the warning entirely and makes unexpected changes auditable. Either way, the rule is simple: a certificate warning you did not expect is a reason to pause, not to click through.

Client checks the badge Server presents certificate ID badge ✓ Unexpected certificate warning? Stop and verify — don't click through.
Fig. 2 — The certificate is the server's ID badge. Verify it once, then watch for unexpected changes.

Enforcing TLS + NLA: the actual steps

With full administrator access — standard on every RDP Temple plan — these take about five minutes in the Local Group Policy Editor or Remote Desktop Session Host Configuration. The settings live under Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Security.

  1. Require the TLS security layer. Set "Require use of specific security layer for remote (RDP) connections" to SSL (TLS 1.0). This refuses the legacy RDP Security Layer outright.
  2. Set the encryption level to High. Set "Set client connection encryption level" to High Level, which encrypts both directions with strong ciphers.
  3. Require Network Level Authentication. Set "Require user authentication for remote connections by using Network Level Authentication" to Enabled.
  4. Apply and restart the Remote Desktop Services service (or reboot during a maintenance window) so the new layer takes effect for new connections.
  5. Reconnect and confirm. Open a fresh RDP session — not a reconnected one — and check the connection bar / client details to confirm the session reports strong encryption.
  6. Verify the certificate thumbprint on first connect against the value shown in your hosting console or welcome materials, then allow the client to remember it.
  7. Test from each client you use. Confirm your Windows, Mac, Android, and iOS clients all still connect — anything ancient enough to fail here needed replacing anyway.
  8. Document the setting. Note what you changed and where, so a future rebuild or migration reproduces it instead of silently reverting to Negotiate.

How to verify encryption is really on

Configuration is a claim; verification is proof. The quickest check is on the client side: in the Microsoft Remote Desktop client, an established session's connection information shows the security/encryption in use. If it reports anything other than strong TLS-level encryption after your change, something — a Group Policy override, a cached setting — is fighting you.

The stronger test is a packet capture: run a sniffer on your own machine while connected, filter for the server's IP, and confirm the RDP traffic is opaque — no readable keystrokes, window titles, or file names. Readable plaintext in a capture means the session negotiated down, and you should revisit the security-layer setting. Do this test once after hardening, and again after any major Windows upgrade, since feature updates occasionally reset security policies to defaults.

Gotchas that silently weaken encryption

  • Group Policy vs local policy conflicts. A domain or hosting-template GPO can override your local settings. If your change does not seem to stick, check resultant policy (gpresult) for a higher-precedence rule.
  • Old saved .rdp files. A saved connection file can carry its own security settings. After hardening the server, recreate or update saved .rdp files rather than trusting old ones.
  • Feature updates resetting policies. Major Windows upgrades sometimes restore defaults. Re-verify the TLS layer and NLA after each feature update, not just after initial setup.
  • Clicking through certificate warnings by habit. Every unexamined "yes" trains you to ignore the one warning that matters. Verify thumbprints deliberately, once, then let the client remember.
  • Assuming encryption equals authentication. TLS without NLA still lets anyone reach the logon screen; NLA without TLS still exposes session content. You need both, as this guide's steps enforce.

The 5-minute version: force the SSL (TLS) security layer, set encryption to High, require NLA, verify the certificate thumbprint once, and confirm with a fresh connection. Those four moves take minutes and eliminate the entire category of "session negotiated down to something weak" problems. For the rest of the hardening picture, see our RDP security best practices.

Ready for your own RDP server?

Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.

Shared Servers$6/mo
Dedicated Server$165/mo
Get Started

3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA

RDP TLS Encryption: FAQ

Usually, but not always strongly. Modern Windows servers negotiate TLS encryption by default, which is good — but the "Negotiate" security layer can fall back to weaker methods if an old client connects, and NLA may not be required. The safe move is to explicitly force the SSL (TLS) security layer and require NLA, rather than trusting defaults.

TLS encrypts the content of your session so eavesdroppers cannot read it; NLA requires authentication before a full session is even created, which blocks pre-authentication attacks. They solve different problems and you want both: force the TLS security layer and require Network Level Authentication in policy.

Because the server presented a self-signed certificate that no trusted authority vouches for. The encryption itself still works, but you should verify the certificate thumbprint through a trusted channel the first time — your hosting console or welcome email — and treat any unexpected reappearance of the warning as a reason to stop and investigate.

Not the content, if TLS is properly enforced — the traffic is encrypted. But public Wi-Fi is still hostile territory for other reasons (captive portals, DNS tricks), so combining RDP with a VPN on untrusted networks remains wise. And none of this helps if the password is weak: encryption protects the pipe, not the credentials.

Check the established session's connection information in your Remote Desktop client, which reports the security layer in use. For stronger proof, capture packets on your own machine during a session and confirm the RDP traffic is opaque — readable keystrokes or window titles in the capture mean the session negotiated down.

Negligibly on modern hardware. The handshake adds a fraction of a second at connect time, and bulk encryption is hardware-accelerated on any recent CPU. If a session feels slow, the cause is almost always network latency or bandwidth, not the encryption — check ping times before blaming TLS.