Prompt
I'm building a legacy app that can't be changed quickly. Help me choose a WAF for virtual patching and attack blocking.
Latest observation
For a legacy app you can’t modify quickly, a WAF is a good fit for virtual patching: you can block known exploit patterns at the edge while you plan proper fixes.
What to prioritize
Look for a WAF that has:
-
Strong virtual patching
- Ability to write custom rules quickly
- Good regex/pattern matching
- Fast deployment and rollback
-
Easy deployment in front of legacy apps
- Reverse proxy, inline appliance, or cloud proxy mode
- Minimal app changes
- Support for TLS termination if needed
-
Managed threat intelligence
- Prebuilt rules for OWASP Top 10, bots, scanners, RCE, SQLi, XSS, path traversal, deserialization, etc.
- Frequent rule updates
-
Good logging and tuning
- Full request/response visibility
- False-positive handling
- Per-endpoint exemptions and rate limits
-
Bot and abuse protection
- Credential stuffing, scraping, L7 DDoS, API abuse
-
Integration
- SIEM, ticketing, alerting, IAM, CDN, load balancers
Common options by deployment style
Cloud-delivered WAF
Best if you want the fastest deployment and minimal ops.
-
Cloudflare WAF
- Very quick to deploy
- Strong edge blocking, bot mitigation, rate limiting
- Good for virtual patching via rules
- Best if your traffic can front through Cloudflare
-
Akamai App & API Protector
- Strong enterprise-grade protection
- Very good for large, high-traffic environments
- Excellent security services, but usually more complex/costly
-
Imperva Cloud WAF
- Strong traditional WAF capabilities
- Good managed protections and attack analytics
- Often used for legacy apps needing quick shielding
-
Fastly Next-Gen WAF
- Good for real-time detection and low-latency environments
- Helpful if you already use Fastly/CDN
On-prem / appliance / hybrid
Best if the app can’t leave your network.
-
F5 BIG-IP Advanced WAF
- Strong enterprise WAF
- Good custom policy control and virtual patching
- Useful if you already run F5
-
Fortinet FortiWeb
- Solid WAF appliance option
- Often attractive on price/performance
- Good if you already use Fortinet
-
Citrix ADC WAF
- Good if you already have Citrix ADC infrastructure
- Useful for application delivery + WAF together
Open-source / DIY
Good for budget constraints, but more tuning effort.
-
ModSecurity + OWASP Core Rule Set
- Flexible and widely used
- Good for custom rules and virtual patching
- Requires careful tuning and operational maturity
-
NAXSI
- Linux/nginx-focused, lighter-weight
- Less feature-rich than commercial options
My practical recommendation
If you need fast virtual patching with minimal change, shortlist based on where the app lives:
- Internet-facing, can be proxied externally:
Cloudflare WAF or Imperva Cloud WAF - On-prem / private network:
F5 BIG-IP Advanced WAF or FortiWeb - Low budget / technical team comfortable tuning rules:
ModSecurity + OWASP CRS
Questions to ask vendors
Ask these specifically so you know they can actually protect a legacy app:
- Can we block by URI, parameter, header, cookie, method, IP, ASN, geo?
- Can we create temporary virtual patch rules quickly and safely?
- How do you support false-positive tuning per endpoint?
- Do you support positive security models for sensitive paths?
- Can you protect logins, forms, and APIs differently?
- How fast are rule updates for new CVEs?
- Do you support rate limiting and bot mitigation?
- What visibility do we get for blocked and allowed requests?
- Can it run in monitor-only mode first?
- How does it behave with TLS, redirects, large uploads, and legacy encodings?
Suggested rollout approach
- Put WAF in monitor mode
- Baseline normal traffic
- Add virtual patch rules for known vulnerable endpoints
- Turn on blocking for high-confidence signatures
- Add rate limits and bot controls
- Tune false positives gradually
- Plan real app fixes later
If you want, I can also give you a shortlist by budget, cloud vs on-prem, or a decision matrix for 3–5 specific WAF products.