Port 3389/tcp/udp: RDP (Remote Desktop Protocol)
Category: File Sharing & Remote Access. Range: registered. Status: iana registered.
What runs here
Microsoft's remote graphical desktop protocol (MS-RDPBCGR), historically a pure TCP protocol but, since RDP 8.0, able to negotiate an additional UDP transport (MS-RDPEUDP) for the same session, used to improve responsiveness for graphics, input, and audio when available, with TCP always present as the base/fallback channel. IANA registers ms-wbt-server on both TCP and UDP port 3389, and Microsoft's own documentation lists "TCP and UDP 3389" as the standard RDP port.
Why it matters
RDP is the single highest-value remote-access port on a Windows network for both legitimate admins and intruders alike: a valid credential over RDP grants a full interactive desktop session. It is central to the modern ransomware playbook. Exposed RDP is one of the most common initial-access vectors brute-forced or purchased by initial-access brokers and ransomware affiliates, and RDP is equally a common lateral-movement path once inside a network.
Where you see it
Legitimately: help-desk/sysadmin remote support, RDS session hosts, remote work. Anomalously/maliciously: internet-facing RDP brute-force or credential-stuffing (near-constant background noise on any exposed 3389), RDP used as initial access or lateral movement by ransomware operators, or RDP session hijacking via tscon.exe.
What to look for
| Signal | What it means |
|---|---|
| Logon Type 10 | Events 4624 (success) / 4625 (failure) with Logon Type 10 (RemoteInteractive) are the definitive Windows Security-log marker of an RDP logon attempt. |
| Event 1149 | TerminalServices-RemoteConnectionManager/Operational Event 1149 records an authenticated RDP network connection and persists even if the Security log has since rolled over, useful when the primary log has aged out. |
In practice
A host with no history of legitimate remote-admin RDP activity logs a burst of Logon Type 10 failures (Event 4625) from a single external IP, followed by one success (Event 4624): a textbook brute-force-then-compromise pattern that should trigger immediate triage of that account and host.
ATT&CK techniques
- T1021.001: T1021.001