Imperva Web Application Firewall (WAF) vs. StackPath Edge Delivery

Imperva web application firewall does a great job in giving us control over access to our public web servers. With our regular hosting provider, we couldn't block access based on geography, or really anything. So we had to rely on traditional access controls to protect the data. But with the WAF, we can block countries such as North Korea, or we could stop any SQL Injection attempts, or even do a temporary block of IP in the case of detected brute-forcing.

Well suited to:

1. Startups - Very competitive pricing, better than AWS for object storage and CDN.
2. The less technical - for those looking to implement a CDN, it doesn't get any easier than StackPath
3. The more technical - Well documented API, serverless scripting and container deployments
4. Fast object delivery - StackPath tends to be faster (sometimes much more ) than AWS S3. See below however...

Not so well suited to:

1. Multi-tiered web applications
2. Ultra high bandwidth requirements. Stackpath isn't meant to be a substitute for AWS or Azure when you're looking to push 100s of TBs of traffic.
3. Object storage works well if you don't need fine-grained bucket lifecycle or permissions management.

Incentivized

• Alert Aggregation - Correlates different violations into perceived correlated attacks.
• Ease of deployment - as one of the only WAFs that allow bridge mode deployment, this can be deployed with without downtime and no Network Architecture modifications. If the need for proxy is required at a later time, Transparent Reverse Proxy can be deployed within seconds and minimal configuration.
• Custom Policies - Custom security policies are easy to configure.
• Reporting - There are a good amount of pre-configured reports available by default.

Incentivized

• Price competitive.
• Easy to use.
• Good reporting.
• Quick to deploy.
• Start-up friendly.
• Good technical information via blog, FAQ and community discussion.
• I can talk to real person for urgent support.

Incentivized

• The UI can use a little work (but is largely decent)

• Analytics.
• Many options hidden in API.
• Web console.

Incentivized

There are just a couple of points that are hard to find, that probably could be elsewhere. But these are minor; everything else is right where you'd expect it to be.

We haven't needed support from Imperva since implementation. But during that time, their personnel were very quick to respond to questions. Since then, it's been largely doing its thing for us (which is exactly what we'd hoped).

Ultimately, it was the easiest to work with that was still a "known" company (we've been burned too many times by up-and-comers). We needed something that gave us a lot of control but then didn't need its handheld on a daily basis. Imperva gives us a lot of that and we are still able to navigate it with ease.

When we identified the need for having a Content Delivery Network to improve our website loading performance we researched a bit and found StackPath. Reading its reviews and the info on its website we have found that they had everything we needed so we didn't need to look for other products.

Incentivized

• Meet compliance requirements - Check.
• Better Insight into web application - Absolutely great, checks all the traffic against RFC standards and will alert on common development mistakes that duplicate application traffic or provide attack vectors for potential attackers.
• Have had several issues blocking a customer without producing alerts, while it happened only one week out of 2 years of working with the devices, it did produce a lot of headaches.

Incentivized

• Easy 25-30% improvement in website performance vs non CDN solution
• Less expensive and faster object storage than AWS
• Aided greatly in maintaining KPIs in terms of performance, availability

Incentivized