Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
noorqureshi/defense-forensicsDFIR y threat hunting

defense-forensics

⁨Deep forensic artifact analysis after triage — memory dumps (Volatility 3), disk and super-timelines (Plaso), PCAP (tshark), and Windows host artifacts (Zimmerman toolset) — with hashing and chain of custody. Load when an incident moves past first response into "prove what the attacker did on this i⁩

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-forensics

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
mLU/8oqCQP…Q6JspOAQ==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete4338fe33…62ec3f8a
4338fe3307b7…7a8562ec3f8a1 archivo · ⁦2.4 KB⁩
EscaneoBajo1 hallazgo
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-forensics@ee0e0c5

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

When it applies

Triage (defense-dfir-triage) has scoped the incident and you now hold preserved evidence — a memory dump, a disk image (E01/raw), a PCAP, or exported host artifacts — and must prove, artifact by artifact, what the attacker did: which process ran, what persisted, what left the network. This is deep analysis of dead-box/dead-disk evidence, not live first response.

Why it works

Attackers can delete logs, but memory, filesystem metadata ($MFT, USN journal), and packet captures retain artifacts the attacker never controlled. Parsing them with purpose-built tools reconstructs execution, persistence, and exfiltration even after the live system was cleaned — and hashing plus chain of custody makes the conclusions defensible.

Method

  1. Preserve before you parse. SHA-256 every image/capture, record timezone + acquisition command, work on a copy with the original read-only. Write chain-of-custody notes into your timeline as you go — every conclusion must trace back to an artifact path.
  2. Memory (Volatility 3) — situational awareness first, then chase anomalies:
    bash
    vol -f mem.dmp windows.info      # OS profile, build, timezone
    vol -f mem.dmp windows.pslist    # processes — unknown names, odd parents
    vol -f mem.dmp windows.netscan   # connections — beacons, lateral SMB/RDP
    vol -f mem.dmp windows.cmdline   # full command lines
    Follow with windows.malfind (injected code) and dlllist/handles on suspects; dump a suspicious PID (--pid <pid> --dump) for defense-malware-triage / reverse-eng-malware.
  3. Disk & super-timeline — run Plaso (log2timeline.py) over the image and filter around the known-bad window in Timeline Explorer; correlate $MFT, USN journal, Shimcache, Amcache, and Prefetch into one ordered view. Autopsy / FTK Imager for carving and deleted files.
  4. Windows host artifacts (Eric Zimmerman's toolset) — the execution/persistence core:
    • Execution: Amcache, Prefetch, BAM, Shimcache.
    • Persistence: Run keys, services, scheduled tasks, WMI subscriptions.
    • Logs: Security, PowerShell 4104 script-block, Sysmon — feed defense-log-analysis.
  5. Network (PCAP) — tshark conversation/protocol/DNS statistics first, then carve suspicious streams and export objects. Custom protocol payloads → reverse-eng-protocol; C2 implants → defense-malware-triage.
  6. Hand off — extract IOCs with confidence + provenance, map to ATT&CK, feed detections to defense-detection-sigma, and run reporting-evidence-review before the incident report.

Gotchas

  • Never analyze the original — one mount without a write blocker and the evidence is challengeable. Hash first, analyze a copy, re-hash after to prove nothing changed.
  • Timezone skew kills timelines — Volatility, Plaso, and event logs each default differently; normalize everything to UTC before correlating.
  • Wrong Volatility profile = garbage output — confirm windows.info before trusting pslist. Linux/macOS dumps need symbol tables (ISF) built for that exact kernel.
  • Prefetch proves execution happened, not who ran it — corroborate with logs/accounts.
  • Absent artifact ≠ absent activity — log clearing and timestomping are themselves findings; record gaps explicitly instead of reading them as "clean".
  • Raw IOCs can tip the attacker or leak victim data — grade and redact before sharing.

Verify success

A reviewable timeline (Time | Host | Artifact | Finding | Confidence | Evidence path) where every claim names the artifact that proves it, before/after analysis hashes match, and IOCs + ATT&CK mapping are ready for detection engineering and reporting.

References

Volatility 3 docs; Plaso/log2timeline; Eric Zimmerman's tools; SANS DFIR posters; NIST SP 800-86.


Portions adapted from reverse-skill by zhaoxuya520, MIT License.

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.10.14-ee0e0c513 nov 2026ee0e0c54338fe33Firmada–

Pregunta 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. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login