A system auditor observes that malicious encrypted TLS command-and-control (C2) traffic traversing an internal server VLAN went completely undetected by a newly installed Network Intrusion Detection System (NIDS) connected to a core switch SPAN port. The organization requires a security solution that can inspect host system calls, file integrity changes, and decrypted application memory buffers on critical servers without altering network physical cabling or introducing a single point of failure that causes latency on the switch hardware. Which solution should be implemented to fulfill these security and architectural requirements?
- Deploy a Host-based Intrusion Detection System (HIDS) directly on the critical target servers.Answer
- BReconfigure the core switch SPAN port to mirror Layer 2 Ethernet frames instead of Layer 3 IP packets so the NIDS can decode encrypted payloads.
- CRe-architect the NIDS into an inline Network Intrusion Prevention System (NIPS) directly on the core switch link to intercept and inspect encrypted packet headers.
- DModify the NIDS detection signatures to inspect TCP port 80 traffic instead of TCP port 443 traffic to bypass TLS encryption processing.
Answer
Deploying a Host-based Intrusion Detection System (HIDS) directly on the critical target servers provides local process, file integrity, and decrypted memory visibility without impacting network switch latency or introducing single-point-of-failure hardware topology dependencies.
Deploying a Host-based Intrusion Detection System (HIDS) directly on the target servers allows inspection of host system calls, unencrypted memory buffers, system logs, and file modifications. Because HIDS operates on the endpoint OS rather than inline on the physical network switch, it avoids introducing network latency or inline failure points while solving the network encryption visibility gap.
Step-by-Step Solution
Key Concept
HIDS vs NIDS/NIPS Visibility and Deployment Architecture