Skip to main content

Normalization & Parsing

Stay up to date with the latest & greatest

  • 41 Topics
  • 85 Replies
41 Topics
A
alekstaKnown Participant
asked in Normalization & Parsing
Change timestamp on incoming logs

Hi!I’ve several logs that comes in UTC timeformat. My timezone Is UTC + 2. Which mess things up when I perform querys, hunting, analyzing events and taking out reports.My log Exporters often send syslog in UTC timeformat, RFC-compliant behavior.Is It possible to apply any sort of Normalization Package for these incoming logs to fix this?Can I try with some querys that changes the log_ts & col_ts field to UTC +2 timezone? Instead of the default UTC timezone.Thanks

1012
A
3 months ago
U
Uwe PoliakNew Participant
asked in Normalization & Parsing
Windows Server DNS Query Log

Hi all,I have configured my windows 2022 dns server to log dns queries. We need those logs for security and possible forensic reasons. The configuration is done in Windows Event Manager as described in DNS Logging and Diagnostics | Microsoft Learn. We are using LPAgent to collect other logs from this server. The result is an etl file, which cannot be read from the eventlog with im_msvistalog configuration from LPAgent. etl cannot be read with the im_msvistalog plugin of LPAgent. I have read that there is an NXLOG EE plugin im_etw out there which should be able to handle this file type, but we do not have the NXLog Enterprise Subscription. Is there any other option to collect the dns query logs from the server and import them into LogPoint?Is ther e any the best practice to handle windows dns server query logs (without using NXLOG EE)?Kind regardsUwe

13233
Nils Krumey
LogPoint Team
5 months ago
A
Andre KurtzInspiring
asked in Normalization & Parsing
Problem adding McAfee ePo server via Syslog

We configured our McAfee ePO (5.10) server to send its logs to a syslog server and configured it in the LP accordingly. Yet, when using the “Test Syslog” Feature in McAfee ePO, the test failed. Nonetheless, we are receiving logs from the server, but they only contain gibberish. LP raw logs This is as far as i think not a problem with normalization, as a tcpdump also shows the log payload not being human readable.tcpdumpI already tried to change the charset min the log m,collection policy from utf_8 to iso8559_15 and ascii, to no avail.  I found following McAfee (KB87927)  document, which says:ePO syslog forwarding only supports the TCP protocol, and requires Transport Layer Security (TLS). Specifically, it supports receivers following RFC 5424 and RFC 5425, which is known as syslog-ng. You do not need to import the certificate used by the syslog receiver into ePO. As long as the certificate is valid, ePO accepts it. Self-signed certificates are supported and are commonly used for this

457312
A
6 months ago
G
Gökhan GökNew Participant
asked in Normalization & Parsing
Normalisation for Miliseconds

<123>2024-01-11T11:11:11.123Z hostnameI want to remove two fields from the above rohdaten using normalization, so to say. After normalization I should have the following fields:milliseconds=123log_ts=2024-01-11T11:11:11ZCan I do this in normalization (or signature)? If yes, can you write me the normalization/signature rule? This problem can be solved like this:| <<:int>><log_ts:datetime_m> <host:all>but I don't want that. I want to separate my fields at the beginning using normalization. 

440
G
7 months ago
R
Ronny KempeNew Participant
asked in Normalization & Parsing
WIndows Logs

We would like to send log files from a directory such as C:\Logs to our logpoint server.What needs to be entered in nxlog.conf?

2172
Kai Gustafson
8 months ago
Kai Gustafson
Kai GustafsonKnown Participant
asked in Normalization & Parsing
Nxlog configuration, dropping logs from local host on IIS

Hi,I can’t get this to work, maybe some of you have tried this before.The drop line below works fine syntax wise, but my goal are to get rid of 127.0.0.1 logs, and when i remove the “!” it fails.Help Are apprecieredeRegards Kai  <Input IIS1>    Module   im_file    File    "C:\\inetpub\\logs\\LogFiles\\W3SVC1\\u_ex*"    Exec if $MessageSourceAddress != "127.0.0.1" drop ();     ReadFromLast FALSE    Recursive TRUE    PollInterval  1    Exec     $FileName = file_name();    Exec if $raw_event =~ /^#/ drop();\       else\       {\        w3c->parse_csv();\    $EventTime = $EventTime - (2 * 3600);\        $SourceName = "IIS";\       }</Input>

