Windows Sysmon error events indicating service configuration update failures

Flags Windows Sysmon errors for failed service configuration/driver update attempts that may indicate tampering.

FreeReviewedSigma · High · v1
Product
windows
Category
sysmon_error
Author
frack113 (SigmaHQ), DRL 1.1
Published
2021-06-04
Updated
2026-07-30

ATT&CK techniques

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 matches Sysmon error messages reporting failures when opening service configuration and connecting to the driver to update configuration. Such activity can be used by an adversary attempting to disrupt or evade Sysmon logging, making these errors a useful stealth/defense evasion signal. The detection relies on the presence of specific error text and related error-code wording in Sysmon error telemetry, with several language and generic benign patterns filtered out.

Related detections9 linkedT1564 — drag to rearrange
Suspicious Windows Security Spoofing via pin Executable Writing output.txt via process_creation
Obfuscated Extended Rights Backdoor Obfuscation - Via localizationDisplayId Attribute (via security)
Suspicious Process Execution from Public User Media Folders via process_creation
Suspicious Windows Sandbox Configuration Execution for AsyncRAT via Process Creation
System Informer Execution on Windows Process Creation
Linux mount executed with hidepid=2 option
Windows Process Hacker Execution Identified by Image Metadata and Hashes
Windows File Events: Suspicious Executable File Name Creation
Windows: Suspicious Parent Process Execution From \Users\Public Spawning Scripting/Shell Binaries
Windows Sysmon error events indicating service configuration update failures
Pivot detection · T1564 · 9 related

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