detection-rule-development
/detection-rule-development
Develop or review a detection rule (Sigma, YARA, KQL/SPL/EQL) for a specific behavior or threat, mapped to MITRE ATT&CK, with test cases and false-positive tuning. Use when building, porting, or reviewing detections from a TTP, IOC, or incident finding.
- Author
- jassics ↗
- Repository
- awesome-claude-security ↗
- Licence
- GPL-3.0
- Last repository change
- 07.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.08.2026, without references to retired models or APIs.
GPL-3.0, otwarta.
What it does and when to use it
Develop or review a detection rule (Sigma, YARA, KQL/SPL/EQL) for a specific behavior or threat, mapped to MITRE ATT&CK, with test cases and false-positive tuning. Use when building, porting, or reviewing detections from a TTP, IOC, or incident finding.
Original author description
Develop or review a detection rule (Sigma, YARA, KQL/SPL/EQL) for a specific behavior or threat, mapped to MITRE ATT&CK, with test cases and false-positive tuning. Use when building, porting, or reviewing detections from a TTP, IOC, or incident finding.
How it works
SKILL.md has no level-two headings · 40 lines, 265 words
SKILL.md preview
--- name: detection-rule-development description: >- Develop or review a detection rule (Sigma, YARA, KQL/SPL/EQL) for a specific behavior or threat, mapped to MITRE ATT&CK, with test cases and false-positive tuning. Use when building, porting, or reviewing detections from a TTP, IOC, or incident finding. --- # Goal A robust, documented detection rule that catches the intended behavior, is mapped to ATT&CK, has known false positives addressed, and is testable. # Aim high on the Pyramid of Pain Prefer detecting **TTPs/behaviors** over brittle atomic indicators (hashes, IPs). Behavior-based detections cost the adversary more to evade. Use IOC-based rules for fast wins, but pair them with behavioral coverage. # Steps 1. **Define what you're detecting** — the specific behavior/technique, the data source required (process creation, EDR telemetry, auth logs, DNS, etc.), and the ATT&CK technique ID(s). 2. **Confirm log/telemetry availability** — no rule works without the data; note the source and any onboarding gap. 3. **Write the rule** — in the target language (Sigma as portable source of truth; YARA for files/memory; KQL/SPL/EQL for the SIEM/EDR). Make the logic specific to the behavior, not incidental artifacts. 4. **Test** — true positives (does it fire on the behavior? use an emulation like Atomic Red Team) and false positives (what benign activity matches?). Tune to cut FPs without blinding the rule. 5. **Document** — ATT&CK mapping, data source, FP notes, severity, and response guidance for the analyst. # Output The rule (in the requested format) plus a metadata block: ATT&CK technique · data source · test cases · known FPs · severity · triage steps. Add to the detection library; track coverage with `detection-coverage-review`. # Notes A detection without a tuned false-positive story creates alert fatigue and gets muted — tuning is part of "done." Validate against real telemetry/emulation, not just by reading the logic. Map every rule to ATT&CK so coverage is measurable.
Versions
The database has no other skills named detection-rule-development.
Database snapshot: 13.11.2026 · package version da3ebf1984b1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100siem-detection
Engineer and audit SIEM detection rules — log source coverage, Sigma / KQL / SPL / Elastic query authoring, MITRE ATT&CK mapping, false-positive tuning, and detection-as-code workflows. Use when the user mentions 'SIEM,' 'detection engineering,' 'detection rules,' 'Sigma,'… - 100detection-engineering
Use this skill when the user says 'write a Sigma rule', 'Splunk SPL query', 'KQL hunting', 'detect LOLBins', 'alert tuning', 'detection as code'. Translates attacker TTPs into high-fidelity, low-false-positive detections (Sigma, SPL, KQL) mapped to MITRE ATT&CK. Defensive only.… - 98yara-l-authoring
Use when writing, reviewing, tuning, or converting Google SecOps (Chronicle) YARA-L 2.0 detection rules or search queries, including turning a threat description, ATT&CK technique, Sigma rule, or SPL/KQL query into YARA-L. - 100detection-engineering
Write, test and tune log detection rules as code: Sigma rules converted with sigma-cli to Splunk, Elastic or KQL, native SPL, KQL, EQL or ES|QL queries where Sigma does not fit, CI validation and sample-event tests, MITRE ATT&CK coverage mapping, cloud log sources (CloudTrail,… - 100sigma-detection-engineer
Turns a described threat behavior or log sample into a validated Sigma detection rule with MITRE ATT&CK mapping, false-positive notes and a test plan. Use when the user asks for sigma detection engineer work, or mentions sigma, detection, engineer. - 98engineering-detections
Build, test, and tune detection content — Sigma, YARA, Suricata, and EDR/SIEM queries — mapped to MITRE ATT&CK with explicit false-positive analysis and detection-as-code practices. Use when writing or reviewing a detection rule, converting IOCs or TTPs into alerts, measuring…