# Linux Artifacts

Linux forensic artifacts, indexed by the question each one answers.

Linux has fewer purpose-built artifacts than Windows and more that depend on configuration. Shell history, auditd and journald can answer a lot or almost nothing depending on settings applied long before the incident.

## Before you read the table

- Paths differ by family. Debian and Ubuntu log to /var/log/auth.log. RHEL and Fedora use /var/log/secure.
- journald is volatile by default on several distributions. Without Storage=persistent it lives in /run and does not survive a reboot.
- auditd records nothing without rules. Its silence describes the configuration, not the activity.
- syslog-style lines carry no offset. Find the host's zone before you build a timeline.

## Related

- [Linux Persistence Reader: auditd and systemd](https://www.cyberkit.win/tools/linux-persistence/?tab=audit-systemd)
- [Linux Case](https://www.cyberkit.win/drills/linux/)
- [Command Reference](https://www.cyberkit.win/reference/command-cheatsheet/)

Canonical: https://www.cyberkit.win/reference/linux-artifacts/

This is a static reference page. It does not collect anything.
