collecting-volatile-evidence-from-a-suspect-host
Collects volatile evidence from a potentially compromised host in correct order of
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/collecting-volatile-evidence-from-a-suspect-hostGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacotebc51d343…6c4d9e8e
bc51d343ead5…c8c76c4d9e8e4 arquivos · 3.2 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/collecting-volatile-evidence-from-a-suspect-host@da7600a
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
When to Use
- A host is suspected of compromise and you must capture state that disappears on reboot.
- You are performing live response before isolating or imaging the machine.
- You need an ordered, integrity-preserving collection for later analysis.
Do not use this as a substitute for full disk imaging when persistence matters — volatile collection complements, not replaces, a forensic image. And do not reboot before collecting.
Prerequisites
- Trusted, statically linked collection tools run from external media (not host binaries).
- Authorization to collect, and a destination on external/write-once media.
Safety & Handling
- Assume host tools are compromised; use your own trusted binaries to avoid rootkit deception.
- Hash every artifact at collection time and record actions for chain of custody; minimize changes to the host.
Workflow
Step 1: Follow the order of volatility
Collect most-volatile first (RFC 3227): CPU/registers and cache → RAM → network state and connections → running processes → logged-on users/sessions → open files/handles → then disk.
Step 2: Capture memory first
Acquire a full RAM image with a trusted acquisition tool before anything that alters memory; it is the richest and most perishable source.
Step 3: Snapshot network and process state
Record active connections, listening ports, ARP/DNS cache, running processes with command lines and parent links, and loaded modules.
python scripts/analyst.py manifest ./collection --case IR-42 --host WS01Step 4: Record users and handles
Capture logged-on users, sessions, scheduled tasks, and open handles/files.
Step 5: Hash, log, and hand off
Hash each artifact, write a collection manifest with timestamps, and transfer to the analysis environment preserving integrity.
Validation
- Artifacts are collected in order of volatility, memory first, before any reboot.
- Every artifact has a recorded hash and collection timestamp in the manifest.
- Trusted external tools were used; host changes are documented.
Pitfalls
- Rebooting or shutting down before capturing RAM, destroying the best evidence.
- Using the host's own (possibly trojaned) tools and trusting their output.
- No hashing/manifest, undermining evidentiary integrity.
References
- See
references/api-reference.mdfor the manifest helper. - RFC 3227 and NIST SP 800-86 (linked in frontmatter).
Arquivos desta versão
references/11.3 KB
- api-reference.md1.3 KB
scripts/12.3 KB
- analyst.py2.3 KB
- LICENSE340 B
- SKILL.md3.4 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Sim | Sim |
| 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 | bc51d343 | 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 Relatórios e compliance
Ver a categoria- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
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