14 : Maps registry key and value rename operations to this event type.
Event ID
14
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 Field
LogRhythm Default
LogRhythm Default v2.0
Provider
N/A
N/A
EventID
<vmid>
<vmid>
Version
N/A
N/A
Level
<severity>
<severity>
Task
<vendorinfo>
<vendorinfo>
Opcode
N/A
N/A
Keywords
N/A
<result>
TimeCreated
N/A
N/A
EventRecordID
N/A
N/A
Correlation
N/A
N/A
Execution
N/A
N/A
Channel
N/A
N/A
Computer
<dname>
<dname>
Security
<domain>, <login>
N/A
EventType
<action>, <tag1>
<action>, <tag1>
ProcessGuid
<session>
N/A
ProcessId
<processid>
<processid>
Image
<subject>, <processpath>, <process>
<process>
TargetObject
<object>
<object>
RuleName
<policy>
<policy>
NewName
<result>
N/A
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 Event
Classification
1009733
EVID 14 : Key And Value Rename
Base Rule
Object Modified
Access Success
EVID 14 : Rename Value
Sub Rule
Object Modified
Access Success
EVID 14 : Key Renamed
Sub Rule
Object Modified
Access Success
LogRhythm Default v2.0
Regex ID
Rule Name
Rule Type
Common Event
Classification
1011211
V 2.0 : Registry Modification Events
Base Rule
Object Modified
Access Success
V 2.0 : EVID 12 : Registry Object Created
Sub Rule
Object Created
Access Success
V 2.0 : EVID 12 : Registry Object Deleted
Sub Rule
Object Deleted/Removed
Access Success
V 2.0 : EVID 13 : Registry Value Set
Sub Rule
Object Modified
Access Success
V 2.0 : EVID 14 : Registry Object Renamed
Sub Rule
Object Renamed
Access Success
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.
