Windows Sysmon Driver Altitude Registry Changes

ATT&CK techniques

Recon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule matches registry writes that update the Sysmon instance altitude value under the Services Instances path. Changing the driver altitude can be used to interfere with Sysmon’s ability to load correctly at boot, impacting monitoring through defense impairment. Detection relies on registry set events containing the TargetObject paths that include \Services\ and end with \Instances\Sysmon Instance\Altitude.

Reporting behind it

Related detections9 linkedT1685 — drag to rearrange

Suspicious Vulnerable Intel Ethernet Driver Load for BYOVD via SCATTERED SPIDER (via driver_load)

Malicious Defender Disable And Executable Exclusion Via Registry

Malicious UAC Disable via EnableLUA Registry Modification (via registry_set)

Malicious AMSI and ETW Patching via PowerShell Script

Malicious PowMix AMSI Bypass via amsiInitFailed

Suspicious ThrottleStop Driver Abuse for Defense Evasion in Ransomware Attacks

Malicious Disabling of Microsoft Defender Real-Time Protection via SystemSettingsAdminFlows by DeadLock Ransomware

Suspicious Security Software Uninstallation via WMIC Product Call Uninstall (Chaos Ransomware)

Suspicious Security Product Uninstall via wmic product call uninstall

Windows Sysmon Driver Altitude Registry Changes

Pivot detection · T1685 · 9 related

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

windows-sysmon-driver-altitude-registry-changes-4916a35e

title: Windows Sysmon Driver Altitude Registry Changes
id: b4b4d16c-4d2d-40ed-a6aa-f8e7ba1e0be0
status: test
description: This rule matches registry writes that update the Sysmon instance altitude value under the Services Instances path. Changing the driver altitude can be used to interfere with Sysmon’s ability to load correctly at boot, impacting monitoring through defense impairment. Detection relies on registry set events containing the TargetObject paths that include \Services\ and end with \Instances\Sysmon Instance\Altitude.
references:
  - https://posts.specterops.io/shhmon-silencing-sysmon-via-driver-unload-682b5be57650
  - https://youtu.be/zSihR3lTf7g
  - https://github.com/SigmaHQ/sigma/blob/master/rules/windows/registry/registry_set/registry_set_change_sysmon_driver_altitude.yml
author: B.Talebi, Huntrule Team
date: 2022-07-28
modified: 2024-03-25
tags:
  - attack.defense-impairment
  - attack.t1685
logsource:
  category: registry_set
  product: windows
detection:
  selection:
    TargetObject|contains: \Services\
    TargetObject|endswith: \Instances\Sysmon Instance\Altitude
  condition: selection
falsepositives:
  - Legitimate driver altitude change to hide sysmon
level: high
license: DRL-1.1
related:
  - id: 4916a35e-bfc4-47d0-8e25-a003d7067061
    type: derived

Convert

This rule as a query you can run. Uses no unlock credit.

SplunkSPL