# Linux Persistence Reader

Read a crontab line, a systemd unit or an auditd record, and see what runs, when, and as whom.

On Linux, persistence usually comes down to three questions: what runs, when, and as whom. This page answers them for a crontab line, a systemd unit, or an auditd record.

## How to read it

In a systemd unit, read ExecStart and User first, then the WantedBy line that decides when it starts.

A cron line runs as the user whose crontab holds it, unless it sits in /etc/crontab or /etc/cron.d, where the sixth field names the user.

An auditd record splits across several lines with one serial number. Read them together, and compare auid with uid, since auid keeps the original login even after sudo.

## Tab by tab

### auditd and systemd

Open it: https://www.cyberkit.win/tools/linux-persistence/?tab=audit-systemd

An auditd record or a systemd unit is a list of terse fields where one or two matter. This annotates each field and points at the ones worth a second look.

In auditd, uid and euid are who the process runs as now. auid is the account that logged in, and the kernel keeps it across su and sudo. So auid=1000 uid=0 means user 1000 became root, and 1000 is the number that names a person.

An auid of 4294967295 means no login session at all: a daemon, a service, or something started outside a login.

In a unit file, ExecStart is the whole story, and ExecStartPre runs before it with the same privileges. A second command hidden there is easy to skip.

### Cron

Open it: https://www.cyberkit.win/tools/linux-persistence/?tab=cron

A cron expression is five fields, and a malicious one hides well in a crontab full of ordinary jobs. This reads one back in plain English, or builds one field by field.

Paste an expression, pick a common schedule, or switch to Build. The tool follows the crontab(5) grammar from cronie, a practical superset of POSIX that adds names and step values.

When both day-of-month and day-of-week are restricted, cron runs the job when either one matches, not both. That trap is the most common misread.

@reboot runs once when cron starts. It is a favorite for persistence because it never appears in a time-based review.

## Related

- [Linux Artifacts](https://www.cyberkit.win/reference/linux-artifacts/)
- [Linux Case](https://www.cyberkit.win/drills/linux/)
- [Terminal](https://www.cyberkit.win/drills/terminal/)

Canonical: https://www.cyberkit.win/tools/linux-persistence/

This runs in the browser. Nothing you enter is uploaded.
