CyberKit

Event IDs

Sysmon event 16

ServiceConfigurationChange

Channel: Microsoft-Windows-Sysmon/Operational. Category: Sysmon Configuration.

What it records

Logs changes to the Sysmon configuration itself, such as when filtering rules are updated.

Why it matters

An unexpected configuration change (e.g., rules that suddenly exclude a process or event type) can indicate an attacker with admin access tampering with the logging pipeline to blind specific detections.

What triggers it

Legitimate administrative reconfiguration or tuning of Sysmon's rules, or an attacker with elevated privileges altering the configuration to suppress logging of their activity.

Fields that carry the answer

Key fields
FieldWhat it tells you
ConfigurationThe path to the configuration file or the exact command line used to reconfigure Sysmon. It shows precisely what was changed and by what means, which matters when checking whether a legitimate admin or an attacker made the change.
ConfigurationFileHashThe hash of the configuration file applied, when one was used, which lets you confirm whether the new config matches your known-good baseline or was tampered with.

In practice

Configuration shows the service was reconfigured via sysmon.exe -c newconfig.xml, and the resulting ConfigurationFileHash doesn't match the SHA256 of the organization's approved baseline config, seen without a corresponding deployment-tooling change ticket, that mismatch is a strong indicator someone with local admin rights altered filtering rules to suppress specific logging.

Sample record

Sysmon config state changed:
UtcTime: 2024-01-15 09:12:00.000
Configuration: C:\ProgramData\sysmonconfig.xml
ConfigurationFileHash: SHA256=A1B2C3D4E5F60718293A4B5C6D7E8F9001122334455667788990AABBCCDDEEFF

Sources

Paste a record into Event XML or open a log in EVTX Reader.