huntrule

Windows Sysmon Operational Channel Reference Deleted via Security Event

Detects Security log events showing Sysmon Operational channel being disabled via channel reference deletion-like changes.

FreeReviewedSigma · High · v2
Product
windows
Service
security
Author
Roberto Rodriguez (Cyb3rWard0g), OTR (Open Threat Research) (SigmaHQ), DRL 1.1
Published
2020-07-14
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Persistence → Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies attempts to disable the Sysmon Operational channel by changing an event channel value from Enabled to 0 and by observing related registry access. Attackers may impair defenses by muting or disabling Sysmon to reduce visibility into their activity. The detection relies on Windows Security logs (Event IDs 4657 and 4663) capturing object name/value updates and access attempts for the Sysmon event channel identifiers.

Reporting behind it

Related detections9 linkedT1112 — drag to rearrange
Suspicious Registry Value under Console WindowsUpdates for C2 Storage
Suspicious Office VBA Object Model Access Enabled via Registry (via registry_set)
Suspicious PowerShell Payload Staging in HKCU Printers Registry Key
Suspicious Rootkit Configuration Registry Keys (via registry_set)
Suspicious Disabling of Chromium App-Bound Encryption via Policy Registry Key (via registry_set)
Windows reg.exe Registry Tampering of Internal Tool and Explorer Policy Settings (T1112)
Suspicious Disabling of Restricted Admin Mode via Registry (via registry_set)
Malicious WDigest UseLogonCredential Enabled for Cleartext Credential Theft (via registry_set)
Suspicious ClickFix RunMRU Entry Recording LOLBIN Command from Run Dialog
Windows Sysmon Operational Channel Reference Deleted via Security Event
Pivot detection · T1112 · 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.