Analysis updated 2026-05-18
Automatically generate draft Sigma detection rules for newly disclosed exploited vulnerabilities each week.
Build an audit trail showing how fast your team responds to new threats, useful for SOC 2 or ISO 27001 evidence.
Get a weekly email briefing summarizing new CVEs with draft detection logic for analyst review.
| manishrawat21/cisa-kev-threat-intel-orchestrator | 0whitedev/detranspiler | 0xluk3/zk-resources | |
|---|---|---|---|
| Stars | 21 | 21 | 21 |
| Language | — | Python | — |
| Setup difficulty | moderate | hard | easy |
| Complexity | 4/5 | 4/5 | 1/5 |
| Audience | ops devops | developer | researcher |
Figures from each repo's GitHub metadata at analysis time.
Requires n8n plus API keys for Google Gemini and Google Sheets access.
This project automates a task that security teams normally do by hand: turning newly disclosed, actively exploited software vulnerabilities into detection rules. It watches the CISA Known Exploited Vulnerabilities catalog, a public list the US government keeps of security flaws that are already being used in real attacks, and checks it every Monday morning for new entries. When it finds a new vulnerability, the pipeline generates a Sigma detection rule for it. Sigma is a common format for describing how to spot an attack in system logs, and the rules produced here are meant to be dropped straight into tools like Splunk, Elastic, or Wazuh, which security teams use to monitor networks. Google Gemini writes each rule, guided by a prompt that pushes it to name the exact affected product, use the right Windows monitoring event types for the technique involved, add several filters to reduce false alarms, and tag the rule with the matching MITRE ATT&CK technique, a widely used catalog of attacker behaviors. Every processed vulnerability gets logged to a Google Sheet, creating a timestamped record of when each flaw was disclosed and when a detection rule became available for it. This kind of audit trail is useful for teams that need to show compliance with standards like SOC 2 or ISO 27001, which ask organizations to prove they respond promptly to new threats. The pipeline also emails a weekly summary to analysts, listing the new vulnerabilities, their severity, and draft detection logic ready for review. The whole system runs on n8n, a workflow automation tool, connected to the CISA KEV API, Google Gemini, Google Sheets, and email. The author describes it as a working weekly pipeline rather than a finished product. Planned improvements include sending generated rules directly into a security team's monitoring system instead of only by email, testing generated rules against sample logs before analysts see them, and connecting the pipeline to incident response systems. This is a solo project built by an independent detection engineer and SOC analyst, aimed at cutting the multi hour manual process of writing a detection rule per vulnerability down to near zero.
An automated weekly pipeline that turns newly exploited CVEs from the CISA KEV catalog into ready to use Sigma detection rules for SOC teams.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.