Getting started with Hexrook
Welcome to Hexrook. Choose a collector or Desktop workflow, then follow the evidence from observation to review.
- Choose your workflow
Observe filesystems, processes, Registry or services. Collector guide → Platform details →
- Prepare your evidence
Retain original observations and health. Keep filesystem evidence outside monitored roots.
- Observe deliberately
Choose explicit targets, limits and new outputs. Desktop or CLI workflows →
- Compare and review
Examine records, relationships and gaps. Baseline acceptance is a separate, deliberate decision.
Detailed guide and a filesystem example
Choose what you need to observe
Hexrook combines system observation, integrity monitoring and evidence analysis. DirLogger covers filesystems; ProcLogger covers sampled process observations and experimental journals; RegLogger and SvcLogger cover Windows Registry and service configuration, with selected scopes and bounded broad collection in the latest candidate. Each collector has its own scope and platform qualification.
Desktop or command line
The accepted Windows Desktop dev30 checkpoint inspects saved evidence. The dev31 candidate adds operational tasks, comparisons, profiles and process-journal workflows. The 8 November responsive update repairs measured table/report-publication stalls, improves grouped search and readable detail, and adds bounded broad Registry/service collection when targets are empty. Selected scopes remain available; partial visibility does not establish deletion or host cleanliness. Both release/debug builds passed ten-minute mixed-load guest checks. Desktop screenshots remain candidate previews; some advanced operations are CLI-only and no public binary release is implied.
Protect original evidence
Use protected evidence storage outside monitored filesystem roots. Keep observations, accepted baselines and queues in distinct files. New databases use the .hexrook extension; existing supported .sqlite and .db files remain readable when their embedded format is valid. Use new output destinations and retain incomplete records when an operation stops.
A filesystem example
For DirLogger's qualified Windows x64/local NTFS reference profile, inspect the target before choosing a baseline. Discovery does not enroll a target or authorize collection.
dirlogger_cli.exe --inspect-target C:/data --worker-timeout-ms 5000
dirlogger_cli.exe C:/data --save-baseline C:/evidence/data.hexrook --isolate-worker
dirlogger_cli.exe C:/data --verify-baseline C:/evidence/data.hexrook --isolate-worker
The initial save creates an accepted baseline and must be a deliberate decision. Verification does not advance it. DirLogger's exit 0 means unchanged, 1 means changed, and 2 means failed or unverified; other collectors use their own exit contracts.
Review coverage before conclusions
Read the observations together with health, scope, identities and any gaps. Missing events, denied properties and interrupted work are not evidence of a clean system. Hashes identify retained bytes; they do not authenticate an observer or prove a host uncompromised.