Azure Application Gateway vs. Imperva Web Application Firewall (WAF)

For building scalable and highly available applications, Azure Application Gateway does most of the job on behalf of you; automatically load-balancing traffic from a number of users to a number of back-end servers. This ensure scalability and availability. The in-built security is great as can be expected from Microsoft, and user has a variety of tools for monitoring the health of the load-balancing function as well as the health of back end servers behind it.

Incentivized

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.

• Easy integration with Load Balancer and Azure Scale Set to provide a full solution for traffic management.
• With rich routing rule, we could use one Application Gateway as the central point for all internal applications to expose to the external network.

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

• Live examples in the Azure documentation
• Application Gateway UI Blade in Azure Portal can be streamlined
• Have more advanced feature set as WAF (Web Application Firewall)

Incentivized

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

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.

I don’t like that it's part of the Microsoft brand. In general, I am not a fan of Microsoft products but Azure gets it right.

Incentivized

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).

Other load balancing tools in Azure (Azure LB and Azure Traffic Manager) are limited in their functionality in comparison with the Azure Application Gateway, and also, they don't provide security features. Azure Firewall, although it has security features, is more expensive, and most importantly, it's not a load balancer at all.

Incentivized

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.

• Costs increased for the company, so expenses were more than before.
• Was able to get better user experience so users won't feel the website is useless.

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