Sysmon event 13
RegistryEvent (Value Set)
Channel: Microsoft-Windows-Sysmon/Operational. Category: Registry.
What it records
Logs registry value modifications, recording the data written for DWORD and QWORD value types.
Why it matters
This is the primary Sysmon event for catching persistence via Registry Run/RunOnce keys and other autostart-referenced values: one of the most common, well-documented persistence mechanisms in Windows intrusions.
What triggers it
Legitimate application configuration changes, alongside malware writing itself or a loader into Run/RunOnce keys or other autostart-referenced values.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Image | The process that wrote the value: identifies what set the data, e.g., a script or installer versus a suspicious process. |
| TargetObject | The full path of the registry value modified: the field to match against known persistence locations like Run/RunOnce keys. |
| Details | The actual data written to the value (for DWORD/QWORD types); for Run-key-style persistence this is often the exact command that will execute at logon, making it directly actionable. |
In practice
Image C:\Windows\System32\cmd.exe writes TargetObject HKCU\Software\Microsoft\Windows\CurrentVersion\Run\OneDriveSync with Details powershell.exe -enc <base64>, under the profile for CORP\jsmith: the Details field hands the analyst the exact command that will fire at the user's next logon, confirming Registry Run Key persistence (T1547.001).
Sample record
Registry value set:
RuleName: technique_id=T1547.001,technique_name=Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
EventType: SetValue
UtcTime: 2024-01-15 14:46:15.678
ProcessGuid: {A1B2C3D4-E5F6-4A5B-8C9D-0E1F2A3B0007}
ProcessId: 2200
Image: C:\Windows\System32\reg.exe
TargetObject: HKU\S-1-5-21-1111111111-2222222222-3333333333-1001\Software\Microsoft\Windows\CurrentVersion\Run\Updater
Details: C:\Users\jsmith\AppData\Roaming\update.exe
User: CORP\jsmithATT&CK techniques
Sources
Paste a record into Event XML or open a log in EVTX Reader.