Windows: Outbound RDP (3389) Connections Initiated by Non-Standard Processes

Alerts on outbound port 3389 connections on Windows when initiated by an unapproved process, suggesting non-standard RDP tooling.

FreeReviewedSigma · High · v2
Product
windows
Category
network_connection
Author
Markus Neis (SigmaHQ), DRL 1.1
Published
2019-05-15
Updated
2026-07-31

ATT&CK techniques

Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies outbound network connections to destination port 3389 that are initiated by processes other than the expected mstsc.exe RDP client and other commonly allowed RDP-related binaries. Attackers may use alternate tools to establish RDP sessions for lateral movement while avoiding detection tied to mstsc.exe. The rule relies on Windows network connection telemetry with fields for destination port, initiation status, and the initiating process image path (including image exceptions).

Related detections9 linkedT1021.001 — drag to rearrange
Suspicious TermService ServiceDll Hijack via Registry (via registry_set)
Suspicious RDP Connection File Opened From Download or Mail Directory via Process Creation
Suspicious Firewall Rule Allowing SSH via New-NetFirewallRule During Ransomware
Malicious RDP Tunneling via ngrok (via process_creation)
Suspicious Remote Desktop Enablement via Registry By Ransomware
Suspicious Remote Desktop Enablement via netsh Firewall Rule (via process_creation)
Suspicious RDP Enablement via netsh Firewall Rule
Suspicious RDP Enablement via fDenyTSConnections Registry Modification
Suspicious RDP Enablement via fDenyTSConnections Registry Modification [Huntress] #2
Windows: Outbound RDP (3389) Connections Initiated by Non-Standard Processes
Pivot detection · T1021.001 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.