During a post-incident review, a security analyst discovers that an attacker who gained initial access through a compromised web application loaded a custom Loadable Kernel Module (LKM) to establish a rootkit and achieve kernel-level persistence on a production Linux server. Which host hardening practice provides the MOST effective mitigation to prevent unauthorized kernel module execution?
- Restricting module insertion after boot by locking kernel module loading via sysctl runtime parametersCevap
- BDeploying an inline network intrusion prevention system (NIPS) to monitor encrypted HTTPS application traffic
- CConfiguring perimeter firewall rules to block incoming SSH management access on TCP port 22
- DInstalling a high-interaction network honeypot to capture and inline-block malicious rootkit installation commands
Cevap
Restricting module insertion after boot by locking kernel module loading via sysctl runtime parameters is the most effective host hardening mitigation.
The correct option correctly identifies kernel parameter hardening as the direct technical mitigation for Loadable Kernel Module (LKM) rootkits. Disabling dynamic module loading via system configuration prevents any user space process—even those operating with root privileges—from inserting unverified code into kernel memory space after the system finishes booting.
Adım Adım Çözüm
Anahtar Kavram
Host Hardening and OS Kernel Security Controls