logstash-patterns-core
logstash-patterns
| logstash-patterns-core | logstash-patterns | |
|---|---|---|
| 3 | 4 | |
| 2,160 | 233 | |
| -0.0% | 0.0% | |
| 0.0 | 2.1 | |
| about 1 year ago | about 1 year ago | |
| Ruby | Python | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
logstash-patterns-core
-
Log4j 2.15.0 – Previously suggested mitigations may not be enough
Logstash is a hugely popular service for collecting/processing/shipping logs, mainly associated with elasticsearch ("ELK") but has lots of output plugins. It uses log4j, so if one of the log events it was processing contained an exploit string, and also caused logstash to encounter an error processing or shipping the message, that message would get logged to logstash's own log, thus triggering the exploit deep in someone's infrastructure.
probably not too hard to come up with a way to break one of the many "grok" pattern regexes https://github.com/logstash-plugins/logstash-patterns-core/b...
-
Writing an effective GROK pattern
Logstash ships with 120 default patterns. You can find here: https://github.com/logstash-plugins/logstash-patterns-core/tree/master/patterns
-
Ubiquiti Dream Machine Pro Syslog -> ELK via Logstash
You can see all the Grok regexp preset here.
logstash-patterns
- Grok filter working in online debuggers but not in actual implementation
-
A portable, modern regular expression language
Why don't languages have grok patterns in their standard libraries?
It seems to only exist in log parsing ecosystems but this really helps with getting rid of little bugs and wrong parsing of specific regex patterns.
Instead of doing "^\d+(\.\d+){3}$" for IP checking which is clearly wrong, you'd do "%{IPV4:ip}" which is so much better.
List of known patterns : https://github.com/hpcugent/logstash-patterns/blob/master/fi...
Even for PHP a third party library only has 15 stars.
-
Dissect pattern help
in case you haven't, it can be found here. https://github.com/hpcugent/logstash-patterns/blob/master/files/grok-patterns
-
Writing an effective GROK pattern
Also, some of the patterns can be referred from https://github.com/hpcugent/logstash-patterns/blob/master/files/grok-patterns I personally prefer the above link for constructing grok pattern.
What are some alternatives?
aegis4j - A Java agent that disables platform features you don't use, before an attacker uses them against you.
JSVerbalExpressions - JavaScript Regular expressions made easy
log4shell-tools - Tool that runs a test to check whether one of your applications is affected by the recent vulnerabilities in log4j: CVE-2021-44228 and CVE-2021-45046
rx - Standalone version of Emacs' rx macro
ysoserial - A proof-of-concept tool for generating payloads that exploit unsafe Java object deserialization.
common-regex - Most common regex
lunasec - LunaSec - Dependency Security Scanner that automatically notifies you about vulnerabilities like Log4Shell or node-ipc in your Pull Requests and Builds. Protect yourself in 30 seconds with the LunaTrace GitHub App: https://github.com/marketplace/lunatrace-by-lunasec/
kbnf - KBNF has been renamed to Dogma
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
fluent-plugin-grok-parser - Fluentd's Grok parser
log4j-affected-db - A community sourced list of log4j-affected software