Case 44A6A8 · Blue team / DFIR · L3 Applied

Linux Host Forensics

Practise as: Deep diveLevel: L3 Applied
  1. 01 Context
  2. 02 Mechanism
  3. 03 Lessons
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Volatile first: processes, sockets (ss), /proc/<pid>/exe pointing to deleted binaries, and memory via AVML or LiME.
  2. Logs: auth.log or secure, journald, wtmp/btmp/lastlog, and auditd if enabled; attackers often truncate local copies.
  3. Persistence: cron, systemd units and timers, authorized_keys, /etc/ld.so.preload, PAM modules, shell profile scripts.
  4. Integrity: rpm -Va or debsums to find modified packaged binaries; build a timeline from ext4 timestamps including crtime.
  5. Lessons: shell history is easy to disable, so ship auditd/EDR telemetry off-box before you need it.

If the interviewer pushes back

  • A container on the host was compromised and then deleted. What evidence survives on the node, and where?

Go deeper

More Blue team / DFIR cards

All Blue team / DFIR cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09