CyberKit

systemd Journal

Also called journald, journalctl, /var/log/journal.

Structured, indexed binary log managed by systemd-journald on modern Linux.

What it is

The logging service of systemd that stores events as structured, indexed binary records under /run/log/journal (volatile) or /var/log/journal (persistent), queried with journalctl. Each entry carries rich metadata fields such as the unit, PID, UID, boot ID, and an optional cryptographic seal (FSS).

Where it lives

/var/log/journal/ (persistent, if the directory exists / Storage=persistent) or /run/log/journal/ (volatile, in-memory default)

Why it matters

On systemd distributions it consolidates kernel, service, and authentication events into one queryable source, letting an investigator filter by unit, boot, or time and tie a process back to the service that spawned it. Forward-secure sealing can also detect after-the-fact tampering of the journal.

In practice

journalctl _SYSTEMD_UNIT filtering tied an outbound-beacon process to a rogue systemd service that had been masquerading as an updater.

What to look for

  • Unit starts and stops for unfamiliar services.
  • SSH and sudo messages with exact timestamps.
  • Journal files rotated or vacuumed during the incident.

Common mistake

Assuming it persists across reboots. On some systems the journal lives only in memory by default.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • osquery Open source

    Exposes Linux and macOS system state as SQL tables you can query.

  • Velociraptor Open source

    Collects Linux artifacts such as logs, cron and shell history at scale. Our notes.

  • Falco Open source

    Watches system calls at runtime and alerts on suspicious behavior.

  • Wazuh Open source

    Collects Linux logs and checks file integrity on each host.

Read next

Sources