Windows Successful SMB Logon (Event ID 4624 Logon Type 3) From Public IPs

Flags successful Windows SMB (LogonType 3) logons from non-private, non-local source IP addresses.

FreeReviewedSigma · High · v2
Product
windows
Service
security
Author
Micah Babinski (@micahbabinski), Zach Mathis (@yamatosecurity) (SigmaHQ), DRL 1.1
Published
2023-01-19
Updated
2026-07-31

ATT&CK techniques

Initial Access → Cred Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule identifies successful Windows logons using SMB (LogonType 3) where the source IP is not one of the local/private or otherwise excluded ranges and is not empty. Attackers may use network SMB authentication from the internet after initial access or during lateral movement, so public-facing SMB logons are a high-signal indicator. It relies on Windows Security Event ID 4624 telemetry and the event fields for LogonType and source IpAddress.

Related detections9 linkedT1078 — drag to rearrange
Windows RDP Successful Logon (4624 LogonType 10) from Public IP
OpenCanary Telnet Login Attempt Recorded in Application Logs
OpenCanary application logs: SSH new connection attempt on monitored node
OpenCanary Application Logs: SSH Login Attempt on Monitoring Node
Cisco LDP MD5 Authentication Failure Events
Cisco BGP Authentication Failure Events Indicating Potential Credential Attacks
Huawei BGP Authentication Failures Indicating Failed Session Attempts
Juniper BGP Logs: Missing MD5 Digest in Route Authentication
Windows Failed Logon (Event ID 4625) From Non-Private Public IP
Windows Successful SMB Logon (Event ID 4624 Logon Type 3) From Public IPs
Pivot detection · T1078 · 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.