hunting-from-a-threat-intel-report
Operationalizes a threat intelligence report into hunts: extracting IOCs and TTPs,
v1.0.03 installazioni+3 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/hunting-from-a-threat-intel-reportScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchettoef4b4bd9…202bfbb7
ef4b4bd9da41…8cd2202bfbb74 file · 3.3 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-from-a-threat-intel-report@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When to Use
- You received a CTI report (vendor writeup, ISAC bulletin, IR report) and must operationalize it.
- You want to convert narrative TTPs and IOC lists into concrete hunts against your telemetry.
- You need to prioritize which indicators are worth hunting given they age at different rates.
Do not use an IOC blocklist as the whole engagement — atomic indicators (hashes, IPs) are trivially changed; durable value comes from hunting the behaviors (TTPs).
Prerequisites
- The report and a way to extract its IOCs and behavioral claims.
- Knowledge of your telemetry coverage to judge which TTPs are huntable.
Workflow
Step 1: Extract IOCs and TTPs
Pull atomic indicators (hashes, IPs, domains, URLs) and the behavioral TTPs (the report's "how"). Defang/normalize indicators for safe handling.
python scripts/analyst.py extract report.txtStep 2: Map to ATT&CK and the Pyramid of Pain
Tag behaviors with techniques and rank indicators by the Pyramid of Pain — prioritize TTPs and tools over hashes/IPs because they cost the adversary more to change.
Step 3: Check telemetry feasibility
For each TTP, confirm you have the data source to hunt it; note gaps as detection-engineering work.
Step 4: Build concrete hunts
Translate the high-value TTPs into queries (Sysmon, DNS, proxy, EDR), and sweep atomic IOCs as a quick first pass for current presence.
Step 5: Execute, document, and feed back
Run the hunts, record findings/gaps/negatives, escalate hits to IR, and convert durable logic into detections (Sigma).
Validation
- Both atomic IOCs and behavioral TTPs are extracted, not just the indicator list.
- Hunts target the highest-pain indicators feasible with your telemetry.
- Each TTP maps to a real data source or is logged as a coverage gap.
Pitfalls
- Stopping at IOC sweeps; the adversary rotates them and you miss the campaign.
- Hunting TTPs you have no telemetry for, producing false confidence.
- Failing to defang indicators, risking accidental execution/clicks.
References
- See
references/api-reference.mdfor the IOC/TTP extractor. - MITRE ATT&CK and the Pyramid of Pain (linked in frontmatter).
File di questa versione
references/11.0 KB
- api-reference.md1.0 KB
scripts/12.8 KB
- analyst.py2.8 KB
- LICENSE340 B
- SKILL.md3.1 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | ef4b4bd9 | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- 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
Altro in DFIR e threat hunting
Vai alla 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login