RDP (3389) open to the whole internet
Remote Desktop on port 3389, reachable from the internet, is one of the most abused entry points — brute-forced and exploited through RDP vulnerabilities to land ransomware.
Why it matters
A large share of ransomware incidents begin with exposed RDP: weak or reused passwords are guessed, or a known RDP CVE is exploited.
Exposed RDP is found within minutes and attacked continuously; MFA and patching help but don't remove the exposure.
How to check for it
- Check cloud firewall / NSG / security-group rules for 3389 open to Any / 0.0.0.0/0.
- From outside your network, confirm 3389 is not reachable on your public IPs.
How to fix it
- Never expose 3389 publicly — require a VPN, a bastion, or a zero-trust access service, and restrict the port to those sources.
- Enforce MFA for remote access and keep the OS patched against RDP vulnerabilities.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Is changing the RDP port enough?
- No — moving off 3389 only slows casual scanning. The real fix is to keep RDP off the public internet behind a VPN or bastion.