Idea ID: 2874245

New log source support: WinCollect

Status : New Idea

One of our suppliers changed the solution they are collecting security logs from Windows. The new solution is called WinCollect (https://www.ibm.com/docs/en/qradar-on-cloud?topic=7-wincollect-overview). WinCollect transfers the Windows events into it's own format which is currrently not supported by ArcSight. As Windows security logs are an essential key stone for todays IT security we require the support of this log source.

New format: <13>Feb 17 15:33:58 example.host AgentDevice=WindowsLog            AgentLogFile=Security                PluginVersion=7.3.1.22  Source=Microsoft-Windows-Security-Auditing                Computer=example.host       OriginatingComputer=1.2.3.4       User=    Domain=                EventID=4624    EventIDCode=4624          EventType=8      EventCategory=12544    RecordNumber=1680885709                TimeGenerated=1645112027      TimeWritten=1645112027           Level=Log Always             Keywords=Audit Success Task=SE_ADT_LOGON_LOGON   Opcode=Info      Message=An account was successfully logged on.  Subject:  Security ID:  NULL SID  Account Name:  -  Account Domain:  -  Logon ID:  0x0  Logon Type:   3  Impersonation Level:  Impersonation  New Logon:  Security ID:  exampledomain\userName  Account Name:  userName  Account Domain:  exampledomain  Logon ID:  0x1BE6E99FF  Logon GUID:  {DB29D1D5-B757-CA09-0901-F40D472D8500}  Process Information:  Process ID:  0x0  Process Name:  -  Network Information:  Workstation Name: -  Source Network Address: 4.3.2.1  Source Port:  54935  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

Technical challenge: it was (for us) not possible to somehow integrate and reuse existing parser and pre-processors.

Tags:

Labels:

Connectors