yeti
sysmon-config
Our great sponsors
yeti | sysmon-config | |
---|---|---|
2 | 1 | |
1,626 | 749 | |
2.1% | - | |
9.7 | 7.2 | |
7 days ago | 6 months ago | |
Python | PowerShell | |
Apache License 2.0 | GNU Lesser General Public License v3.0 only |
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.
yeti
- Yeti: Organize observables, indicators of compromise, TTPs, and threats
-
Ask HN: SIEM-like product with DNS as its data API?
Hello, author here. That's a database driven DNS server alright. (Bonus: it's got a web admin interface.) There are DNS implementations with various backends; that's kind of the point.
I'm not sure that a mainstream SQL database is really a good target for network telemetry and e.g. access logging artifacts. Not talking about a time stream database either. There is an architecture here, and it's predicated on not collecting "all the things" in a central place.
Example: In this model, a service / server you're monitoring might have a couple of Redis keys which get incremented every time there's a successful or unsuccessful login. Maybe there's a redis hashkey with fails for individual accounts too.
There might be a graph somewhere of the login / attempt rates. It would query the summary redis keys (via the DNS) once a minute (doing whatever it needs to keep historical datapoints for however long they're needed).
If the rate skyrockets, maybe the hashkey with account-level granularity is consulted but most of the time it wouldn't be.
There might also be a Zabbix alarm somewhere querying the same keys, and if a threshold setting is exceeded, then an alarm is sent.
It's pull, not push. It's easy enough to write something to make the periodic queries and post them to e.g. ElasticSearch and graph it with Kibana.
So the question concerns the SIEM part. Something like Splunk is married to its database (their pricing model is based on how much data you want to put into that database). Something like the Yeti Threat Intelligence Platform (TIP) (https://github.com/yeti-platform/yeti) comes with the ability to manage and orchestrate a large number of periodic or event-driven tasks and therefore has the capability to generate the periodic DNS queries; it's been a few years, but its graphing capabilities didn't compare to ELK when I looked at it.
There's a lot of overlap with SCADA as well. All of the necessary features I've mentioned can be assembled from open source projects.
Is there some SIEM, TIP or Ops product out there, with an active userbase, which has the periodic task capability, alarming, and graphing?
sysmon-config
What are some alternatives?
PyMISP - Python library using the MISP Rest API
ThreatIngestor - Extract and aggregate threat intelligence.
rbldnsd - A small and fast DNS daemon especially made to serve DNSBL zones.
SysmonTools - Utilities for Sysmon
iocextract - Defanged Indicator of Compromise (IOC) Extractor.
sysmon-modular - A repository of sysmon configuration modules
SnitchDNS - Database Driven DNS Server with a Web UI
cowrie - Cowrie SSH/Telnet Honeypot https://cowrie.readthedocs.io
IntelOwl - IntelOwl: manage your Threat Intelligence at scale
DFIRMindMaps - A repository of DFIR-related Mind Maps geared towards the visual learners!
MISP - MISP (core software) - Open Source Threat Intelligence and Sharing Platform
sysmon-config - Sysmon configuration file template with default high-quality event tracing