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
mukul975/generating-forensic-timelines-with-hayabusaDFIR e threat hunting

generating-forensic-timelines-with-hayabusa

⁨Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV/JSON timeline with severity levels, MITRE ATT&CK mappings, and per-host/per-Event-ID metrics. Use during DFIR triage to turn raw event logs into a fast, SIEM-free incident ti⁩

v1.03 installazioni+3 in 7 giorni36,3K StelleApache-2.0sincronizzato 12 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/generating-forensic-timelines-with-hayabusa

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

FirmaFirmato, ed25519
W+ajEgwmJd…Nsnn2ACw==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto0be90350…d754bf53
0be90350ce33…7452d754bf535 file · ⁦9.7 KB⁩
ScansioneMedio2 segnalazioni
  • Script eseguibile incluso nella skillscripts/agent.py
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/generating-forensic-timelines-with-hayabusa@54a7988

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

Overview

Hayabusa (隼, Japanese for "peregrine falcon") is a Sigma-based threat-hunting and fast-forensics timeline generator for Windows event logs, developed by Yamato Security in Rust. It parses .evtx files (offline or via live analysis of a local host), applies a large built-in library of Sigma detection rules plus Hayabusa-specific rules, and produces a single, readable, chronological timeline of high-signal events with severity levels, MITRE ATT&CK tactics, and rule references. This collapses thousands of raw event-log records into a prioritized incident timeline that an analyst can review quickly.

Hayabusa is purpose-built for DFIR triage. Instead of loading EVTX into a SIEM, an investigator runs a single binary against a directory of collected logs and gets a CSV or JSON timeline plus metrics (events per computer, per Event ID, per channel). Because detections are Sigma-based, coverage tracks the open detection-engineering community, and rules can be updated on demand with update-rules. The tool's output integrates with downstream analysis: CSV opens in Timeline Explorer, JSONL feeds into jq, and timesketch-* profiles export directly into Timesketch.

A frequent finding in Hayabusa timelines is malicious PowerShell — MITRE ATT&CK T1059.001 (Command and Scripting Interpreter: PowerShell) — surfaced via Sigma rules over Event ID 4104 (script-block logging), 4103, and Sysmon process creation. This skill maps to NIST CSF RS.AN-03 (analysis is performed to establish what has taken place during an incident).

When to Use

  • During incident-response triage, to turn a pile of collected .evtx files into a prioritized timeline.
  • When you need fast, SIEM-free detection over Windows event logs with community Sigma coverage.
  • To enumerate suspicious activity (PowerShell, account changes, lateral movement) across many hosts' logs.
  • To produce metrics (events per computer/Event ID/channel) and pivot keywords for deeper hunting.
  • To export an incident timeline into Timesketch or Timeline Explorer for collaborative analysis.

Prerequisites

  • Hayabusa binary. Download a pre-compiled release (Windows/Linux/macOS) from GitHub:
    bash
    # Linux example
    curl -LO https://github.com/Yamato-Security/hayabusa/releases/latest/download/hayabusa-3.0.0-lin-x64-gnu.zip
    unzip hayabusa-*.zip && cd hayabusa-*
    ./hayabusa-3.0.0-lin-x64-gnu --version
    Or build from source (rules are a submodule):
    bash
    git clone https://github.com/Yamato-Security/hayabusa.git --recursive
    cd hayabusa && cargo build --release
  • Collected Windows .evtx files (or run with --live-analysis on the host, as Administrator).
  • Updated detection rules:
    bash
    ./hayabusa update-rules
  • Optional: Timeline Explorer (Windows) or Timesketch for visualizing output; jq for JSONL.

Objectives

  • Build a CSV or JSON forensic timeline from a directory of .evtx files.
  • Update and tune the Sigma rule set used for detection.
  • Select an output profile appropriate to the investigation (minimal vs. verbose vs. timesketch).
  • Generate metrics (computer, Event ID, log) and pivot keywords for hunting leads.
  • Filter the timeline by minimum severity to focus triage.
  • Search logs for specific IOCs by keyword or regex.

MITRE ATT&CK Mapping

