logstash-patterns-core
elastic-stack-eh-muito-pratica
| logstash-patterns-core | elastic-stack-eh-muito-pratica | |
|---|---|---|
| 3 | 1 | |
| 2,160 | 0 | |
| -0.0% | - | |
| 0.0 | 1.8 | |
| about 1 year ago | over 3 years ago | |
| Ruby | ||
| 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.
elastic-stack-eh-muito-pratica
-
Ubiquiti Dream Machine Pro Syslog -> ELK via Logstash
Here is an example I made but using a custom log pattern being received by filebeat, but the grok usage is the same, in that case I add a patterns_dir property into grok input to specify where is the custom pattern I made.
What are some alternatives?
logstash-patterns - Grok patterns for parsing and structuring log messages with logstash
aegis4j - A Java agent that disables platform features you don't use, before an attacker uses them against you.
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
ysoserial - A proof-of-concept tool for generating payloads that exploit unsafe Java object deserialization.
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/
Apache Log4j 2 - Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
log4j-affected-db - A community sourced list of log4j-affected software