360
Kai Gustafson
1 year ago
A
alekstaKnown Participant
asked in Normalization & Parsing
Re-parse an event for normalization (JSON-event)

Hi !Just a interesting question. I know that other SIEM vendors have problem with this. Maybe LogPoint have a good function for this. So I received a JSON-event that didn’t normalise, due to that no normalization-package was enabled. I enabled this after I received the event. So to my question. Is It possible to parse this event afterwards so that It gets normalized? Or do I have to wait for another event from the same logsource to see If this one gets normalized?

2446
A
1 year ago
Kai Gustafson
Kai GustafsonKnown Participant
asked in Normalization & Parsing
Have anyone tried to get logs from Kubernetes, maybee a best pratice.

I see that there are no Vendor Apps for Kubernetes, so normalization are maybee going to be written, but how do you get logs to Logpoint, are there a nativ way for this.I found that Auditing of logs are not default turned on, and if they are they only reside for 1 hour. Any one with some god advise in the matter ?Regards Kai

2202
Kai Gustafson
1 year ago
A
alekstaKnown Participant
asked in Normalization & Parsing
Windows SCCM send logs to LogPoint

Hi!I’m curious into how to collect logs from SCCM. Logs related to endpoint protection, virus alarms, quarantind threats etc.Found out that nxlog provides a configuration file for this. Missing some fields in the configuration file, example <Output out_syslog>. To point out the syslog dst. Microsoft System Center Configuration Manager :: NXLog DocumentationHas anyone any experience about this?Thankful for replies. 

5857
A
1 year ago
A
Anonymous
posted in Normalization & Parsing
Universal REST API Fetcher Release

Hi All,We are excited to share the release of the new Universal REST API Fetcher. The Universal REST API fetcher provides a generic interface to fetch logs from cloud sources via REST APIs. The cloud sources can have multiple endpoints, and every configured source consumes one device license.For more details, please see the links below:Help Center: https://servicedesk.logpoint.com/hc/en-us/articles/6047943636253-Universal-REST-API-FetcherDocumentation: https://docs.logpoint.com/docs/universal-rest-api/en/latest/ 

2281
Reinhard Vielhaber
1 year ago
A
alekstaKnown Participant
asked in Normalization & Parsing
Cisco Firepower logs not normalized

Hi!Been struggling with the normalization of Cisco Firepower logs, were I expect better normalization and a better enrichment. The syslog is configured from the Firepower Management Center.Everything should be correct in LogPoint were we’ve put in all the normalization policys for the log source. Compiled Normalizer:-  Cisco FirepowerNormalizer-  CiscoPIXASACompiledNormalizerNormalization Packages:- LP_Cisco Firepower​​​​​​​- LP_Cisco Fiirepower Management Center​​​​​​​- LP_Cisco Fiirepower Management Center v6_2​​​​​​​- LP_Cisco PIX/ASA Generic​​​​​​​- LP_Cisco PIXASAIs there any problem with the format syslog? Had the same issue with CheckPoint FW, but this got solved when we changed the format to CEF. Only the problem that Cisco Firepower only support the format syslog.Is there someone that has any tips on how to move on forward with this?

1742
A
1 year ago
2
24Solutions SupportNew Participant
asked in Normalization & Parsing
Multi line parser for Java applications.

Hi.We are trying to push multi-line logs to Logpoint, for example a stack trace.They are created by Java applications like Jboss, Tomcat and few more. Where we have some debug information in logs such as content of XML messages processes by the system etc.When such logs are displayed in Logpoint, we need to preserve the line breaks along with indentation to make them readable by a human.Can you please show a complete recipe on how to achieve that?I saw this topichttps://community.logpoint.com/normalization-parsing-43/multi-line-parser-147and understood that there are some pre-compiled normalizers which can be used, can you please explain how they gonna work and how exactly we need to: 1.  send logs to Logpoint 2. process logs in logpointIn order to be able to present properly formatted (line breaks and indentation)  logs for users who will look for the logs ? Thanks

3493
P
1 year ago
A
Anonymous
posted in Normalization & Parsing
CSV Enrichment Source v5.2.0 is now publicly available

