Skip to content
SysmonregistryRequires audit policy

Sysmon Event ID 13: RegistryEvent (Value Set)

Sysmon event 13 logs a registry value being written, with the data for DWORD, QWORD and string values. The main Sysmon event for registry persistence.

Overview

Event ID
13
Log / channel
Microsoft-Windows-Sysmon/Operational
Provider
Microsoft-Windows-Sysmon
Category
registry
Enabled by default
No
How to enable
Sysmon installed; filter with <RegistryEvent> rules in the configuration.

What event 13 logs

Sysmon event 13 records a registry value write: the value path in TargetObject, the data in Details, and the writing process. Numeric values appear as DWORD (0x...) or QWORD (...); string values show their text; binary data is not reproduced.

This is the event that shows Run key persistence, new service ImagePath values, disabled security features (for example Defender or UAC settings) and IFEO debugger hijacks, in one record with the responsible process.

Volume depends entirely on the configuration; target known persistence and security-setting paths.

Fields

Every field recorded in event 13, with the values that matter for investigation.

EventType

Always SetValue for this event.

ProcessGuid

Process that wrote the value; pivot to its event 1.

Image

Executable that wrote the value.

TargetObject

Full path of the value, e.g. HKU\<SID>\Software\Microsoft\Windows\CurrentVersion\Run\<name>.

Details

Data written. For Run keys and service ImagePath this is the command that will run; for DWORD settings, e.g. DWORD (0x00000001).

User

Account of the process (newer Sysmon versions).

How to enable this event

Sysmon installed; filter with <RegistryEvent> rules in the configuration.

Detection and investigation

Typically benign

  • Applications registering auto-start helpers in Run keys at install time.
  • Windows and Group Policy writing settings, Explorer updating per-user state (very frequent).

Worth investigating

  • Run or RunOnce values pointing to a binary or script in a user-writable folder.
  • Service ImagePath changed to a new binary, or a Debugger value set under Image File Execution Options.
  • Security settings weakened, such as Defender or firewall policy values set to disable protection.

Investigation notes

  • Read Details and check whether the referenced path exists and was recently written (event 11).
  • Pivot on ProcessGuid to event 1 — reg.exe, PowerShell or an unknown binary writing Run keys stands out.
  • Check for the matching key creation (event 12) and for the persisted program running after reboot (event 1).

MITRE ATT&CK techniques

Related event IDs

References