Hi Rahul,
logtash was installed on a seperate server. Nothing was installed on QRadar. I did not even configured something. One logsource, the logtash server was automatically discoverd as "
Microsoft Windows Security Event Log" type .The events from the winlogbeat will be send to an elastic search data lake and will be imported with kafka and then send as syslog to qradar. So far we use the NSA Filter on logtash and have problems, because the events includes carrige returns \n and tabs \t. The Event IDs and categories are parsed correctly but a log of the rest looks a little funny.
The closest i could find as an guide was
From <https://www.ibm.com/docs/en/dsm?topic=log-installing-winlogbeat-logstash-windows-host>
Close because it assumes that winlogbeat sends the events directly from winlogbeat to Logtash. Maybe that is caused by the difference in the setup i use. Would be great if you share your experience and knowledge also. Especiallly if you have the problem with the extra symbols \t and \n as well and maybe a solution.
Regards
Martin
------------------------------
Martin Schmitt
------------------------------
Original Message:
Sent: Mon August 22, 2022 05:18 AM
From: rahul dhiman
Subject: windows log through wincollect has extra text
Hi Martin,
Thanks for your reply.
Yeah, logstash has very good options for removing unwanted fields and information from the log.
But I have never used logstash with Qradar.
so, have you installed logstash on Qradar ? I have recently started using ELK for the testing purpose so it would be great help if you can tell me how you are utilizing logstash with qradar.
Regards,
Rahul
Original Message:
Sent: 8/22/2022 4:45:00 AM
From: Martin Schmitt
Subject: RE: windows log through wincollect has extra text
Hi Rahul,
using Wincollect i totally agree to what Karl and Ralph wrote. If you are not set to collecting the events with wincollect have a look into other collection clients. I lately started integrating logbeat/logtash and the configuration possibilities i saw so far should accomodate what you want to achive.
------------------------------
Martin Schmitt
Original Message:
Sent: Wed August 03, 2022 04:22 AM
From: rahul dhiman
Subject: windows log through wincollect has extra text
Hi Community,
Hope you all are doing well.
From windows if you are collecting logs using wincollect a large number of the events have a sentence or two about the event itself at the end of the event. unnecessary and repetitive information and same message is always used for the same "EventCode" and Sometimes the extra text is quite long.
Is there any "feature" in wincollect with which we can turn off or stripping this extra information.
for example, every log with event id code 4624 contains below mentioned text that will be part of payload irrelevant of logon type triggered in the log:
"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."
I have raise a case with IBM but, though it would be great idea to open a discussion here on this portal as well.
Regards,
Rahul D
------------------------------
rahul dhiman
------------------------------