1---2name: detection-engineering3description: Detection engineering skill for writing, testing, and tuning Sigma, YARA, YARA-L, Suricata, Snort, Zeek, KQL, SPL, EQL, Chronicle, and Elastic detection rules. Covers ATT&CK coverage mapping, telemetry gap analysis, false-positive tuning, detection-as-code pipelines, and validation with Atomic Red Team and Caldera. Use to design durable detections backed by tests.4metadata:5 source: https://skillmd.com/skills/masriyan/detection-engineering6---78# Detection Engineering910## Operating Rules1112- Start from a threat behavior, not a single IOC. Rules expire; behaviors persist.13- Every rule ships with: hypothesis, data source, ATT&CK mapping, false-positive notes, response action, and a test.14- Tune for analyst time, not raw event volume. A noisy critical is a broken critical.1516## Authoring Workflow17181. State hypothesis: actor, technique, observable, data source, confidence.192. Identify telemetry: process, file, registry, network, auth, cloud, email, identity, EDR fields.203. Draft rule in the platform's native DSL; keep selectors readable; comment non-obvious filters.214. Generate matched and unmatched test events; run in a dry-run pipeline.225. Validate with Atomic Red Team / Caldera tests; record true positive evidence.236. Tune: add allow-lists with reasons and review dates; never silently broaden.247. Ship with a runbook: triage steps, expected next queries, containment.2526## Coverage Strategy2728- Maintain a matrix of ATT&CK techniques × data sources × rule IDs × last-tested date.29- Track gaps as backlog items with prerequisite telemetry (e.g., enable Sysmon 1/3/10/11).30- Score detections on durability, fidelity, and response cost.3132## Output Contract3334- `rules/<platform>/<id>.yml` with metadata block.35- `tests/<id>/` with positive and negative pcaps, EVTX, or JSON.36- `coverage.csv`: ATT&CK × rule × status × last_validated.37- `runbooks/<id>.md`: analyst playbook.38- `release-notes.md`: what changed, why, expected volume delta.