Skip to content
LinuxSystemHigh

Linux Syslog

Plain-text system event log written by rsyslog or syslog-ng, recording kernel messages, daemon output, cron jobs, and (on older distros) authentication events. Standard format on Debian/Ubuntu and RHEL/CentOS systems without journald-only logging.

artifact_type: linux_syslog

Where to find it

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

  • $/var/log/syslog
  • $/var/log/messages
  • $/var/log/syslog.1
  • $/var/log/syslog.*.gz

Forensic significance

Common scenarios in which this artifact becomes decisive evidence.

  • Detecting kernel-level anomalies (OOM, segfaults, USB attach events)
  • Tracing daemon failures around the time of a known incident
  • Correlating cron job execution with file modifications
  • Spotting log gaps that suggest tampering or anti-forensic activity

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
Plaso (log2timeline)
Splunk
Logwatch
grep/awk

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