Skip to content
Home » RDP & Remote Access » What Is NLA (Network Level Authentication) and Why You Need It

What Is NLA (Network Level Authentication) and Why You Need It

Illustration showing Network Level Authentication (NLA) concept with a secure access door displaying “Access Denied,” server infrastructure, identity verification, and a secure connection screen against a cityscape background.

Network Level Authentication (NLA) is a Remote Desktop setting that makes anyone connecting to your Windows server prove a valid username and password before the server starts a session for them. Most business owners have never heard of it, it costs nothing, and it takes a minute to check. This post explains what NLA does, what it does not do, and how to switch it on.

What Is NLA in Simple Terms?

Think of your server as an office building. Without NLA, the server lets every visitor into the lobby, sits them at the reception desk and only then asks for ID. Each visitor uses a chair and some of the receptionist’s time, even if they have no business being there.

With NLA, ID is checked at the gate. The Remote Desktop client sends the user’s credentials first (Windows uses a protocol called CredSSP for this), and only if they are valid does the server create a session and show a desktop. That is the whole idea: authenticate first, then build the session.

Why Does This Matter?

The main reason is the code that runs before sign-in. Without NLA, anyone who connects gets a full Remote Desktop session with a sign-in screen, so any bug in that early stage can be attacked without a password. That is exactly how BlueKeep (CVE-2019-0708) worked: a worm-capable flaw that let attackers run code on unpatched older Windows versions, including Windows 7 and Server 2008 R2, just by connecting. CISA listed enabling NLA as a mitigation, because with NLA an attacker needs valid credentials first (CISA, 2019). Patching is still the real fix for such bugs; NLA is a second layer for the next one.

NLA also saves resources. Building a session for every anonymous connection uses memory and processor time, and floods of connections can slow a server down. With NLA, a connection without valid credentials is turned away early. And without NLA the sign-in screen can show the name of the last person who signed in, which hands an attacker a real username.

What NLA Does Not Do

Two common claims about NLA are wrong, and believing them leads to false comfort:

  • It does not hide your server. The NLA handshake itself still reveals the server’s computer name, its domain and its Windows build number to anyone who connects, without credentials. Free tools such as Nmap’s rdp-ntlm-info script read them in a second.
  • It does not stop password guessing. An attacker can send username and password pairs through NLA all day. Each wrong guess is logged as a failed sign-in (Event ID 4625, usually with Logon Type 3 when NLA is on), and a right guess gets them in. Against brute-force attacks you need long passwords, account lockout and, above all, Remote Desktop closed to the internet.

How to Check If NLA Is Enabled on Your Server

The menus have moved between Windows versions, so the quickest route is a command that works on all of them:

  1. Sign in to the server, press Windows + R, type SystemPropertiesRemote.exe and press Enter.
  2. On the Remote tab, under Remote Desktop, find the box “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)”.
  3. Make sure it is ticked, then click Apply.

To check from PowerShell, read the registry value; 1 means NLA is required, 0 means it is not:

Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication

To switch it on from PowerShell (as Administrator):

Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -Value 1

If the box is greyed out, a Group Policy is setting it. The policy is under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security > “Require user authentication for remote connections by using Network Level Authentication”. Set it to Enabled there.

What If My Remote Users Have Trouble Connecting?

Old computers are rarely the problem: NLA arrived with Remote Desktop 6.0 in Windows Vista and Server 2008, and even Windows XP SP3 clients can be set up to use it. The problems admins actually hit are these:

  • Expired passwords. With NLA on, a user whose password has expired, or who is set to “User must change password at next logon”, cannot sign in over Remote Desktop to change it, because the check happens before any session exists. Have them change it at the console or another session, or reset it for them. Do not switch NLA off to work around it.
  • CredSSP update mismatches. The error “An authentication error has occurred … This could be due to CredSSP encryption oracle remediation” means one side has the 2018 CredSSP security update and the other does not. The fix is to update the unpatched machine (Microsoft: CredSSP updates for CVE-2018-0886), not to weaken the setting.
  • Users not in the right group. A user who is not in Remote Desktop Users (or Administrators) is refused with a message that the account “is not authorized for remote login” whether NLA is on or off.

NLA Is One Layer

Turn NLA on, keep Windows patched, and then deal with the bigger issue: whether your Remote Desktop sign-in is reachable from the internet at all. Our guide on how to restrict RDP access safely covers the steps, including password length and lockout, and the RDP security guide puts everything in order. The strongest step is to close RDP to the internet; Prixl Guard Secure Access lets staff reach the server through an encrypted tunnel so you can do that without stopping work from home.

Prixl Warden‘s security audit checks whether NLA is required on your server, along with the other RDP and firewall settings, and on paid plans can switch it on from the Hardening tab with one click. It also watches the Windows event logs and emails you when someone is guessing passwords or signs in at odd hours. Start your 30-day free trial to see your own server’s results.

Leave a Reply

Your email address will not be published. Required fields are marked *