explaingit

manishrawat21/cisa-kev-threat-intel-orchestrator

Analysis updated 2026-05-18

21Audience · ops devopsComplexity · 4/5Setup · moderate

TLDR

An automated weekly pipeline that turns newly exploited CVEs from the CISA KEV catalog into ready to use Sigma detection rules for SOC teams.

Mindmap

mindmap
  root((repo))
    What it does
      Watches CISA KEV catalog
      Generates Sigma rules
      Sends weekly briefing
    Tech stack
      n8n
      Google Gemini
      Google Sheets
    Use cases
      Detection engineering
      Compliance evidence
      SOC automation
    Audience
      SOC analysts
      Detection engineers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Automatically generate draft Sigma detection rules for newly disclosed exploited vulnerabilities each week.

USE CASE 2

Build an audit trail showing how fast your team responds to new threats, useful for SOC 2 or ISO 27001 evidence.

USE CASE 3

Get a weekly email briefing summarizing new CVEs with draft detection logic for analyst review.

What is it built with?

n8nGoogle GeminiGoogle SheetsGmail/SMTP

How does it compare?

manishrawat21/cisa-kev-threat-intel-orchestrator0whitedev/detranspiler0xluk3/zk-resources
Stars212121
LanguagePython
Setup difficultymoderatehardeasy
Complexity4/54/51/5
Audienceops devopsdeveloperresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Requires n8n plus API keys for Google Gemini and Google Sheets access.

In plain English

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.

Copy-paste prompts

Prompt 1
Help me set up this n8n workflow to pull the CISA KEV catalog and generate Sigma rules with Google Gemini.
Prompt 2
Modify the Gemini prompt template in this project so generated Sigma rules also map to a specific MITRE ATT&CK tactic I choose.
Prompt 3
Show me how to change the email delivery step in this n8n pipeline so it posts the weekly briefing to Slack instead.
Prompt 4
Write test cases to validate the Sigma rules this pipeline generates before they reach an analyst.

Frequently asked questions

What is cisa-kev-threat-intel-orchestrator?

An automated weekly pipeline that turns newly exploited CVEs from the CISA KEV catalog into ready to use Sigma detection rules for SOC teams.

How hard is cisa-kev-threat-intel-orchestrator to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is cisa-kev-threat-intel-orchestrator for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.