Get started →

OBSERVE · PRESERVE · CONTROL

Documentation

Guides, reference material, and technical information.

Choose a Hexrook collector

Filesystem, process, Registry and service observation: four collector families with explicit scope and platform boundaries.

DirLogger: filesystem integrity

DirLogger compares bounded filesystem observations against deliberately accepted baselines. Native identity, metadata, content hashing, declared coverage, verification sets and mounted-tree workflows support precise scope. Windows x64/local NTFS is the qualified reference profile. Linux ext3/ext4 and macOS acquisition work retain research boundaries.

ProcLogger: process evidence

The experimental Windows collector records bounded process samples, identity fields and per-field failures. Saved samples can be compared with explicit same-host/session assertions. Experimental watch journals combine retained capture input and periodic samples, with visible loss, interruption and unknown tails. Complete process history is not claimed.

RegLogger: Windows Registry configuration

Collect an explicitly selected key hierarchy and Registry view, retaining observed names, raw value types/bytes and available security metadata. The latest dev31 candidate also supports bounded broad collection when the target is empty, attempting loaded HKLM/HKU namespaces and 32/64-bit views. Access failures, mutations, refused links and collection budgets remain explicit. Compare compatible snapshots and run bounded watches; these are not atomic Registry snapshots or complete change histories.

SvcLogger: Windows services

Inspect selected service configuration, runtime status and accessible properties. In the latest dev31 candidate an empty target requests bounded broad service/driver collection, including actual accessible property reads. Discovery, omissions, access limits and incomplete tails remain visible. Correlate saved service/process observations under explicit host/boot assertions; incomplete visibility is not proof of deletion or continuous ownership.

Shared discipline, separate qualification

RegLogger and SvcLogger form the accepted dev29 development checkpoint; production qualification remains separate. Accepted Desktop is dev30 and the current 8 November update remains a dev31 candidate. DirLogger remains 2.0.0-dev28. Windows collection support does not imply native Linux/macOS collectors or GUI support there.

Need more help?Find guidance, platform details, and troubleshooting.
HEXROOK | PRIVACY · CONTROL · FREEDOMINDEPENDENT TOOLS FOR A MORE SECURE WORLD.