GRYPHLOG // SINGLE-BINARY SERVER FLIGHT RECORDER

Who got in. What they ran. What they changed.

One 6.3 MB binary turns any Linux or Windows server into a tamper-evident flight recorder. Traces command parentage across sudo, keeps unified file diffs, correlates outage spikes to root causes, and generates SOC 2 CC6.1 & CC7.2 compliance evidence.

Install Standalone Agent CLI Reference (19 Commands) Documentation Hub

The Four Pillars of Server Flight Recording

01. Complete Session Attribution

Records human and service sessions across SSH, RDP, and console logins with origin IP, public key fingerprints, and session lifetime.

02. Command Lineage Across Sudo

Traces the full process tree via the Linux Netlink connector. Sudo, su, and subshells cannot hide who originally launched a process.

03. Unified Git-Style File Diffs

Know exactly what line changed in /etc or application configs with instant before-and-after diffs and attribution to the executing session.

04. Outage Metric Correlation

Automatically correlates CPU, memory, and disk spikes to preceding configuration edits so you identify root causes in minutes.

05 / COMPETITIVE MATRIX • ARCHITECTURAL COMPARISON

Where the extra infrastructure usually goes.

Most security and audit solutions assume you have a cluster team to run them. Gryphlog was built for teams who want answers right on the server without multi-node managers or heavy pipelines.

Capability Gryphlog Wazuh Splunk / Elastic
Infrastructure footprint None — single 6.3 MB binary Manager + indexer + dashboard Cluster or SaaS data lake
Session Attribution across sudo Automatic via Netlink connector Custom auditd rules Manual pipeline engineering
File changes as diffs Built-in git-style before/after diffs Opt-in (capped to 32KB) Not supported (raw logs)