Parsing Syslog for Cisco FirePower #3547
Replies: 2 comments 2 replies
-
A question: Why did you do this directly in the I made a partial parsing pipeline for Sophos UTM and made the syslog file direct the pipeline to my custom one based on certain parameters in de syslog message. However currently they're redirected on basis of the hostname of the syslog sender, which makes my config less dynamic as I would have hoped. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi.. trying to set this up..will this work with ASA that doesnt have firepower? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The below file allows parsing of Cisco FirePower / ASA access log and VPN log files. It could be a starting point to be adopted to local needs. In the bottom I've added the template definition for the fields.
It's been in testing for about 13 Million events per hour peak and seems to do its job. Comments, suggestions, and improvements are welcomed.
New version as of 2021-03-31. For changes see comments inline.
For a general how-to see #3175 .
/opt/so/saltstack/local/salt/elasticsearch/files/ingest/syslog
Index definitions for the new fields:
/opt/so/saltstack/local/salt/elasticsearch/templates/so/so-common-template.json
Beta Was this translation helpful? Give feedback.
All reactions