Technique ID Official Name Why Hayabusa Detects It
T1059.001 Command and Scripting Interpreter: PowerShell Sigma rules over Event IDs 4104/4103 and Sysmon flag malicious PowerShell
T1059.003 Command and Scripting Interpreter: Windows Command Shell Rules over process-creation events surface suspicious cmd usage
T1078 Valid Accounts Logon events (4624/4625/4672) reveal anomalous authentication
T1547.001 Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder Rules over registry-modification events flag persistence
T1053.005 Scheduled Task/Job: Scheduled Task Event ID 4698/106 rules surface task creation
T1003 OS Credential Dumping Rules flag LSASS access and credential-dumping patterns

Workflow

1. Update the rule set

Pull the latest Sigma and Hayabusa rules before every investigation.

bash
./hayabusa update-rules

2. Build a CSV timeline from collected logs

Point Hayabusa at a directory of .evtx files and write a CSV timeline. -w skips the interactive wizard for scripted runs.

bash
./hayabusa csv-timeline -d ./collected_evtx -o timeline.csv -w
# UTC timestamps for cross-host correlation
./hayabusa csv-timeline -d ./collected_evtx -o timeline_utc.csv -U -w

3. Choose an output profile

Profiles control detail. Use verbose to include MITRE ATT&CK tactics, tags, and the source rule/EVTX file; all-field-info to retain every original field.

bash
# Verbose: adds MITRE tactics, tags, rule file, evtx file
./hayabusa csv-timeline -d ./collected_evtx -o timeline_verbose.csv -p verbose -w
# Preserve all original event fields
./hayabusa csv-timeline -d ./collected_evtx -o timeline_full.csv -p all-field-info -w

Available profiles: minimal, standard (default), verbose, all-field-info, all-field-info-verbose, super-verbose, timesketch-minimal, timesketch-verbose.

4. Filter by minimum severity

Focus triage on the highest-confidence detections with -m/--min-level.

bash
./hayabusa csv-timeline -d ./collected_evtx -o critical.csv -m high -w

Levels: informational, low, medium, high, critical.

5. Produce a JSON/JSONL timeline for tooling

JSONL feeds cleanly into jq and downstream pipelines.

bash
./hayabusa json-timeline -d ./collected_evtx -L -o timeline.jsonl -w
# Example: top rule titles
jq -r '.RuleTitle' timeline.jsonl | sort | uniq -c | sort -rn | head

6. Generate metrics and pivot keywords

Summaries reveal which hosts and Event IDs dominate, and pivot keywords give hunting leads.

bash
./hayabusa computer-metrics -d ./collected_evtx -o computers.csv
./hayabusa eid-metrics -d ./collected_evtx -o eid.csv
./hayabusa log-metrics -d ./collected_evtx -o logs.csv
./hayabusa pivot-keywords-list -d ./collected_evtx -m medium -o pivots

7. Search logs for specific IOCs

Use the search command for keyword or regex hunting independent of detection rules.

bash
# Keyword search (case-insensitive) for a suspicious binary
./hayabusa search -d ./collected_evtx -k "powershell" -i
# Regex search for base64-looking PowerShell encoded commands
./hayabusa search -d ./collected_evtx -r "-[Ee]nc(odedCommand)?\s+[A-Za-z0-9+/=]{20,}"

8. Live triage on a running host

On the affected machine (Administrator), analyze local logs without exporting first.

bash
./hayabusa csv-timeline -l -o live_timeline.csv -m high -w

Tools and Resources

Tool Purpose Source
Hayabusa Sigma-based EVTX timeline/threat hunting https://github.com/Yamato-Security/hayabusa
hayabusa-rules Sigma + Hayabusa detection rules https://github.com/Yamato-Security/hayabusa-rules
Takajō Hayabusa results analyzer https://github.com/Yamato-Security/takajo
Timeline Explorer Review CSV timelines https://ericzimmerman.github.io/
Timesketch Collaborative timeline analysis https://timesketch.org/
Sigma Generic detection rule format https://github.com/SigmaHQ/sigma

Validation Criteria

  • Hayabusa binary installed and --version confirmed.
  • Rules updated with update-rules before analysis.
  • CSV timeline generated from the collected .evtx directory.
  • Appropriate output profile selected for the investigation goal.
  • Timeline filtered by minimum severity for triage focus.
  • JSON/JSONL timeline produced for downstream tooling where needed.
  • Computer/EID/log metrics generated.
  • Pivot keywords list produced for hunting leads.
  • Targeted IOC searches run with keyword/regex.
  • Findings (e.g., PowerShell T1059.001 detections) documented in the incident timeline.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
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/agent.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.013 nov 202654a79880be90350Firmata–

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