Case 44A6A8 · Blue team / DFIR · L3 Applied
Linux Host Forensics
- 01 Context
- 02 Mechanism
- 03 Lessons
What a strong answer covers
Try it out loud first. Then check yourself:
- Volatile first: processes, sockets (ss), /proc/<pid>/exe pointing to deleted binaries, and memory via AVML or LiME.
- Logs: auth.log or secure, journald, wtmp/btmp/lastlog, and auditd if enabled; attackers often truncate local copies.
- Persistence: cron, systemd units and timers, authorized_keys, /etc/ld.so.preload, PAM modules, shell profile scripts.
- Integrity: rpm -Va or debsums to find modified packaged binaries; build a timeline from ext4 timestamps including crtime.
- 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?