Skip to content
LinuxSystemCritical

systemd Journal (journald)

Binary, structured, indexed log store written by systemd-journald. Contains kernel ring buffer, dmesg, all unit (service) output, and authenticated metadata such as UID, GID, PID, command line, and SELinux context for every entry.

artifact_type: linux_journald

Where to find it

Default filesystem paths and registry locations. Collect these with your preferred live-response or disk-image tooling.

  • $/var/log/journal/
  • $/run/log/journal/
  • $/var/log/journal/<machine-id>/system.journal
  • $/var/log/journal/<machine-id>/user-*.journal

Forensic significance

Common scenarios in which this artifact becomes decisive evidence.

  • Recovering high-fidelity execution timeline on modern Linux hosts
  • Attributing a process to a real user via authenticated _AUDIT_LOGINUID
  • Correlating service crashes with privilege escalation attempts
  • Detecting log truncation — journal sealing keys can prove gaps

MITRE ATT&CK mapping

Techniques this artifact can help detect or substantiate. Click a technique to view the official MITRE entry.

Tools that parse it

unJaena AI and other DFIR tools commonly used to extract evidence from this artifact.

unJaena AI
journalctl
Plaso (log2timeline)
systemd-journal-remote

Related artifacts

References & further reading

Stop parsing artifacts by hand

unJaena AI ingests disk images, live-response output, and mobile backups, then automatically correlates every artifact on this page — and 200+ more — into an investigator-ready timeline.

Try unJaena AI