{"id":658,"date":"2026-08-19T23:24:59","date_gmt":"2026-08-19T23:24:59","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=658"},"modified":"2026-08-28T22:22:55","modified_gmt":"2026-08-28T22:22:55","slug":"secure-rdp-brute-force-attacks","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/","title":{"rendered":"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Remote Desktop Protocol (RDP) is the most targeted service on any public-facing Windows server. Botnets continuously scan the internet for port 3389, and ransomware operators routinely buy stolen RDP credentials or brute-force their way in. The good news is that Windows Server ships with the tools to stop almost all of these attacks. This article covers seven hardening steps &mdash; from account lockout to RD Gateway &mdash; that collectively block 99% of automated brute-force attempts. If you are still choosing a provider, <a href=\"https:\/\/windows-vps.org\/#providers\">our Windows VPS comparison table<\/a> flags providers that include firewall and DDoS protection in the base plan.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How RDP Brute-Force Attacks Work<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Understanding the attack pattern helps you choose the right defenses. A typical campaign follows this sequence:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A scanner finds your server because port 3389 responds. The entire IPv4 range is swept continuously &mdash; no prior knowledge of your IP is needed.<\/li>\n<li>The attacker tries common usernames (<code>Administrator<\/code>, <code>admin<\/code>, <code>user<\/code>) against dictionaries of leaked passwords and default credentials.<\/li>\n<li>Sophisticated attackers throttle to a few attempts per minute per source IP to stay under lockout thresholds, spreading the load across hundreds of botnet nodes.<\/li>\n<li>A single successful login &mdash; even to a low-privilege account &mdash; is enough to start reconnaissance, install persistence, and move laterally.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The key insight: single-IP defenses are not enough because the traffic comes from thousands of addresses. You need layered controls that make the attempts fail regardless of the source.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Configure Account Lockout Policy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The account lockout policy is your first line of defense. It limits how many failed logon attempts are allowed before the account is temporarily locked. Open <code>secpol.msc<\/code> and navigate to <strong>Account Policies &rarr; Account Lockout Policy<\/strong>, or set it via Group Policy:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Setting<\/th><th>Recommended Value<\/th><\/tr><\/thead><tbody><tr><td>Account lockout threshold<\/td><td>5 invalid attempts<\/td><\/tr><tr><td>Account lockout duration<\/td><td>15 minutes<\/td><\/tr><tr><td>Reset account lockout counter after<\/td><td>15 minutes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Set these via PowerShell on a standalone server:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>net accounts \/lockoutthreshold:5 \/lockoutduration:15 \/lockoutwindow:15<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Watch for lockout denial-of-service: an attacker who knows your admin account name can lock it repeatedly. Keep a second break-glass account outside the policy and monitor Event ID 4740 (account locked out).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Rename the Built-In Administrator Account<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The default <code>Administrator<\/code> account has a well-known SID (S-1-5-21-&#8230;-500). Attackers target it first because it is always present and always has elevated privileges. Rename it and create a separate local admin account with a different name for daily use:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Rename the built-in Administrator account\n$admin = Get-LocalUser -Name \"Administrator\"\nRename-LocalUser -InputObject $admin -NewName \"X-Admin-$(Get-Random -Maximum 99999)\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then create a new account for your own daily administration and add it to the Administrators group. Use the renamed account only as a break-glass recovery option.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Enable Network Level Authentication (NLA)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">NLA forces the client to authenticate <em>before<\/em> a full RDP session is created. With NLA off, an attacker completes the RDP handshake and reaches the Windows logon screen, which historically enabled &ldquo;BlueKeep&rdquo;-class vulnerabilities and lets attackers hammer the credential prompt with less noise. With NLA on, the connection is rejected unless the client presents valid credentials up front:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Verify NLA is enabled\nGet-ItemProperty \"HKLM:\\SYSTEM\\CurrentControlSet\\Control\\Terminal Server\\WinStations\\RDP-Tcp\" |\n  Select-Object UserAuthentication, SecurityLayer\n\n# UserAuthentication should be 1, SecurityLayer should be 2<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">NLA is enabled by default on Windows Server 2022\/2025, but templates and imaging pipelines occasionally disable it. Confirm it during every server build.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Restrict RDP Access by Firewall and IP<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The single most effective control is restricting <strong>which IP addresses<\/strong> can reach port 3389. If your team connects from a static office IP or a VPN endpoint, whitelist only those addresses:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Remove the default \"allow all\" rule\nRemove-NetFirewallRule -DisplayName \"Remote Desktop*\"\n\n# Create a scoped rule\nNew-NetFirewallRule -DisplayName \"RDP - Office IP\" `\n  -Direction Inbound -Protocol TCP -LocalPort 3389 `\n  -RemoteAddress \"203.0.113.0\/24\" -Action Allow<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you cannot whitelist specific IPs, at minimum restrict the RDP firewall rule to your VPN subnet. Many VPS providers also offer security groups &mdash; use them as a first line of defense before the Windows firewall even sees the traffic.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Change the Default RDP Port<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Changing port 3389 to a non-standard port is cosmetic against a targeted attack, but it eliminates the vast majority of automated scanner noise. On a server exposed to the internet, this alone can reduce failed logins from 20,000\/day to under 100\/day:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Change RDP port from 3389 to 3390 (or any other port)\nSet-ItemProperty \"HKLM:\\SYSTEM\\CurrentControlSet\\Control\\Terminal Server\\WinStations\\RDP-Tcp\" -Name PortNumber -Value 3390\n\n# Update the firewall rule\nNew-NetFirewallRule -DisplayName \"RDP - Custom Port 3390\" `\n  -Direction Inbound -Protocol TCP -LocalPort 3390 -Action Allow<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Do not forget to update your RDP client connection settings to use the new port: <code>your-server:3390<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Use a Remote Desktop Gateway or VPN<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For the strongest protection, do not expose RDP at all. Instead, route RDP through a Remote Desktop Gateway (RD Gateway) or a VPN. An RD Gateway terminates TLS on port 443, hides the session host, and lets you enforce MFA at the gateway. For single servers, a WireGuard or SSTP VPN with RDP bound to the VPN interface only is the strongest configuration you can build with built-in tools. The practical effect: the public interface never sees an RDP connection attempt, which makes the lockout policy and port change almost redundant in practice.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Monitor and Audit RDP Logins<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Even with all the above controls in place, monitoring tells you if something slipped through. Key Event IDs to track:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Event ID<\/th><th>Description<\/th><\/tr><\/thead><tbody><tr><td>4625<\/td><td>Failed logon attempt<\/td><\/tr><tr><td>4624 (Logon Type 10)<\/td><td>Successful RDP logon<\/td><\/tr><tr><td>4740<\/td><td>Account locked out<\/td><\/tr><tr><td>4648<\/td><td>Logon using explicit credentials<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Quick check for recent failed logins:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4625} -MaxEvents 50 |\n  Select TimeCreated, @{n='User';e={$_.Properties[5].Value}}, @{n='SourceIP';e={$_.Properties[18].Value}}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Set up a scheduled task that alerts when the failed-login rate exceeds a threshold &mdash; for example, 50 failed attempts in 10 minutes. Forward these events to a SIEM or a simple log aggregator for long-term trend analysis.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Putting It Together<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These seven steps form a layered defense that works together. Account lockout stops brute-force guessing. Renaming the admin account removes the most common target. NLA eliminates pre-auth attack surface. IP restriction and port change reduce noise. VPN or Gateway hides RDP entirely. Monitoring catches anything that gets through. Apply all seven before the server ever gets a public IP, and you can skip most of the &ldquo;RDP honeypot&rdquo; anxiety. When you are choosing a provider, <a href=\"https:\/\/windows-vps.org\/#providers\" rel=\"noreferrer noopener sponsored\">compare Windows VPS plans<\/a> and check which ones include security-group support and DDoS protection &mdash; worth having when 3389 has to face the internet.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Remote Desktop Protocol (RDP) is the most targeted service on any public-facing Windows server. Botnets continuously scan the internet for port 3389, and ransomware operators routinely buy stolen RDP credentials or brute-force their way in. The good news is that Windows Server ships with the tools to stop almost all of these attacks. This article &#8230; <a title=\"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks\" class=\"read-more\" href=\"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/\" aria-label=\"Read more about RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":9,"footnotes":""},"categories":[5],"tags":[],"class_list":["post-658","post","type-post","status-publish","format-standard","hentry","category-tutorials-guides"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks - Windows VPS Blog<\/title>\n<meta name=\"description\" content=\"Remote Desktop Protocol (RDP) is the most targeted service on any public-facing Windows server. Botnets continuously scan the internet for port 3389, and\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks\" \/>\n<meta property=\"og:description\" content=\"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks\" \/>\n<meta property=\"og:url\" content=\"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/\" \/>\n<meta property=\"og:site_name\" content=\"Windows VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-19T23:24:59+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-28T22:22:55+00:00\" \/>\n<meta name=\"author\" content=\"windows-vps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@myxiechengxuan\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"windows-vps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/\",\"url\":\"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/\",\"name\":\"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks - Windows VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\"},\"datePublished\":\"2026-08-19T23:24:59+00:00\",\"dateModified\":\"2026-08-28T22:22:55+00:00\",\"author\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\"},\"description\":\"Remote Desktop Protocol (RDP) is the most targeted service on any public-facing Windows server. Botnets continuously scan the internet for port 3389, and\",\"breadcrumb\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/windows-vps.org\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\",\"url\":\"https:\/\/windows-vps.org\/blog\/\",\"name\":\"Windows VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/windows-vps.org\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\",\"name\":\"windows-vps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"caption\":\"windows-vps\"},\"sameAs\":[\"https:\/\/windows-vps.org\/blog\",\"https:\/\/x.com\/myxiechengxuan\"],\"url\":\"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks - Windows VPS Blog","description":"Remote Desktop Protocol (RDP) is the most targeted service on any public-facing Windows server. Botnets continuously scan the internet for port 3389, and","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/","og_locale":"en_US","og_type":"article","og_title":"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks","og_description":"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks","og_url":"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/","og_site_name":"Windows VPS Blog","article_published_time":"2026-08-19T23:24:59+00:00","article_modified_time":"2026-08-28T22:22:55+00:00","author":"windows-vps","twitter_card":"summary_large_image","twitter_creator":"@myxiechengxuan","twitter_misc":{"Written by":"windows-vps","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/","url":"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/","name":"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks - Windows VPS Blog","isPartOf":{"@id":"https:\/\/windows-vps.org\/blog\/#website"},"datePublished":"2026-08-19T23:24:59+00:00","dateModified":"2026-08-28T22:22:55+00:00","author":{"@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58"},"description":"Remote Desktop Protocol (RDP) is the most targeted service on any public-facing Windows server. Botnets continuously scan the internet for port 3389, and","breadcrumb":{"@id":"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/windows-vps.org\/blog\/secure-rdp-brute-force-attacks\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/windows-vps.org\/blog\/"},{"@type":"ListItem","position":2,"name":"RDP Brute-Force Protection: 7 Server Hardening Steps That Block 99% of Attacks"}]},{"@type":"WebSite","@id":"https:\/\/windows-vps.org\/blog\/#website","url":"https:\/\/windows-vps.org\/blog\/","name":"Windows VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/windows-vps.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58","name":"windows-vps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","caption":"windows-vps"},"sameAs":["https:\/\/windows-vps.org\/blog","https:\/\/x.com\/myxiechengxuan"],"url":"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/"}]}},"_links":{"self":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/658","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/comments?post=658"}],"version-history":[{"count":2,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/658\/revisions"}],"predecessor-version":[{"id":704,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/658\/revisions\/704"}],"wp:attachment":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/media?parent=658"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/categories?post=658"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/tags?post=658"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}