Dear All, We are happy to share that we have released CSV Enrichment Source v5.2.0 publicly.The CSV Enrichment Source application enables you to use a CSV file as an enrichment source in LogPoint. The application fetches data feeds from a CSV file and enriches search results with the data. For further information, please visit the link below:https://servicedesk.logpoint.com/hc/en-us/articles/115003786109For detailed information about the implementation in Logpoint products, please refer to the articles below:Logpoint: https://docs.logpoint.com/docs/csvenrichmentsource/en/latest/ Director API: https://docs.logpoint.com/docs/csvenrichmentsource-for-director-console-api/en/latest/ Director Console: https://docs.logpoint.com/docs/csvenrichmentsource-for-director-console-ui/en/latest/ 

902
A
1 year ago
A
Anonymous
posted in Normalization & Parsing
Release of Universal Normalizer v5.0.0.

Dear All,We are excited to announce the public release of Universal Normalizer v5.0.0.Why is this great news? Universal Normalizer enables you to create Customer Compiled Normalizers for a range of supported log formats by yourself with just a few simple steps and no waiting time.   The supported log formats currently include:  JSON CSV XML CEF LEEF Key-value pair To read more about Universal Normalizer v.5.0.0., please follow the links below:Dowload: https://servicedesk.logpoint.com/hc/en-us/articles/8874831748253Documentation: https://docs.logpoint.com/docs/universalnormalizer/en/latest/#universal-normalizer    

1864
A
1 year ago
A
Anonymous
posted in Normalization & Parsing
Logpoint Agent Collector v5.2.3 available now

Hi All, The Logpoint Agent Collector v5.2.3 has been released publicly. For more information, please visit the links below. Release notes: https://servicedesk.logpoint.com/hc/en-us/articles/360020035977  Documentation: https://docs.logpoint.com/docs/logpoint-agent/en/latest/

3210
A
1 year ago
A
Anonymous
posted in Normalization & Parsing
Detecting devices that are not sending logs

Receiving logs is one of the cure features of having a SIEM solution but in some cases logs are not received as required. In our newest KB article, we are diving into how to monitor log sources using Logpoint alerts to detect no logs being received on Logpoint within a certain time range.To read the full article, please see the link below: https://servicedesk.logpoint.com/hc/en-us/articles/5734141307933-Detecting-devices-that-are-not-sending-logs- 

3640
A
2 years ago
A
Anonymous
posted in Normalization & Parsing
Understanding file_keeper Working and Configuration

The `file_keeper` service,  primarily used for storing raw logs and then forwarding them to be indexed by the `indexsearcher` is often used in its default configuration. However in some real life situations this might not be sufficient to deal with the type, and volume of logs being ingested into LogPoint, hence tuning is required. In our newest KB article, we´re gonna guide you through how exactly to do it.For more details, please read the full article on the link below: https://servicedesk.logpoint.com/hc/en-us/articles/5794306067101-Understanding-file-keeper-Working-and-Configuration

1080
A
2 years ago
A
Anonymous
posted in Normalization & Parsing
Release of CloudTrailv5.1.0

Dear all,We´re happy to share the public release of CloudTrailv5.1.0Please see the details on the link below:https://servicedesk.logpoint.com/hc/en-us/articles/360000219549

180
A
2 years ago
A
Anonymous
posted in Normalization & Parsing
New applications available with Logpoint v.7.1.0.

Hi All, We´re happy to share that we have released the following applications on the Help Center: Experimental Median Quartile Quantile Plugin v5.0.0  Help Center: https://servicedesk.logpoint.com/hc/en-us/articles/115003890489-Experimental-Median-Quartile-Quantile-Plugin Vulnerability Management v6.1.1:   Help Center: https://servicedesk.logpoint.com/hc/en-us/articles/360014082658 Lookup Process plugin v5.1.0:  Help Center: https://servicedesk.logpoint.com/hc/en-us/articles/115005632749-Lookup-Process-Plugin Logpoint Agent Collector V5.2.2  Help Center: https://servicedesk.logpoint.com/hc/en-us/articles/360020035977 Universal REST API Fetcher v1.0.0 Help Center: https://servicedesk.logpoint.com/hc/en-us/articles/6047943636253-Universal-REST-API-v1-0-0 All applications have been bundled in Logpoint v7.1.0 and are available out of the box.

750
A
2 years ago
A
Anonymous
posted in Normalization & Parsing
Common Issues in Normalized logs

