An RDP listener exposed to the internet collects thousands of failed login attempts a day. Securing it is not one setting but a short stack of them, and doing them in the right order avoids the familiar mistake of locking yourself out at step three. This is the order that works on a fresh Windows Server instance.
Start With the Firewall, Not With RDP
Before touching any RDP configuration, open Windows Defender Firewall with Advanced Security and create an inbound rule that allows TCP 3389 only from the addresses you actually connect from. If your ISP hands out a dynamic address, use the widest prefix that still covers your range rather than Any.
Test the rule from a second session before you close the first one. Providers give console access through their panel for exactly this situation, but relying on it during an outage adds minutes you do not have. Having two independent working sessions open is the cheapest insurance available.
Network Level Authentication Is Not Optional
System Properties → Remote → “Allow connections only from computers running Remote Desktop with Network Level Authentication” should be checked. NLA performs authentication before a session is allocated, which means unauthenticated traffic never reaches the session manager. Without it, pre-authentication vulnerabilities in the RDP stack are reachable by anyone who can route to the port.
Some older clients refuse NLA. That is usually a signal to update the client rather than to weaken the server, but if a specific legacy tool genuinely cannot negotiate it, isolate that exception to one host and document why it exists.
Local Security Policy: Lockout and Logon Rights
Open Local Security Policy and set an account lockout threshold. Ten invalid attempts with a fifteen-minute duration is a reasonable default for a small server; the goal is to make online guessing uneconomical without letting a typo lock out the only administrator. Pair it with a logon-hours restriction only if the workload genuinely runs on a schedule.
Then review “Allow log on through Remote Desktop Services”. By default it includes Administrators and Remote Desktop Users. Remove any group you do not recognise — particularly anything inherited from a template image someone else built.
Rename and Disable the Built-In Administrator
The account named Administrator has a known name and a fixed well-known SID, so it is the first thing any password spray targets. Create a separate administrative account with an unrelated name, confirm it can log in and elevate, and then disable the built-in one. Verify the new account works before disabling the old, not after.
Keep the built-in account disabled rather than deleted: it is the recovery path in Safe Mode if your custom account’s profile is damaged. Document the recovery procedure in the same place you store the console credentials.
Certificate Binding to Remove the Identity Warning
The self-signed RDP certificate produces an “identity cannot be verified” prompt at every connection from a new client. Binding a certificate the client already trusts removes the prompt, which matters because administrators who click through warnings routinely will click through a real one during an attack.
Issue the certificate from your internal CA with the server’s fully qualified hostname as a subject alternative name, then bind it to the RDP listener through the Remote Desktop Session Host configuration. Confirm the thumbprint matches after binding, since a mismatch produces a silent fallback to the self-signed certificate.
Auditing Failed Logons
Enable the Audit Logon and Audit Other Logon/Logoff Events policies under Advanced Audit Policy Configuration. Event ID 4625 records failed logons with source address and account name; 4624 records successes with logon type 10 for RDP. Collecting these for a week tells you whether you are being targeted and from where.
For a single server, forwarding those events to a central collector is optional. For a fleet, it is mandatory — an attacker who disables local logging on one host removes your only record. See how our Windows VPS options handle outbound log shipping when sizing the plan.
What Belongs Behind a VPN Instead
If the people connecting are a fixed small team, putting RDP behind a WireGuard or provider VPN removes it from the public internet entirely and is strictly better than any port-hardening exercise. The trade-off is a second piece of client software on every device.
For occasional access from changing locations, certificate-based RDP with a short-lived client certificate is a middle path that avoids exposing passwords at all. Whichever you choose, write the decision down with the reasoning, because the next administrator will otherwise re-open the port during a support call. Whichever path you take, verify it from a second network before you close the session that made the change — a policy that works only because an existing authenticated session bypassed it is not a policy that works.
Verification and Ongoing Maintenance
After every change in this list, reconnect from a genuinely different network — a phone hotspot is enough — rather than trusting the session that is already open. A rule that works only because the existing session bypassed it is not a working rule.
Then confirm the exposed state from outside: a port scan of your own address should show the RDP port either closed to the world or filtered. Our comparison of Windows VPS plans notes which configurations include external firewall management in the control panel, which makes this verification a two-click check.
Review the allowed source list quarterly. Addresses that were valid when you provisioned — a home connection, a former colleague’s laptop — outlive their justification by years if nobody looks. Combine the review with your credential rotation so it happens on a schedule rather than after an incident.
Keep the server patched and reboot on a known cadence; an exposed RDP service on an unpatched host is the specific combination attackers scan for. Neither hardening nor patching is sufficient alone, and the two together take about an hour a quarter.



