Built a self-hosted threat intel aggregator, finally cleaned it up enough to open source it
Source Reddit ThreatIntel
Discussion
This content describes an open-source self-hosted threat intelligence aggregator tool designed to collect, deduplicate, and correlate threat intelligence feeds from over 60 sources. It includes features such as IOC extraction, ATT&CK mapping, integration with asset inventories, and detection engineering capabilities. The tool can run locally or integrate with Azure environments and supports optional AI triage. It is not a vulnerability or exploit but rather a security tool release.
r/threatintel (opens in a new tab)u/3eandrews30 points0 comments
Been sitting on this since May, so figured I'd just put it out there. Basically I got tired of manually checking a dozen+ vendor blogs every morning to see if anything was actually relevant to what I run, so I built something that pulls from 60ish feeds (CISA, Talos, MSRC, SANS, the usual suspects), dedupes it, pulls out IOCs, and maps everything to ATT&CK so you're not just staring at a wall of blog titles.
The part I actually care about is the "your stack" thing, you tell it what EDR/cloud/SIEM/firewall you run and it filters down to what's relevant instead of dumping every CVE on earth on you. If you've got RunZero hooked up it goes a step further and actually checks your live asset inventory, so instead of "this affects Fortinet devices" you get "this affects 3 assets you actually have right now," which is the difference between reading a blog post and knowing you have a problem today.
Also has a whole detection engineering side if you're into that, you can import your own KQL/Sigma/SPL/YARA/Suricata rules, or if you're on Sentinel it'll sync and help tune your analytics rules. Everything that touches an actual rule gets run through a static gate + backtest before it's treated as good, and there's an audit log so you can see what's failing instead of just trusting it blindly.
Runs fully local with docker compose or you can point it at Azure/Entra if that's your environment already. Same code either way, just env vars.
Heads up before anyone asks, there's an AI triage piece that's optional, it's not required to run the thing and the basic tier has it off entirely. I worked in this space building it and I'm aware "AI powered security tool" is basically a meme at this point so no hard feelings if that's an instant close-tab for you, the core aggregation/dedup/ATT&CK mapping stuff works without it.
It's MIT licensed, repo's here if anyone wants to poke at it or tell me what's broken: Threat Intel Aggregator
Screenshots in the readme if you want to see it before cloning. Happy to answer questions, hear how it could be improved, or why it sucks