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 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/defense-detection-engineeringEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete0b739fa1…1548c0c0
0b739fa19f36…2f501548c0c01 archivo · 1.4 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-detection-engineering@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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.
Archivos de esta versión
- SKILL.md2.6 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 0b739fa1 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Ingeniería inversa y fuzzing
Ver la categoríaPregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login