Hi All,Our latest KB article discusses common issues where logs seem normalized ( both norm_id and sig_id are present), but some problems prevent them from being used in analytics.To read the full article, please follow the link below: https://servicedesk.logpoint.com/hc/en-us/articles/5830850414493-Common-Issues-in-Normalized-logs 

1020
A
2 years ago
A
Anonymous
posted in Normalization & Parsing
Resolving timestamp related issues in Normalization

Hi All,Sometimes we face an issue like an alert not being triggered or a dashboard widget not being populated. There could be many possible reasons. Among them, one is a huge time gap between log_ts and col_ts. In this article, we will be discussing some of the possible causes and sharing tips and tricks to solve this. Please see the link to the article below :) https://servicedesk.logpoint.com/hc/en-us/articles/4791434110877-Resolving-timestamp-related-issues-in-Normalization

650
A
2 years ago
A
Anonymous
posted in Normalization & Parsing
New in KB: Addressing delayed Logs and its uncertainty with /logpoint.

Hi All,We are delighted to share our latest KB article addressing the difference between two fields, log_ts (event creation time) and col_ts (event ingestion time in log point) in logs and how they can alter the expected behavior of logpoint service. You can access the article via the below link:https://servicedesk.logpoint.com/hc/en-us/articles/5348407972893-Delayed-Logs-and-its-uncertainity-with-LogPoint

1040
A
2 years ago
A
Andre KurtzInspiring
asked in Normalization & Parsing
PaloAlto PanOS 10 - Logs not normalized

Hello, since we replaced the PaloAlto firewall devices a couple of days ago (the old ones were running PanOS 9.1.7, the new ones are on 10.1.4) for one of our customers, none of the logs coming from the firewalls are normalized anymore (there are 1000s of logs in the repo, but doing a search query “ norm_id="*" “ shows no result). We are using the same policies (collection, normalization etc) as before, and the firewall admin says that they just migrated the configuration fromt ht eold to the new devices and can not see any changes regarding the log configuration settings. I already restarted all normalizer services, even rebooted the LP and completely recreated the device configuration. We are using the latest (5.2.0) PaloAlto Application plugin on LogPoint 6.12.2, and its details clearly state that PanPOS 10 is supported (Palo Alto Network Firewall – ServiceDesk # LogPoint). And taking a look at the raw logs, i can not see any differenc in the log format of PanOS 9 and 10.  However,

8329
Nils Krumey
LogPoint Team
2 years ago
markus.nebel@8com.de
markus.nebel@8com.deBrainy
asked in Normalization & Parsing
FortiMail Logs not Correctly Separated into Multiple Lines

We recently added a FortiMail appliance as a log source to one of our logpoints and now see an issue during collection and normalization.It seems that FortiMail is sending the log messages without separating the single messages with a newline or NULL-termination or something else. Thus the syslog_collector is reading from the socket until the maximum buffer length is exceeded.So we get a maximum length raw log message (10k characters, which then breaks in between a log message), which contains up to 30 or 40 single log messages, which are written one after the other. The normalizer then normalizes only the first message and discards the rest.Here a shortened example of how this looks like:550 <6>date=2022-06-20 time=07:24:11.992 device_id=[...]553 <6>date=2022-06-20 time=07:24:11.992 device_id=[...]479 <6>date=2022-06-20 time=07:24:11.992 device_id=[...]324 <6>date=2022-06-20 time=07:24:12.279 device_id=[...] Is there a way to resolve this issue? 

870
markus.nebel@8com.de
2 years ago
markus.nebel@8com.de
markus.nebel@8com.deBrainy
asked in Normalization & Parsing
EventHubs: Azure AD Identity Protection Timestamp Format

We recently noticed that some Azure EventHubs Applications (e.g. the Azure AD Identity Protection -> https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/overview-identity-protection) are setting the "time" field not in the ISO 8601 Datetime format, but in the "general date long time" format (see https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings#GeneralDateLongTime).Thus the month and day field seem to be mixed up in these cases, and e.g. events that were actually collected on 6th of april (according to col_ts) are sorted into the repos on 4th of june (because of the wrong log_ts).Also alert rules on these events are then triggering months later, when the accidentally wrongly sorted events slip into the current window of the search time range.The following screenshots shows how the timestamp format of the Azure AD Identity Protection differs from the usual ISO 8601 format.Do you know if it is somehow possible to

1082
markus.nebel@8com.de
2 years ago

Badge winners

Show all badges
Terms & ConditionsCookie settings