siem-rule

Convert threat objectives into Sigma rules and cross-platform SIEM detection queries.

21|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/woohyun212/security-skill --skill siem-rule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: siem-rule
Source: https://github.com/woohyun212/security-skill/tree/main/siem-rule
Command: npx skills add https://github.com/woohyun212/security-skill --skill siem-rule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation and cross-platform conversion of SIEM detection rules from threat objectives, reducing duplication and handoffs across tools.

Core Features & Use Cases

  • Full lifecycle: define threat objectives, map log sources, write a platform-agnostic Sigma rule, and convert to Splunk SPL, Elastic KQL/EQL, and Microsoft Sentinel KQL.
  • Validation & tuning: test against sample data and document tuning recommendations to minimize false positives.
  • Use cases: build new detections from CVEs or threat reports, audit existing rules for coverage, and translate Sigma rules for rapid platform deployments.
  • End-to-end workflow supports endpoints, network, identity, and cloud detections.

Quick Start

Provide a detection objective and log sources, then generate a Sigma rule and convert it to Splunk SPL, Elastic KQL/EQL, and Sentinel KQL for validation.

Frequently Asked Questions about siem-rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Sigma rules to Splunk SPL, Elastic KQL, and Sentinel KQL?

You can convert Sigma rules to Splunk SPL, Elastic KQL/EQL, and Sentinel KQL by using Sigma CLI tooling with platform-specific backends, generating standardized detections from a single platform-agnostic rule.

What is the best way to build SIEM detection rules from threat reports or CVEs?

Building SIEM detection rules from threat reports or CVEs involves defining threat objectives, mapping log sources, writing a Sigma rule, and converting it to target platforms. This approach supports endpoints, network, identity, and cloud detections end-to-end.

Do I need Sigma CLI and Python3 to translate detection rules across SIEM platforms?

Yes, translating detection rules across SIEM platforms requires Sigma CLI tooling, backends for Splunk, Elastic, and Microsoft Defender, Python3, and jq, along with access to sample logs for validation and tuning.

Can I audit existing SIem rules for coverage using Sigma?

You can audit existing SIEM rules for coverage by mapping them back to threat objectives and validating against sample data, documenting tuning recommendations to minimize false positives across your deployed detection infrastructure.

How do I validate SIEM detection rules against sample logs to minimize false positives?

Validating SIEM detection rules against sample logs requires testing the generated queries in your target platforms and documenting tuning recommendations, ensuring the detections accurately map to threat objectives while minimizing false positives.

Does this approach support writing detections for cloud and identity log sources?

Yes, this approach supports writing detections for cloud and identity log sources, covering endpoints, network, identity, and cloud environments within an end-to-end workflow that maps threat objectives to platform-specific queries.