Question

Difficulty: MediumMitigation Strategies and Enterprise Hardening Practices

A security analyst is reviewing audit findings for a Linux-based public web server operating within an enterprise DMZ. The audit report highlights that the web server daemon process currently runs under the root superuser account, exposing the entire host operating system to complete takeover if an application-level remote code execution vulnerability is exploited. Which of the following mitigation strategies represents the MOST effective host hardening control to resolve this security risk?

  1. Reconfigure the web daemon to execute under a dedicated, non-privileged service account with minimal filesystem access.Answer
  2. B
    Deploy an inline network intrusion prevention system (NIPS) to inspect and block incoming HTTP exploit payloads.
  3. C
    Implement continuous network microsegmentation to isolate traffic between the DMZ web server and internal databases.
  4. D
    Configure a high-interaction honeypot within the DMZ to redirect and filter malicious remote commands.

Answer

Reconfiguring the web daemon process to run under a dedicated, low-privilege service account with restricted system rights enforces least privilege and mitigates full host compromise.
Reconfiguring the application service to execute under a dedicated, low-privilege service account directly resolves the risk by enforcing the principle of least privilege. If an application flaw is subsequently exploited, the attacker's execution context is restricted to the limited privileges of that service account, preventing full operating system compromise.

Step-by-Step Solution

1
Analyze the reported vulnerability condition
Identified that the web server daemon process is running with superuser (root) privileges on the host OS.
Running services as root violates the principle of least privilege and allows any application exploit to grant immediate administrative control over the underlying operating system.
2
Evaluate potential host hardening and mitigation controls
Determined that changing the execution context of the service process to a restricted service account directly mitigates the privilege escalation risk.
Host process hardening limits the administrative blast radius if a process is compromised, ensuring attackers cannot easily access host credentials or system binaries.
3
Differentiate host-level controls from perimeter and network controls
Selected service account privilege reduction over network filtering and deception mechanisms.
Network controls (NIPS, microsegmentation) address transport and perimeter threats, whereas service account restriction directly hardens the vulnerable host environment.

Key Concept

Principle of Least Privilege and Process Hardening
Rate this question