| Device Key in Log Message | LogRhythm Schema | Data Type | Schema Description |
| Provider | N/A | N/A | Identifies the provider that logged the event. The Name and GUID attributes are included if the provider used an instrumentation manifest to define its events. The EventSourceName attribute is included if a legacy event provider (using the Event Logging API) logged the event. |
| EventID | <vmid> | Number | The identifier that the provider used to identify the event. |
| Version | N/A | N/A | The version number of the event's definition. |
| Level | <severity> | String/Number | The severity level defined in the event. |
| Task | <vendorinfo> | String/Number | The task defined in the event. Task and Opcode are typically used to identify the location in the application from where the event was logged. |
| Opcode | N/A | N/A | The opcode defined in the event. Task and Opcode are typically used to identify the location in the application from where the event was logged. |
| Keywords | <result> | Text/String | A bitmask of the keywords defined in the event. Keywords are used to classify types of events (for example, events associated with reading data). |
| TimeCreated | N/A | N/A | The time stamp that identifies when the event was logged. The time stamp will include either the SystemTime attribute or the RawTime attribute. |
| EventRecordID | N/A | N/A | The record number assigned to the event when it was logged. |
| Correlation | N/A | N/A | The activity identifiers that consumers can use to group related events together. |
| Execution | N/A | N/A | Contains information about the process and thread that logged the event. |
| Channel | N/A | N/A | The channel to which the event was logged. |
| Computer | <dname> | Text/String | The name of the computer on which the event occurred. |
| SubjectUserSid | N/A | N/A | The SID of account that requested the “modify registry value” operation. |
| SubjectUserName | <login> | Text/String | The name of the account that requested the “modify registry value” operation. |
| SubjectDomainName | <domainorigin> | Text/String | The subject’s domain or computer name. Formats vary, and include the following:- Domain NETBIOS name example: CONTOSO
- Lowercase full domain name: contoso.local
- Uppercase full domain name: CONTOSO.LOCAL
- For some well-known security principals, such as LOCAL SERVICE or ANONYMOUS LOGON, the value of this field is NT AUTHORITY.
- For local user accounts, this field will contain the name of the computer or device that this account belongs to.
|
| SubjectLogonId | <session> | Text/String | A hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID. |
| ObjectName | <subject> | Text/String | The full path and name of the registry key which value was modified. The format is: \REGISTRY\HIVE\PATH. |
| ObjectValueName | <objectname> | Text/String | The name of modified registry key value. |
| HandleId | <object> | Text/String | A hexadecimal value of a handle to Object Name. This field can help you correlate this event with other events that might contain the same Handle ID. |
| OperationType | <action> | Text/String/Number | The type of performed operation with registry key value. |
| OldvalueType | N/A | Text/String/Number | The old type of changed registry key value. |
| OldValue | N/A | N/A | The old value for changed registry key value. |
| NewValueType | N/A | N/A | The new type of changed registry key value. |
| NewValue | N/A | N/A | The new value for changed registry key value. |
| ProcessId | <processid> | Number | A hexadecimal Process ID of the process through which the registry key value was modified. Process ID (PID) is a number used by the operating system to uniquely identify an active process. |
| ProcessName | <process> | Text/String | The full path and the name of the executable for the process. |
