yeti VS PyMISP

Compare yeti vs PyMISP and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
yeti PyMISP
2 3
1,626 421
2.1% 1.9%
9.7 9.2
7 days ago 1 day ago
Python Python
Apache License 2.0 GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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

Posts with mentions or reviews of yeti. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-08-21.
  • Yeti: Organize observables, indicators of compromise, TTPs, and threats
    1 project | news.ycombinator.com | 17 Oct 2022
  • Ask HN: SIEM-like product with DNS as its data API?
    3 projects | news.ycombinator.com | 21 Aug 2022
    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?

PyMISP

Posts with mentions or reviews of PyMISP. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-13.
  • FLaNK Stack Weekly for 13 November 2023
    30 projects | dev.to | 13 Nov 2023
  • Get CrowdSec IOCs feed into MISP
    3 projects | /r/CrowdSec | 24 Sep 2022
    You might consider misp feed https://github.com/MISP/PyMISP/tree/main/examples/feed-generator, basically it’s the best way to collect IOCs and import them into a MISP instance. These feeds help to correlate IOCs without manually launching the MISP module every time for each IOC, this also reduce the workload on your API servers as the list is cached locally on the MISP and updated every day.
  • Ingesting IOCs in to CS from MISP
    4 projects | /r/crowdstrike | 13 May 2022
    If you're in Python, you can use PyMISP to login and get the new indicators, and then FalconPy to import them into your CrowdStrike tenant. (Basically the reverse of what the MISP-tools example is doing. You could start here and alter the logic.)

What are some alternatives?

When comparing yeti and PyMISP you can also consider the following projects:

sysmon-config - Advanced Sysmon ATT&CK configuration focusing on Detecting the Most Techniques per Data source in MITRE ATT&CK, Provide Visibility into Forensic Artifact Events for UEBA, Detect Exploitation events with wide CVE Coverage, and Risk Scoring of CVE, UEBA, Forensic, and MITRE ATT&CK Events.

MISP-QRadar-Integration - The Project can be used to integrate QRadar with MISP Threat Sharing Platform

rbldnsd - A small and fast DNS daemon especially made to serve DNSBL zones.

vimGPT - Browse the web with GPT-4V and Vimium

iocextract - Defanged Indicator of Compromise (IOC) Extractor.

clipea - πŸ“ŽπŸŸ’ Like Clippy but for the CLI. A blazing fast AI helper for your command line

SnitchDNS - Database Driven DNS Server with a Web UI

MISP-tools - Import CrowdStrike Threat Intelligence into your instance of MISP

IntelOwl - IntelOwl: manage your Threat Intelligence at scale

PaK-Stocks - Stocks

livegrep - Interactively grep source code. Source for http://livegrep.com/

draw-a-ui - Draw a mockup and generate html for it