Sysmon event 4
Sysmon service state changed
Channel: Microsoft-Windows-Sysmon/Operational. Category: Service State Change.
What it records
Reports the state of the Sysmon service itself: that it started or stopped.
Why it matters
An unexpected stop is a key integrity check on the logging pipeline. It can indicate a gap in telemetry, whether from routine maintenance or an attacker attempting to disable monitoring.
What triggers it
Normal service start at boot and legitimate reconfiguration or upgrade, but also a deliberate stop by an administrator or an attacker with sufficient privileges.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| State | Whether the Sysmon service started or stopped: an unexpected Stop right before other suspicious activity strongly suggests an attacker blinding telemetry. |
| Version | The Sysmon binary version running, which confirms exactly what capabilities were active if a gap in coverage needs explaining. |
| SchemaVersion | The event schema version in effect at the time, which matters for confirming which fields to expect in other events from that period. |
In practice
State changes to "Stopped" with no corresponding maintenance window or config change logged beforehand, because Sysmon writes this event as part of its own shutdown, an unexplained stop here is a strong signal an attacker tried to blind endpoint logging before further activity.
Sample record
Sysmon service state changed: UtcTime: 2024-01-15 09:01:00.001 State: Stopped Version: 15.15 SchemaVersion: 4.90
Sources
Paste a record into Event XML or open a log in EVTX Reader.