Library 88 pages PDF, Text Updated Nov 21, 2026

AuditD Field Guide

Threat hunting and investigation playbook for the Linux audit system

By Travis Coats

An 88-page playbook for finding attackers and investigating incidents with auditd. Look up your problem, turn to the play, and run commands that have been checked against the real tools.

The Linux audit system records what happens on your servers: every program started, every protected file touched, every login, and every attempt to switch auditing off. When something goes wrong, those records are often the only trustworthy account of what happened. The hard part is collecting the right records and getting answers out of them fast.

The AuditD Field Guide is a playbook built around the questions you actually ask during a hunt or an incident. "How do I see every command a person ran as root?" "How do I spot a reverse shell?" "How do I catch someone covering their tracks?" Find the question in the contents and turn to that play. Each play gives you the rule to put in place, the commands to run, real output with an explanation of what matters in it, and where to go next.

What's inside

  • 43 plays in six parts: get ready, read the record, search fast, hunt, investigate, and tune and protect
  • 19 hunting plays for common Linux attacker behavior: root commands, new accounts, brute force, sudoers and setuid changes, cron and systemd persistence, planted SSH keys, preload rootkits, kernel modules, droppers in /tmp, reverse shells, web shells, credential theft, ptrace injection, reconnaissance, crashes, log wiping and audit tampering
  • Investigation workflows for timelines, process trees, following one login session, preserving evidence, and analyzing logs on a clean machine
  • A complete hunting rule set, also included as a ready-to-use .rules file, with every rule tied to the play that uses it
  • Reference tables for every ausearch option and aureport report, record types, key fields, and a map from MITRE ATT&CK techniques to plays.

Every play starts with a play card showing the problem, what to look for, the ATT&CK technique and the rule key to search, so you can scan for the right play in seconds.

Every command and output sample was checked against audit 4.2.1 on Fedora. Everything also applies to RHEL, Rocky, Alma, Debian and Ubuntu, and differences between distributions are called out where they matter.

Who it's for:

  • Linux administrators who have auditd installed but have never had a rule set that records anything useful
  • Security analysts and threat hunters who need to find attacker activity on Linux hosts, with or without a SIEM
  • Incident responders who have to rebuild what happened on a compromised server and present it as defensible evidence
  • Blue teams and SOC staff who want detections mapped to MITRE ATT&CK
  • Anyone working to a compliance requirement (STIG, PCI DSS, OSPP) who wants auditing that helps with investigations too, not just a box ticked

You'll need: comfort with the Linux command line and sudo, and a Linux machine or VM to practice on. No prior auditd experience is required: Part 1 starts from installation.