F5 Distributed Cloud WAF leverages F5's Advanced WAF technology, delivering WAF-as-a-Service and combining signature- and behavior-based protection for web applications. It acts as an intermediate proxy to inspect application requests and responses to block and mitigate a broad spectrum of risks stemming from the OW ASP Top 10, persistent and coordinated threat campaigns, bots, and layer 7 DoS.
N/A
Azure Front Door
Score 9.0 out of 10
N/A
Azure Front Door is a cloud content delivery network (CDN) service that helps users deliver high performance, scalability, and a secure user experiences for content and applications. It includes a customizable rules engine for advanced routing capabilities. It boasts instant scalability with global HTTP load balancing and failover.
It helps our website to manage well during high traffic seasons and Holidays. This plaform manages the website overall performance and also protect it against DDoS attacks during these High demand period. It also protects transactions done on our website for the booking of services and products buying by our customers and keep their data safe.
Azure Front Door is very easy and fast to set up and implement, if you are looking for an easy solution that is secure and reliable, Front Door does all that and can be configured in a few hours. AFD is a CDN with WAF, accordingly, it is well suited for any CDN Scenario, other providers such as Akamai or Verizon have a more expensive base price and are harder to manage/configure, Front Door is simple, easy, and provides what's needed when it comes to Web App Security. If you have multiple data centers, have apps in different regions, or targeting a global audience, AFD is an excellent option to get up to speed quickly. If you are looking for more features and capabilities, or planning a very complex setup, Front Door might be sufficient, but other specialized provides such as Imperva, Cloudflare or Akamai are generally a bit more advanced (but harder to set up and maintain). It always depends on the scenario, but for us, Front Door was an excellent option and served us very well with no issues.
Layer seven attacks are becoming far more common. Traditionally it was always layered three, layer four, where you get an additional firewall, but with the application layer attacks become more frequent, more popular, et cetera. So having the web application firewall protecting us, and then with the recent Log4j, that's the most recent use case when it gave us that instant level of protection whilst we remediated the Log4j that we had that and the F5 Distributed Cloud WAF was protecting us.
I have a great relationship with the account manager, my account manager, and I think he drives the best price possible, um, for me, and I'm happy with that price.
F5 Distributed Cloud WAF is always innovating and evolving.
We run a very competitive proof value where we run numerous competitors against each other, and then we evaluate from that and then make the selection, and F5 Distributed Cloud WAF was the winner.
We gave it an 8 because it protects our web apps well and is reliable. The WAF is flexible and meets most of our needs. It could improve in user interface and make integrations easier, but overall, it’s a solid and effective security tool for us.
I believe is a solution that was designed from the start to be simple and easy to use. Coming from Imperva, it simply eased the burden and complexity of managing and securing our apps on different environments (cloud and on-prem). It easy to scale and very quick to deploy (as a cloud waf should be), provide us with DevOps integrations, visibility and automatic insights from multiple events that guarantee peace of mind for us analysts and opp managers.
It provides fewer false positives and a more granular approach to eliminating them, allowing us to focus on threats. Also, with the need to secure both on-premise and cloud-based web applications, we can only use Azure on the cloud part, but we still need to cover on-premise apps with WAF, so we would need to double the time to deploy and manage. Also, its flexibility of deployment scenarios offers us a faster time to deploy WAF without adjusting the app delivery process to WAF's existence.
It's generally hard to compare CDNs, each has its features, POP locations, latency, and availability. We have used many other CDNs, including Akamai, Verizon, and Cloudflare. They are all great, but each has its own advantages/disadvantages. From our perspective, all other providers were much harder to configure and maintain and their overall cost was higher than AFD. For example, Verizon was great, performance was excellent, but reporting/logging was not up to our expectations, and we had many issues with its Rules Engine. AFD is great for delivering your web apps globally quickly and easily, the cost is reasonable and comes with very little operational overhead, the logging and reporting capabilities are very good, additionally, its integration with Azure Cloud Services gives it an advantage over other competitors.
The biggest gain for us was speed. Before F5 Distributed Cloud WAF, onboarding a new app to our WAF stack meant manual rule tuning, traffic sampling and regression testing. Right now, we spin up a service, tag it with the right policy and its ready (production ready) within hours
AFD implementation was approx. 80% cheaper than other providers, from initiation to operation.
It allowed us to minimize backend resources size/processing power, taking all the load from client requests, cutting tens of thousands of dollars monthly on compute, memory, and network bandwidth.
Overall, the ROI of AFD is very quick, it is not an expensive solution, therefore, its ROI goals are easy to calculate and achieve, our overall ROI exceeded 300%.
