back to labs
Auditd: Watch Sensitive Files
MediumLinux Security20-30 minThe brief
Compliance requires an audit trail on changes to two sensitive files on this host. Read /root/case/assignment.env for the two paths (WATCH_A, WATCH_B) and the audit key you must tag them with (AUDIT_KEY). Add persistent auditd watch rules — the kind that live in /etc/audit/rules.d/ and load at boot — so that writes and attribute changes to both files are recorded under your assigned key. Grading reads the durable rules files (what auditctl loads and 'auditctl -l' would show), so the rules on disk are what must be correct.
What you'll do
- Add a persistent watch on the first sensitive file (write + attribute changes) tagged with the assigned key
- Add the same watch on the second sensitive file
- Use a rules.d file so the rules survive a reboot
Hands-on lab: you work on a real Linux box in your browser, graded on the machine's actual state.
