Q: After a security breach, you need to audit all file access and command execution on a Linux server. What kernel-level auditing framework is available, and how do you set it up?
The Linux Audit Framework (auditd) is a kernel-level subsystem that records system calls, file access, and user actions for security compliance and forensics.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In an interview, I explain my systematic Linux troubleshooting methodology using Brendan Gregg's USE method. The interviewer is testing: Linux Audit Framework (auditd), security forensics.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
The Linux Audit Framework (auditd) is a kernel-level subsystem that records system calls, file access, and user actions for security compliance and forensics.
- Install and enable:
- Add audit rules in
/etc/audit/rules.d/audit.rules: - Load rules:
augenrules --load
Remediation & Permanent Safeguards
Setup: The audit log is stored in /var/log/audit/audit.log and can be forwarded to a SIEM (like Splunk or ELK) for centralized analysis. For compliance standards like PCI-DSS or SOC2, auditd is often a mandatory requirement.
yum install audit
systemctl enable --now auditd
- Search audit logs:
- Install and enable:
- Add audit rules in /etc/audit/rules.d/audit.rules:
- Load rules: augenrules --load
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring security breach need SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring security breach need
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring security breach need Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring security breach need
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).