I believe that the fields you are looking for are likely in the XML, but not on the General tab in the Microsoft Event Viewer. There are certain fields that can appear in the XML that are not part of the forwarded event payload that is collected by the WinCollect. What is in the General tab should be what is in the event payload forwarded to QRadar.
------------------------------
Jonathan Pechta
QRadar Support Content Lead
Support forums: ibm.biz/qradarforums
jonathan.pechta1@ibm.com------------------------------
Original Message:
Sent: Wed April 05, 2023 05:12 PM
From: Kevin B
Subject: Missing Guid and Version Windows Event fields in WinCollect Sysmon payload?
I'm looking at a Wincollect Syslog payload for Windows Event 4624 and there appear to be some fields missing. If I look at the definition of Event ID: 4624 from Microsoft here: https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4624. The fields I can't account for are:
GUID (Provider node Attribute) - Sample value: {54849625-5478-4994-A5BA-3E3B0328C30D}
Version (Child node 'System' ) - Sample values: 0, 1, 2.
I need these values in my system of analysis but I can't seem to find them. Here's a sample Syslog message I am getting from WinCollect.
<13>Mar 14 13:31:13 ME1-ET.IIE AgentDevice=WindowsLog AgentLogFile=Security PluginVersion=WC.MSEVEN6.10.1.2.20 Source=Microsoft-Windows-Security-Auditing Computer=ME1-ET.IIE.INTERNAL.COM OriginatingComputer=10.197.3.122 User= Domain= EventID=4624 EventIDCode=4624 EventType=8 EventCategory=12544 RecordNumber=4417378 TimeGenerated=1678815033 TimeWritten=1378815033 Level=Log Always Keywords=Audit Success Task=SE_ADT_LOGON_LOGON Opcode=Info Message=An account was successfully logged on. Subject: Security ID: - Account Name: - Account Domain: - Logon ID: 0x0 Logon Information: Logon Type: 3 Restricted Admin Mode: - Virtual Account: No Elevated Token: Yes Impersonation Level: Impersonation New Logon: Security ID: MEIT\Svc Account Name: MonSvc Account Domain: MEIT.TEL.NET Logon ID: 0xAF5E3D4 Linked Logon ID: 0x0 Network Account Name: - Network Account Domain: - Logon GUID: {c0fi21c6-1233-f677-af6c-3e289f01739f} Process Information: Process ID: 0x0 Process Name: - Network Information: Workstation Name: - Source Network Address: 10.200.2.75 Source Port: 58457 Detailed Authentication Information: Logon Process: Kerberos Authentication Package: Kerberos 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.
Are these values in here somewhere? Do I need to enable something in WinCollect to report this information? Any help would be greatly appreciated.
------------------------------
Kevin
------------------------------