Q: After a security audit, you need to enforce password complexity and account lockout policies across all Linux servers. What mechanism controls this, and how do you configure it?
Linux uses PAM (Pluggable Authentication Modules) for authentication policy enforcement. PAM configuration files are located in /etc/pam.d/ and control how authentication, password changes, and session management behave.
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: "We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: PAM (Pluggable Authentication Modules), security hardening.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Linux uses PAM (Pluggable Authentication Modules) for authentication policy enforcement. PAM configuration files are located in /etc/pam.d/ and control how authentication, password changes, and session management behave.
- Password Complexity: Edit
/etc/pam.d/common-password(Debian) or/etc/pam.d/system-auth(RHEL) and add: - Account Lockout: Add to
/etc/pam.d/common-auth: - Password History: Prevent password reuse:
Remediation & Permanent Safeguards
Key configurations: This enforces minimum 12 characters with at least 1 digit, 1 uppercase, 1 lowercase, and 1 special character. This locks the account for 15 minutes after 5 failed login attempts.
password requisite pam_pwquality.so retry=3 minlen=12 dcredit=-1 ucredit=-1 ocredit=-1 lcredit=-1
- Password Complexity: Edit /etc/pam.d/common-password (Debian) or /etc/pam.d/system-auth (RHEL) an...
- Account Lockout: Add to /etc/pam.d/common-auth:
- Password History: Prevent password reuse:
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 audit 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 audit 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 audit 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 audit need
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).