A network administrator needs to deploy a security device that inspects inbound HTTP and HTTPS traffic at the application layer and drops requests containing SQL injection signatures before they reach the web server. Which device should the administrator deploy?
A Web Application Firewall parses HTTP and HTTPS requests at Layer 7, matching payloads against SQL injection signatures and blocking them before they reach the web server. Unlike a network firewall, which filters only by IP address and port, a WAF satisfies the stem's requirement for application-layer inspection and signature-based dropping.
Why this answer
A Web Application Firewall (WAF) operates at Layer 7 and inspects HTTP/HTTPS requests for application-layer attacks like SQL injection, XSS, and command injection, dropping malicious requests before they reach the web server. It understands HTTP semantics (headers, parameters, cookies, bodies) and can apply signature-based and anomaly-based rules specifically tuned for web applications.
Exam trap
CND often tests the boundary between NIPS and WAF — candidates pick NIPS because it 'inspects traffic,' but only a WAF is designed to parse HTTP application-layer content and drop SQLi before it reaches the web server.
How to eliminate wrong answers
Option A is wrong because a NIPS inspects network traffic for protocol and exploit signatures at Layers 3–7 but is not purpose-built to parse HTTP application semantics like a WAF; it may miss obfuscated SQLi in POST bodies and lacks WAF-specific rule sets. Option B is wrong because a packet filtering router only examines Layer 3/4 headers (IP, port, protocol) and cannot inspect HTTP payloads at all. Option C is wrong because a traditional stateful firewall tracks connection state at Layers 3/4 but does not perform deep application-layer inspection of HTTP content, so SQL injection signatures pass through undetected.