OpenCanary Application Logs: Detect SYN Port Scan Targets on a Hosted Node

Flags OpenCanary events indicating the host was probed with a TCP SYN port scan.

FreeReviewedSigma · High · v5
Product
opencanary
Category
application
Author
Marco Pedrinazzi (@pedrinazziM) (SigmaHQ), DRL 1.1
Published
2026-01-06
Updated
2026-07-31

ATT&CK techniques

Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies when an OpenCanary node is targeted by a TCP SYN port scan, based on application logs indicating scan activity (logtype 5001). SYN scanning is a common discovery technique used to enumerate open ports quickly before further exploitation. The detection relies on OpenCanary application telemetry that records the scan-related event type.

Related detections9 linkedT1046 — drag to rearrange
Suspicious Fscan Internal Network Scanner Execution (via process_creation)
Possible Network Service Scanning via Nmap or Masscan (via process_creation)
Malicious Anonymous Login - Domain Specified (via security)
Suspicious Network Scanning Tool Execution
Malicious RDP Discovery Performed on Multiple Hosts (via rdp)
Malicious Anonymous Access Performed to Multiple Targets (via security)
Malicious Network Login Performed to Multiple Targets (via security)
Suspicious SoftPerfect Network Scanner Execution for Discovery
Suspicious SoftPerfect Network Scanner Execution (via process_creation)
OpenCanary Application Logs: Detect SYN Port Scan Targets on a Hosted Node
Pivot detection · T1046 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.