Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/collecting-volatile-evidence-from-a-suspect-hostReport e compliance

collecting-volatile-evidence-from-a-suspect-host

⁨Collects volatile evidence from a potentially compromised host in correct order of⁩

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/collecting-volatile-evidence-from-a-suspect-host

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
3TASNgMVie…i5tBhdDw==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettobc51d343…6c4d9e8e
bc51d343ead5…c8c76c4d9e8e4 file · ⁦3.2 KB⁩
ScansioneMedio2 segnalazioni
  • Script eseguibile incluso nella skillscripts/analyst.py
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/collecting-volatile-evidence-from-a-suspect-host@da7600a

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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.

bash
python scripts/analyst.py manifest ./collection --case IR-42 --host WS01

Step 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.md for the manifest helper.
  • RFC 3227 and NIST SP 800-86 (linked in frontmatter).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileSìSì
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
  2. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v1.0.013 nov 2026da7600abc51d343Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login