defense-detection-engineering
Build detections as a repeatable pipeline, not one-off alerts. Load for "improve our detections", "detection as code", "reduce false positives", "measure ATT&CK coverage", or turning a red-team finding into durable blue-team coverage. Complements defense-detection-sigma (the rule format).
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/defense-detection-engineeringWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package0b739fa1…1548c0c0
0b739fa19f36…2f501548c0c01 file · 1.4 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-detection-engineering@ee0e0c5
On this page
When it applies
You have alerts but no system: rules nobody trusts, unknown coverage, and detections that die on the next log-schema change. This is the lifecycle that turns "we should alert on X" into a tested, versioned, measured detection.
Why it works
Detections are software. Treating them as code — with a source of truth, tests, and a coverage metric — is what separates a SOC that improves from one that just accrues noise. ATT&CK gives a shared map so coverage and gaps are countable, not vibes.
Method
- Start from a threat, not a log: pick an ATT&CK technique relevant to your org (threat model or a red-team finding), and write the hypothesis of what it leaves behind.
- Find the telemetry: which data source actually records it (Sysmon 1/EDR process create, 4688, cloud audit log, Zeek). No telemetry → fix logging first; a rule on absent data is theatre.
- Author as code: write the logic in Sigma (see
defense-detection-sigma), store in git, one rule per behaviour, tagged with the ATT&CK ID. - Test both ways: fire the real behaviour (Atomic Red Team / a controlled repro) → it must alert; replay a benign baseline → it must stay quiet. Record both as the rule's test.
- Tune the funnel: measure alert volume; add
filter:for known-good; promote only high-signal rules to paging. Track FP rate per rule. - Measure coverage: map live rules to the ATT&CK matrix (DeTT&CT / a coverage sheet); the gaps are your backlog.
Gotchas
- Coverage counted by rule count lies — count techniques with a tested detection.
- Atomic tests that need cleanup can leave artifacts; run them in a lab, not production.
- A rule with no owner and no test is a future muted alert. Every rule needs both.
Verify success
Each detection has a passing "fires on attack / quiet on baseline" test, an ATT&CK tag, and an owner; the coverage map shows what's detected and what's a known gap.
References
MITRE ATT&CK & DeTT&CT; SigmaHQ; Atomic Red Team; Palantir "Alerting and Detection Strategy" framework.
Files in this version
- SKILL.md2.6 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 0b739fa1 | Signed | – |
More from NoorQureshi
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login