During network security monitoring of a segmented cloud environment, an analyst receives an automated Network Intrusion Detection System (NIDS) alert indicating that an internal deception host (honeypot) has initiated outbound network connections toward an unknown external address. A team member suggests modifying network routing policies to use this honeypot host as an inline security filter for all outbound enterprise traffic to block unauthorized connections. Which of the following best explains why this recommendation represents a fundamental misunderstanding of network monitoring and deception controls?
- Honeypots are designed purely as threat intelligence and detective monitoring tools, not inline preventive traffic-filtering mechanisms.Answer
- BHoneypots function primarily as inline preventive controls that automatically sanitize and forward legitimate user traffic during an incident.
- CNetwork intrusion detection systems automatically reconfigure honeypots into corrective inline firewalls upon triggering high-severity alerts.
- DDeploying a Web Application Firewall rule on perimeter routers is the required primary mitigation to block outbound network IP connections from host machines.
Answer
Honeypots are designed purely as threat intelligence and detective monitoring tools, not inline preventive traffic-filtering mechanisms.
Deception technologies, such as honeypots, are specialized detective security controls placed in network environments to lure attackers, detect unauthorized access attempts, and capture threat intelligence. Because any traffic interacting with a honeypot is inherently suspicious, these assets are strictly isolated and monitored passively. They are not production gateways or inline filtering systems, and routing legitimate enterprise network traffic through them introduces severe security risks and operational degradation.
Step-by-Step Solution
Key Concept
Honeypot Functionality vs. Inline Defense Controls
Estimated Time:1m 30s