logstash-modsecurity | Logstash configuration filter set framework to parse

logstash-modsecurity is a Shell library. logstash-modsecurity has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This example (working) configuration file has been used as the basis to process millions of ModeSecurity audit logs with lots of different variance in regards to which A-K sections are present. At a minimum this is a good starting point to start tackling a complex log format and you can customize it to you needs. Also note that ModSecurity Audit logs can definately contains some very sensitive data (like user passwords etc). So you might want to also take a look at using Logstash’s Cipher filter to secure certain message fields in transit if you are sending these processed logs somewhere else: [You should not need to, however IF you go ahead and EDIT the custom ruby filter blocks, please be aware of as if you introduce any error into the custom ruby blocks, one single error for one event, will take down the whole pipeline. This config file for whatever reason will not run if you try to add the "-- web" option onto the logstash flat jar. This has been reported to the developers. Recommend you run this without the "-- web" option and just hook up Kibana separately. Also recommend you start logstash like "java -jar logstash-x.x.x-flatjar.jar agent -v -f /yourConf.conf" The "-v" will give verbose output and help you debug issues. Also DON’T run in "-v" mode in a prod environment as you will end up outputting a ton of data to your console and/or logstash stdout capture file. (if you have one).