March 2018 - syslog-ng - lists.balabit.hu

PCRE in patterndb with back substitution
by Evan Rempel 20 Mar '18

20 Mar '18

I have a case where an application logs something like {date} {host} {program}: my first line... ...my second line... ...and my third line. I want to make a correlation and unwrap these lines into {date} {host} {program}: my first line my second line and my third line. I started writing the patterndb to do this, but matching the ... at the end of the line is difficult, so I used @PCRE:line:(.*)\.\.\.$@ but I then need to only use the $1 to set a value <values> <value name="mymessage">$1</value> </values> Would this be the correct syntax to do this? Is there an easier way that would perform well? Thanks,

4 9

Re: [syslog-ng] Compression on input and output ?
by Nagy, Gábor 14 Mar '18

14 Mar '18

Hi Scot, I don't know about native compression abilities in syslog-ng. You could use TLS compression, but I don't know if that suits you. Other options would require that you write your compressing programs and include them in program source/destination or using unix sockets. Can you explain what is your use case, please? Maybe compression is not the goal, just the tool to achieve it and we can propose something else. Gabor On 13 Mar 2018 3:05 pm, "Scot" <scotrn(a)gmail.com> wrote: Hi, Has anyone looked at enabling compression between sources and destinations? Looks like Kafka is the only destination that supports compression by documentation. No inputs. Would be great to also compress between a syslog-ng relay and a syslog-ng target. Scot ____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product= syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq

3 3

Compression on input and output ?
by Scot 13 Mar '18

13 Mar '18

Hi, Has anyone looked at enabling compression between sources and destinations? Looks like Kafka is the only destination that supports compression by documentation. No inputs. Would be great to also compress between a syslog-ng relay and a syslog-ng target. Scot

1 0

One source multiple destinations ?
by Scot 10 Mar '18

10 Mar '18

I'm having a problem where I am trying to take input source(s) and write them out to multiple destinations. Before I go barking up the wrong tree I just wanted to make sure I wasn't missing something. We should be able to take a source and send it to file, elastic-search and SPLUNK and sumologic all at the same time right ? Troubleshooting an odd behavior where only one network destination will work but then I switch the order the other starts working. I know it's vague but has anyone seen this behavior? Thanks Scot

4 10

Rewrite syslog priority
by Kaleemulla Sharief (kasharie) 08 Mar '18

08 Mar '18

Hi, Is there support to change the syslog *priority* using rewrite? While I read it was not supported earlier but was planned for syslog-ng 3.2 (apologies if this is a wrong source), can someone help me with an example if it was added in any of the releases later ? Below did not work for me with syslog-ng 3.5.6 to change debug syslog to alert. filter f_syslogd1 { match("%OS-PCE-7-CSPF_FALLBACK") and priority(debug); }; rewrite r_rewrite_set{set("1", value("PRIORITY") condition(filter(f_syslogd1)));}; #Neither 1 without quotes log { source(s_syslog_514); rewrite (r_rewrite_set); destination(d_syslog); }; I am able to achieve this using the template hack something like below (changing to local7.alert=185) but the problem is while I can use the template inside destination definition, rewrite can be used under log section so that I can re-use same destination with different filters with or without rewrite, below will get applied to all syslogs to destination d_syslog which is not my requirement. How can I combine filters with template on same destination if rewrite is not supported. Appreciate any suggestions. template t_asm { template("<185> $DATE $HOST $MSGHDR$MSG\n"); template_escape(no); }; destination d_syslog {udp("server-001" port(514) spoof_source(yes) template(t_asm)); }; Regards ~ Kaleem

2 3

Re: [syslog-ng] Directory/file create ownership
by Dwijadas Dey 07 Mar '18

07 Mar '18

Add create_dirs (yes) in the options section. On 27-Feb-2018 2:24 PM, "Machiel Richards" <machiel.richards(a)gmail.com> wrote: Good day guys I am having an issue that I seem not be able to resolve thus far. I am fairly new to syslog-ng and have setup a new syslog server. We have managed to get most of our servers sending logs to the server without issues, however I am having trouble to get syslog-ng to create the directories and files with the correct ownership. We have a seperate user and group which it needs to create directories with, however it keeps on creating directories and files as root user. below is my current config : # First, set some global options. options { chain_hostnames(off); flush_lines(0); use_dns(yes); use_fqdn(yes); owner("syslog"); group("syslog"); perm(0640); stats_freq(0); bad_hostname("^gconfd$"); log_fifo_size(10000); }; source inputs { system(); internal(); unix-stream("/dev/log"); tcp(max_connections(50)); udp(); }; destination logpile { file("/var/log/HOSTS/$HOST/$YEAR/$MONTH/$FACILITY.$YEAR$ MONTH$DAY" owner("syslog") group("syslog") perm(0660) create_dirs(yes) dir_perm(0770)); }; log { source(inputs); destination(logpile); }; Can someone please assist me as any help would be appreciated. Regard -- I am a bomb technician...If you see me running, TRY TO KEEP UP! ____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/? product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq

5 8

Re: [syslog-ng] Cisco ASA parsing with patterndb/elasticsearch
by Scheidler, Balázs 05 Mar '18

05 Mar '18

Hi, Could you pls send a couple of messages? I would really like to make sure this works out of the box. Thanks On Mar 1, 2018 16:08, "Scheidler, Balázs" <balazs.scheidler(a)balabit.com> wrote: Can you give me a few inbound logs as received by syslog-ng? I would try to fix up cisco parser that it works for your use-case, as it should. Thanks On Feb 28, 2018 21:48, "Tim Ghetti" <tghetti(a)targetedsupport.com> wrote: I tried using the cisco-parser and not having any luck with that either. When I enable the parser, I actually stop seeing outbound traffic to elasticsearch. My config is below log { source { udp(flags(no-parse)); }; parser { cisco-parser(); }; destination { elasticsearch2( client-mode("http") cluster("ITESCL001") index("logstash-syslogng_${YEAR}.${MONTH}.${DAY}") cluster-url("http://192.168.101.199:9200 http://192.168.101.198:9200") type("syslog") flush-limit("1")); }; } [root@ITLOG001 conf.d]# tcpdump -nnSXi ens192 port 9200 -vv tcpdump: listening on ens192, link-type EN10MB (Ethernet), capture size 262144 bytes ^C 0 packets captured 0 packets received by filter 0 packets dropped by kernel *From:* syslog-ng [mailto:syslog-ng-bounces@lists.balabit.hu] *On Behalf Of *Scheidler, Balázs *Sent:* Tuesday, February 27, 2018 11:06 PM *To:* Syslog-ng users' and developers' mailing list < syslog-ng(a)lists.balabit.hu> *Subject:* Re: [syslog-ng] Cisco ASA parsing with patterndb/elasticsearch One additional feature you might be interested in is our cisco-parser() feature. It basically expects a flags(no-parse) input and then puts things in the right buckets, while recognising the various formats that cisco uses. It would be appreciated if you could check if it works with your setup and I can help fixing it up if it doesn't. The parser got added to recent syslog-ng versions, so you might need to upgrade to a new version. Bazsi On Feb 27, 2018 22:29, "Tim Ghetti" <tghetti(a)targetedsupport.com> wrote: Thanks!! It sounds like this is part of my problem. If you would be so kind as to send an example (or point me in the right direction) of how you are changing the program name and message body for the cisco logs that would be extremely helpful. I also suspect that there may be another issue. I’m almost certain that my parser should be picking up at least some of the logs but I am not seeing any of the fields in ES showing up based on parsed logs. Assuming that patterndb is working, would the below config be correct for getting patterndb parsed variables to show as fields in ES? destination d_elastic { elasticsearch2( client-mode("http") cluster("ITESCL001") index("logstash-syslogng_${YEAR}.${MONTH}.${DAY}") cluster-url("http://X.X.X.X:9200") type("syslog") flush-limit("1") ); }; *From:* syslog-ng [mailto:syslog-ng-bounces@lists.balabit.hu] *On Behalf Of *Evan Rempel *Sent:* Tuesday, February 27, 2018 9:06 PM *To:* syslog-ng(a)lists.balabit.hu *Subject:* Re: [syslog-ng] Cisco ASA parsing with patterndb/elasticsearch The program name will have an implied @ANYSTRING@ on the end, so if the syslog payload could be parsed to detect the program name of %ASA..... then your patterndb.xml would work. The problem is that they syslog payload can not be parsed. What we do is use a hand crafted patterndb to detect all of the different problem formats that Cisco logs (in our environment) and change a) the PROGRAM to be cisco_ASA or generally cisco_XXX where the XXX is the leading characters of the %XXX-#-##### of the syslog body. b) the MESSAGE to be %XXX-#-####... for the rest of the line. All of the poor hosts, sequence numbers, timestamps etc are all thrown away. After that, the internal buffers of syslog-ng contain a usable PROGRAM and MESSAGE such that we can use a patterndb to match the message part of the log line. This does mean that we have two patterndb parsers for every log line but it seems to work well for us. What would work better is if Cisco would fix their logging, but that isn't going to happen in my lifetime :-( I hope that makes sense. Evan. On 02/27/2018 05:37 PM, Tim Ghetti wrote: Ok, that makes sense. I sort of suspected that this was due to the program name not matching, since pdbtool works when specifying the program name. Do you know if there is a way to configure patterndb so that it matches the program name, regardless of the full program name with event code? Is it possible to regex the program or use the patterndb format i.e. <pattern>%ASA@ANYSTRING::@</pattern> or something similar? Tim *From:* syslog-ng [mailto:syslog-ng-bounces@lists.balabit.hu <syslog-ng-bounces(a)lists.balabit.hu>] *On Behalf Of *Evan Rempel *Sent:* Tuesday, February 27, 2018 8:26 PM *To:* syslog-ng(a)lists.balabit.hu *Subject:* Re: [syslog-ng] Cisco ASA parsing with patterndb/elasticsearch Welcome to the horrible world of Cisco logging :-( The issue you are bumping into is that when these log lines are parsed by syslog-ng (or any syslog daemon that does not specifically understand Cisco logs) there is no program name, or the program name is the full %ASA-4-106023 part of the log line. There are so many ways that Cisco can log incorrectly it is not possible to say without seeing your exact log lines. Cisco can add a * to the date/time stamp to indicate that there is no time server configured on the device. That makes the date/time invalid as far as parsing is concerned. Cisco can add a period (.) to the date/time stamp to indicate that there is a time server configured on the device, but the time server can not be reached. Again, this makes the date/time invalid as far as parsing is concerned. Cisco can add a sequence number at the start of the log line rather than starting the line with a date/6time stamp. Invalid parsing again. Cisco can leave out the sequence number but still include the trailing colon from the sequence number. You get the idea. So many ways to get it wrong, and they never get it right :-( Evan. On 02/27/2018 04:46 PM, Tim Ghetti wrote: Hi – having some trouble getting paterndb functional and looking for some help. I would like to use patterndb to parse my cisco ass firewall logs before sending it to elasticsearch. However when the messages get to elasticsearch, I don’t see the messages being parsed. Running pdbtool against the logs seems to work. # pdbtool match -p /etc/syslog-ng/patterndb.d/ciscoasa.pdb -P %ASA -f /var/log/asatest.log |more HOST=X.X.X.X MESSAGE=Built dynamic TCP translation from INSIDE:X.X.X.X/X to OUTSIDE:X.X.X.X/X PROGRAM=%ASA-6-305011 LEGACY_MSGHDR=%ASA-6-305011: .classifier.class=system .classifier.rule_id=e075efdc-c25f-5e49-a208-7661e3b5a29b Protocol=TCP GlobalIP=X.X.X.X GlobalPort=X LocalIP=X.X.X.X LocalPort=X TAGS=.classifier.system ********************** SYSLOG-NG CONF FILE @version: 3.11 source s_network { tcp(); udp(); }; destination d_elastic { elasticsearch2( client-mode("http") cluster("ITESCL001") index("logstash-syslogng_${YEAR}.${MONTH}.${DAY}") cluster-url("http://X.X.X.X:9200") type("syslog") flush-limit("1") ); }; destination d_catchall { file("/var/log/catchall.log"); }; filter f_ciscoasa { host("X.X.X.X"); }; parser p_ciscoasa {db-parser(file("/etc/syslog-n g/patterndb.d/ciscoasa.pdb"));}; log { source(s_network); filter(f_ciscoasa); parser(p_ciscoasa); destination(d_elastic); flags(final, flow-control); }; log { source(s_network); destination(d_catchall); }; ********************** PATTERNDB FILE <?xml version='1.0' encoding='UTF-8'?> <patterndb version='4' pub_date='2018-02-19'> <ruleset name='%ASA' id='a300d776-8bd7-834d-a4a9-23eb81a4b3ba'> <pattern>%ASA</pattern> <description> This ruleset covers the Cisco ASA firewalls </description> <rules> <rule provider="%ASA" id="b3de7699-8213-c744-944e-9413298afe86" class="system">  <patterns> <pattern>Teardown @ESTRING:Protocol: @connection for faddr @IPv4:SrcIP:/@@ESTRING:SrcPort: @gaddr @IPv4:GlobalIP:/@@ESTRING:GlobalPort: @laddr @IPv4:LocalIP:/@@ESTRING:LocalPort:@</pattern> </patterns> <examples> <example> <test_message program='%ASA'>Teardown ICMP connection for faddr X.X.X.X/X gaddr X.X.X.X/X laddr X.X.X.X/X</test_message> </example> </examples> </rule> <rule id='90d0f8c9-7591-d44e-b886-2f7e5cb17ce6' class='system' provider='%ASA'>  <patterns> <pattern>Teardown dynamic @ESTRING:Protocol: @translation from @ESTRING:::@@IPv4:LocalIP:/@@ESTRING:LocalPort: @to @ESTRING:::@ @IPv4:GlobalIP:/@@ESTRING:GlobalPort: @duration@ANYSTRING::@</pattern> </patterns> <examples> <example> <test_message program='%ASA'>Teardown dynamic UDP translation from any:X.X.X.X/X to outside:X.X.X.X/X duration 0:00:00</test_message> </example> </examples> </rule> <rule id='8f0a8d57-80c6-4745-8a8a-5ce018bb0d87' class='system' provider='%ASA'>  <patterns> <pattern>Teardown @ESTRING:Protocol: @connection @ESTRING:: @for @ESTRING:::@@IPv4:DstIP:/@@ESTRING:DstPort: @to @ESTRING:::@ @IPv4:SrcIP:/@@ESTRING:SrcPort: @@ESTRING::@</pattern> </patterns> <examples> <example> <test_message program='%ASA'>Teardown UDP connection 55101037 <(55)%20101%20037> for outside:X.X.X.X/X to inside:X.X.X.X/X duration 0:00:00 bytes 132</test_message> </example> </examples> </rule> <rule id='00c0732d-1e34-7340-a75f-21198bf71137' class='system' provider='%ASA'>  <patterns> <pattern>Built outbound @ESTRING:Protocol: @connection @ESTRING:: @for @ESTRING:::@@IPv4:DstIP:/@@ESTRING:DstPort: @(@ESTRING::)@ to @ESTRING:::@@IPv4:SrcIP:/@@ESTRING:SrcPort: @(@ESTRING::)@</pattern> </patterns> <examples> <example> <test_message program='%ASA'>Built outbound UDP connection 55101037 <(55)%20101%20037> for outside:X.X.X.X/X (X.X.X.X/X) to inside:X.X.X.X/X (X.X.X.X/X)</test_message> </example> </examples> </rule> <rule id='4a586711-ebe2-dc4d-bf6e-e512666d8c5d' class='system' provider='%ASA'>  <patterns> <pattern>Built inbound @ESTRING:Protocol: @connection for faddr @IPv4:SrcIP:/@@ESTRING:SrcPort: @gaddr @IPv4:GlobalIP:/@@ESTRING:GlobalPort: @laddr @IPv4:LocalIP:/@@ESTRING:LocalPort:@</pattern> </patterns> <examples> <example> <test_message program='%ASA'>Built inbound ICMP connection for faddr X.X.X.X/X gaddr X.X.X.X/X laddr X.X.X.X/X</test_message> </example> </examples> </rule> <rule id='8be7928d-66e7-7042-abd5-869d6b49c56e' class='system' provider='%ASA'>  <patterns> <pattern>Built inbound @ESTRING:Protocol: @connection @ESTRING:: @for @ESTRING::@@IPv4:SrcIP:/@@ESTRING:SrcPort: @(@ESTRING::)@ to identity:@IPv4:DstIP:/@@ESTRING:DstPort: @(@ESTRING::)@</pattern> </patterns> <examples> <example> <test_message program='%ASA'>Built inbound UDP connection 55101078 <(55)%20101%20078> for inside:X.X.X.X/X (X.X.X.X/X) to identity:X.X.X.X/X (X.X.X.X/X)</test_message> </example> </examples> </rule> <rule id='20aee256-b4f0-8b4d-93cb-263d5338fd21' class='system' provider='%ASA'>  <patterns> <pattern>Teardown @ESTRING:Protocol: @connection @ESTRING:: @for @ESTRING:::@@IPv4:SrcIP:/@@ESTRING:SrcPort: @to identity:@IPv4 :DstIP:/@@ESTRING:DstPort: @duration@ANYSTRING::@</pattern> </patterns> <examples> <example> <test_message program='%ASA'>Teardown UDP connection 55101084 <(55)%20101%20084> for inside:X.X.X.X/X to identity:X.X.X.X/X duration 0:02:01 bytes 88</test_message> </example> </examples> </rule> <rule id='e075efdc-c25f-5e49-a208-7661e3b5a29b' class='system' provider='%ASA'>  <patterns> <pattern>Built dynamic @ESTRING:Protocol: @translation from @ESTRING:::@@IPv4:LocalIP:/@@ESTRING:LocalPort: @to @ESTRING:::@ @IPv4:GlobalIP:/@@ESTRING:GlobalPort:@</pattern> </patterns> <examples> <example> <test_message program='%ASA'>Built dynamic TCP translation from any:X.X.X.X/X to outside:X.X.X.X/X</test_message> </example> </examples> </rule> <rule provider='%ASA' class='system' id='39'> <patterns> <pattern>Cleared @ESTRING:: @urgent flag from @ESTRING:::@ @ESTRING::/@@NUMBER::@ to @ESTRING: ::@@ESTRING::/@@NUMBER::@</pattern> <pattern>regular translation creation failed for @ESTRING:: @src @ESTRING:::@@ESTRING:: @dst @ESTRING: ::@@ESTRING:: @(type @NUMBER::@, code @NUMBER::@</pattern> </patterns> </rule> </rules> </ruleset> </patterndb> N�n�r��)em�h�yhiם�w^�� ____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product= syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq ____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product= syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq

2 1

syslog-ng 3.14 unofficial fedora / RHEL packages
by Czanik, Péter 05 Mar '18

05 Mar '18

Hi, My unofficial syslog-ng packages for Fedora & RHEL/CentOS 7 are now available. syslog-ng now compiles and works fine on Fedora 27, 28, Rawhide and RHEL 7. Note that as the bundled amqp and mongodb libraries do not compile with openssl 1.1, these features are disabled on all Fedora releases. TCP wrapper support was removed from Fedora and thus also from my packages. All of these are still enabled on RHEL. I hope to spare some time for RHEL 6 packages and make those available later this week. Packages are available at https://copr.fedorainfracloud.org/coprs/czanik/syslog-ng314/ Bye, Peter Czanik (CzP) <peter.czanik(a)balabit.com> Balabit / syslog-ng upstream https://syslog-ng.com/blog/author/peterczanik/ https://twitter.com/PCzanik

1 0

syslog-ng 3.14 unofficial openSUSE / SLES packages
by Czanik, Péter 05 Mar '18

05 Mar '18

Hi, My unofficial syslog-ng packages for openSUSE & SLES are now available. I changed tons of things in packaging (got rid of SLES 11 / sysvinit support) and thus simplified it greatly. It works perfectly for me, but that's a single environment, so any feedback is greatly appreciated. syslog-ng now compiles and works fine on openSUSE Leap, Tumbleweed and SLES 12. Note that as the bundled amqp and mongodb libraries do not compile with openssl 1.1, these features are disabled for Tumbleweed (and will be disabled also for SLES/Leap 15). I started to work on SLES 15 support, but due to some dependency problems that's not yet available. Packages are available at https://build.opensuse.org/project/show/home:czanik:syslog-ng314 Bye, Peter Czanik (CzP) <peter.czanik(a)balabit.com> Balabit / syslog-ng upstream https://syslog-ng.com/blog/author/peterczanik/ https://twitter.com/PCzanik

1 0

syslog-ng 3.14 on FreeBSD
by Czanik, Péter 05 Mar '18

05 Mar '18

Hi, As you can see on Freshports ( https://www.freshports.org/sysutils/syslog-ng314/ ) syslog-ng 3.14 is available now in the FreeBSD ports. Please test it and let us know if you run into any problems with it. We plan to update the syslog-ng metaport to version 3.14 later this week if no blocking problems are found. Thanks for your feedback! Bye, Peter Czanik (CzP) <peter.czanik(a)balabit.com> Balabit / syslog-ng upstream https://syslog-ng.com/blog/author/peterczanik/ https://twitter.com/PCzanik

1 0