building-a-threat-hunt-hypothesis
Frames a structured, testable threat-hunting hypothesis: grounding it in adversary
v1.0.03 instalações+3 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/building-a-threat-hunt-hypothesisGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote3c12b2a5…ec2abb13
3c12b2a5e082…d91aec2abb134 arquivos · 3.0 KBVarreduraMédio2 achados
- Script executável junto com a skillscripts/analyst.py
- Links para domínios externos
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/building-a-threat-hunt-hypothesis@da7600a
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
When to Use
- You are starting a proactive, hypothesis-driven hunt rather than responding to an alert.
- You need to turn a vague concern ("are we seeing living-off-the-land abuse?") into a testable, scoped statement with clear data requirements.
- You want a repeatable plan that produces either a detection, a gap, or a confident negative.
Do not use this as an incident-response trigger — if you already have a confirmed alert, pivot to investigation/IR, not hypothesis generation.
Prerequisites
- Knowledge of your environment's telemetry (EDR, Sysmon, proxy, DNS, auth logs) and retention.
- Familiarity with ATT&CK to anchor the behavior you intend to hunt.
Workflow
Step 1: Pick a behavior, not a tool
Anchor on an adversary behavior (an ATT&CK technique/sub-technique) you have reason to expect given your threat model, not a specific product alert.
Step 2: Write a testable hypothesis
Use the form: "If [actor behavior], then I expect to observe [evidence] in [data source]."
If an adversary uses WMI for lateral movement (T1047), then I expect to observe
wmiprvse.exe spawning command interpreters on hosts that do not normally do so,
in Sysmon process-creation (Event ID 1).Step 3: Map to data and logic
Confirm the data source exists and is retained, then define the concrete query/detection logic and what "normal" looks like (baseline) so anomalies stand out.
python scripts/analyst.py plan --technique T1047 --datasource "Sysmon EID1" --window 14dStep 4: Set scope and success criteria
Define the host/time scope, the threshold for "interesting," and the three possible outcomes: finding (→ IR), detection gap (→ engineering), or confident negative (documented).
Step 5: Record and hand off
Capture the hypothesis, queries, and outcome so it becomes a repeatable, version-controlled hunt — successful logic becomes a detection rule.
Validation
- The hypothesis is falsifiable and names a specific data source that actually exists.
- A baseline of "normal" is defined so results are interpretable.
- Each outcome has a defined next action (IR, detection engineering, or documented negative).
Pitfalls
- Hunting for a tool name instead of a behavior, missing variants.
- Writing a hypothesis you cannot test with available telemetry.
- No baseline, so every result looks suspicious (or nothing does).
References
- See
references/api-reference.mdfor the hunt-plan generator. - MITRE ATT&CK and the PEAK framework (linked in frontmatter).
Arquivos desta versão
references/11.1 KB
- api-reference.md1.1 KB
scripts/12.0 KB
- analyst.py2.0 KB
- LICENSE340 B
- SKILL.md3.4 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaArquivo · Script executável junto com a skillscripts/analyst.py
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v1.0.0 | 13 de nov. de 2026 | da7600a | 3c12b2a5 | Assinada | – |
Mais de meltedinhex
Tudo deste publicador- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
Mais em DFIR e threat hunting
Ver a categoria- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login