Security event 4657
A registry value was modified
Channel: Security. Category: Object Access (Audit Registry).
What it records
Records that a specific registry key VALUE (not the key itself) was modified. It generates only when 'Set Value' auditing is configured in the target key's SACL, and fires once per modified value, capturing the Operation Type (new value created, value deleted, or existing value modified) plus the value's old and new content and types.
Why it matters
One of the few Security events that shows a literal before/after diff of a registry change, which makes it the sharpest tool for confirming registry-based persistence or tampering as it happens: a Run/RunOnce autostart entry, a hijacked service ImagePath, or a disabled security-product setting all show up here with the exact old and new values and the process that wrote them, not just 'something changed.'
What triggers it
Legitimate configuration changes pushed by Group Policy, software installers, or admin tools like regedit.exe and PowerShell's Set-ItemProperty; anomalously, malware or an intruder writing a new autostart value under a Run/RunOnce key, editing a service's ImagePath to hijack or persist through it, or disabling a security tool's tamper-protection setting. Requires 'Set Value' SACL auditing on the specific key, which is not enabled by default.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Object Name | Full registry path of the key whose value changed (e.g. \REGISTRY\MACHINE\SOFTWARE\...), which identifies exactly which part of the hive was touched. |
| Object Value Name | The specific value name modified within that key: the actual autostart entry, service parameter, or setting name. |
| Operation Type | Whether the value was newly created, deleted, or modified, which separates a fresh persistence entry from cleanup or removal. |
| New Value | The literal content the value was changed to: the direct evidence of what changed, e.g. an ImagePath now pointing to an unexpected binary. |
| Process Name | Full path of the process that wrote the value, which attributes the change to a specific tool or rules one out. |
In practice
Logged when a process modifies a value under a Run key SACL-audited for 'Set Value': for example, a process writes a new value named 'Updater' under \REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run, with Operation Type 'New registry value created' and New Value pointing to C:\Users\Public\update.exe. Reviewing Object Value Name, Operation Type, and Process Name together flags an unfamiliar autostart entry written by a process with no legitimate reason to touch that key.
Sample record
A registry value was modified. Subject: Security ID: CORP\jsmith Account Name: jsmith Account Domain: CORP Logon ID: 0x3E4F2 Object: Object Name: \REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run Object Value Name: Updater Handle ID: 0x220 Operation Type: New registry value created Process Information: Process ID: 0x1a84 Process Name: C:\Windows\regedit.exe Change Information: Old Value Type: - Old Value: - New Value Type: REG_SZ New Value: C:\Users\Public\update.exe
ATT&CK techniques
Sources
Paste a record into Event XML or open a log in EVTX Reader.