Skip to main content
Skip table of contents

EVID 13 : Registry Value Set (Sysmon 7.01)

Event Details

Event TypeRegistryEvent (Value Set)
Event Description13 : Identifies Registry value modifications.
Event ID13

Log Fields and Parsing

This section details the log fields available in this log message type, along with values parsed for both LogRhythm Default and LogRhythm Default v2.0 policies. A value of "N/A" (not applicable) means that there is no value parsed for a specified log field.

Log FieldLogRhythm DefaultLogRhythm Default v2.0
ProviderN/A N/A
EventID<vmid><vmid>
VersionN/A N/A 
Level<severity><severity>
Task<vendorinfo><vendorinfo>
OpcodeN/A N/A 
KeywordsN/A <result>
TimeCreated N/A N/A 
EventRecordIDN/A N/A 
Correlation N/A N/A 
Execution N/A N/A 
ChannelN/A N/A 
Computer<dname><dname>
Security N/A N/A 
UserID<domain>, <login>N/A 
EventType<action><action>, <tag1>
ProcessGuid<session>N/A 
ProcessId<processid><processid>
Image<subject>, <processpath>, <process><process>
TargetObject<object><object>
RuleNameN/A<policy>

Log Processing Settings

This section details log processing changes made from the LogRhythm Default policy to LogRhythm Default v2.0. In some cases, base rules are broken down into sub-rules to appropriately parse log message types by their event types.

LogRhythm Default

Regex ID

Rule Name

Rule Type

Common Events

Classification

1009449EVID 13 : Registry Value SetBase RuleObject ModifiedAccess Success

LogRhythm Default v2.0

Regex ID

Rule Name

Rule Type

Common Events

Classification

1011211V 2.0 : Registry Modification EventsBase RuleObject ModifiedAccess Success
V 2.0 : EVID 12 : Registry Object CreatedSub RuleObject CreatedAccess Success
V 2.0 : EVID 12 : Registry Object DeletedSub RuleObject Deleted/RemovedAccess Success
V 2.0 : EVID 13 : Registry Value SetSub RuleObject ModifiedAccess Success
V 2.0 : EVID 14 : Registry Object RenamedSub RuleObject RenamedAccess Success
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.