Why do the same Windows Server 2022 std (Traditional Chinese) data collected using XDRC and WEC agents show different statuses in the following fields?
Question 1 : Are the logs from XDRC and WEC displayed correctly? There is currently no documentation specifying this.
Question 2 : I've read the Paloalto tutorials, which all focus on log filtering and parsing using the `_raw_log` field.
I'd like to ask how to perform log normalization in XDRC, which doesn't have a `_RAW_LOG` field?
YT : Cortex XDR How-To Video: Custom Parsing Rules
Question 3 : Because the log content formats collected by "_raw_log" and "message" are different, it is common to encounter situations where fields are created but the correct values cannot be parsed correctly.
Therefore, I would like to confirm what method is used to parse the logs within the specified format.
| Message | _RAW_LOG |
|
An account was successfully logged on.
Subject:
Security ID: S-1-5-18
Account Name: XSIAM-WEC01$
Account Domain: WORKGROUP
Logon ID: 0x3E7
Logon Information:
Logon Type: 5
Restricted Admin Mode: -
Virtual Account: No
Elevated Token: Yes
Impersonation Level: Impersonation
New Logon:
Security ID: S-1-5-18
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3E7
Linked Logon ID: 0x0
Network Account Name: -
Network Account Domain: -
Logon GUID: {00000000-0000-0000-0000-000000000000}
Process Information:
Process ID: 0x2a0
Process Name: C:\Windows\System32\services.exe
Network Information:
Workstation Name: -
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon session is created. It is generated on the computer that was accessed.
The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The impersonation level field indicates the extent to which a process in the logon session can impersonate.
The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
|
<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='Microsoft-Windows-Security-Auditing' Guid='{54849625-5478-4994-a5ba-3e3b0328c30d}'/><EventID>4624</EventID><Version>2</Version><Level>0</Level><Task>12544</Task><Opcode>0</Opcode><Keywords>0x8020000000000000</Keywords><TimeCreated SystemTime='2026-01-18T22:57:56.2825739Z'/><EventRecordID>16486</EventRecordID><Correlation ActivityID='{cb9aec07-7b8a-0001-a3ec-9acb8a7bdc01}'/><Execution ProcessID='692' ThreadID='5844'/><Channel>Security</Channel><Computer>XSIAM-WEC01</Computer><Security/></System><EventData><Data Name='SubjectUserSid'>S-1-5-18</Data><Data Name='SubjectUserName'>XSIAM-WEC01$</Data><Data Name='SubjectDomainName'>WORKGROUP</Data><Data Name='SubjectLogonId'>0x3e7</Data><Data Name='TargetUserSid'>S-1-5-18</Data><Data Name='TargetUserName'>SYSTEM</Data><Data Name='TargetDomainName'>NT AUTHORITY</Data><Data Name='TargetLogonId'>0x3e7</Data><Data Name='LogonType'>5</Data><Data Name='LogonProcessName'>Advapi </Data><Data Name='AuthenticationPackageName'>Negotiate</Data><Data Name='WorkstationName'>-</Data><Data Name='LogonGuid'>{00000000-0000-0000-0000-000000000000}</Data><Data Name='TransmittedServices'>-</Data><Data Name='LmPackageName'>-</Data><Data Name='KeyLength'>0</Data><Data Name='ProcessId'>0x2a0</Data><Data Name='ProcessName'>C:\Windows\System32\services.exe</Data><Data Name='IpAddress'>-</Data><Data Name='IpPort'>-</Data><Data Name='ImpersonationLevel'>%%1833</Data><Data Name='RestrictedAdminMode'>-</Data><Data Name='TargetOutboundUserName'>-</Data><Data Name='TargetOutboundDomainName'>-</Data><Data Name='VirtualAccount'>%%1843</Data><Data Name='TargetLinkedLogonId'>0x0</Data><Data Name='ElevatedToken'>%%1842</Data></EventData><RenderingInfo Culture='en-US'><Message>An account was successfully logged on.

Subject:
 Security ID: S-1-5-18
 Account Name: XSIAM-WEC01$
 Account Domain: WORKGROUP
 Logon ID: 0x3E7

Logon Information:
 Logon Type: 5
 Restricted Admin Mode: -
 Virtual Account: No
 Elevated Token: Yes

Impersonation Level: Impersonation

New Logon:
 Security ID: S-1-5-18
 Account Name: SYSTEM
 Account Domain: NT AUTHORITY
 Logon ID: 0x3E7
 Linked Logon ID: 0x0
 Network Account Name: -
 Network Account Domain: -
 Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
 Process ID: 0x2a0
 Process Name: C:\Windows\System32\services.exe

Network Information:
 Workstation Name: -
 Source Network Address: -
 Source Port: -

Detailed Authentication Information:
 Logon Process: Advapi 
 Authentication Package: Negotiate
 Transited Services: -
 Package Name (NTLM only): -
 Key Length: 0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The impersonation level field indicates the extent to which a process in the logon session can impersonate.

The authentication information fields provide detailed information about this specific logon request.
 - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
 - Transited services indicate which intermediate services have participated in this logon request.
 - Package name indicates which sub-protocol was used among the NTLM protocols.
 - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.</Message><Level></Level><Task>Logon</Task><Opcode></Opcode><Channel>Security</Channel><Provider>Microsoft Windows security auditing.</Provider><Keywords></Keywords></RenderingInfo></Event> |
Question 4 :
Regarding the above questions, for log normalization parsing... which field (message/_raw_log) should be used?
If the "message" field is used, is it necessary to specify two parsing rules for the same event ID (4624)?
