Prompt
What should I use for request filtering at the network edge?
Latest observation
Nov 1, 2026
OpenAI APIWeb search: off
At the network edge, the usual choices are:
-
WAF (Web Application Firewall) for HTTP/HTTPS traffic
- Best for filtering web requests
- Protects against common app-layer attacks like SQL injection, XSS, bad bots, etc.
- Often implemented with CDN or reverse proxy services
-
Firewall / NGFW for general network traffic
- Best for allowing/denying by IP, port, protocol, geography, reputation, etc.
- Good for broad request filtering before traffic reaches your app
-
API Gateway if you’re filtering API requests
- Useful for auth, rate limiting, schema validation, and routing
- Often combined with a WAF
-
Reverse proxy / edge proxy for more custom control
- Can do header checks, TLS termination, rate limiting, and basic filtering
If you mean web application request filtering, use a WAF at the edge.
If you mean network-layer filtering, use an NGFW/firewall.
If you want, I can recommend a specific setup for your environment, like cloud, Kubernetes, or on-prem.