OpenCanary Application Logs: Nmap FIN Scan Targeting (Logtype 5005)

Detects Nmap FIN scan targeting against an OpenCanary node using application logs with logtype 5005.

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 flags OpenCanary instances where the service records activity consistent with an Nmap FIN scan targeting the node. FIN scans are a common reconnaissance technique used to probe network services while attempting to evade more conspicuous scan signatures. Detection relies on OpenCanary application telemetry indicating the specific event logged as logtype 5005.

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: Nmap FIN Scan Targeting (Logtype 5005)
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.