The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Logstash-patterns-core Alternatives
Similar projects and alternatives to logstash-patterns-core
-
Apache Log4j 2
Apache Log4j 2 is a versatile, feature-rich, efficient logging API and backend for Java.
-
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/
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
ysoserial
A proof-of-concept tool for generating payloads that exploit unsafe Java object deserialization.
-
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
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
elastic-stack-eh-muito-pratica
Projeto criado para exemplificação em dojo sobre a Stack Elastic para mostrar a simplicidade do uso da mesma para monitoramento de logs e de recursos de uma máquina/ambiente docker.
logstash-patterns-core reviews and mentions
-
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.
-
A note from our sponsor - WorkOS
workos.com | 24 Apr 2024
Stats
logstash-plugins/logstash-patterns-core is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of logstash-patterns-core is Ruby.
Sponsored