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
OVHcloud Public Cloud
Score 8.1 out of 10
N/A
OVHcloud Public Cloud offers users a large number of cloud solutions that are billed on a pay-as-you-go basis. OVH states their infrastructure is set up in a simple way to enable businesses to harness the flexibility of on-demand resources to scale up from small projects to large-scale deployments.
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.
For demo uploads or for production uploads of companies from different sectors looking for a "general computing" cloud solution, I think that OVH can be a good provider. However, for more delicate or advanced loads or for specific solutions of, for example, AI, OVH has a wide margin for improvement.
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.
Fail over between devices feels unstable if there are thousands of objects attached to the traffic-group. Needs to be more simpler.
We have seen issues with malicious user detection where we have used open protocols due to legacy applications, and have been caught with legitimate traffic being blocked.
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.
Most notably OVHcloud [Public Cloud] has dedicated servers which are a different breed of product than Linode's flagship VPS servers, the unfortunate fact of the matter is that OVHcloud [Public Cloud] can provide a fully-dedicated server at a lower price point than Linode's virtual server. Even worse than that is that with a dedicated server from [OVHcloud Public Cloud] there is zero chance of "cpu theft" (aka, noisy neighbor) which is a very real problem at Linode (we would require multiple migrations every year for servers hosted at Linode that were experiencing cpu theft). In addition to the improvement in quality for network/hardware at OVHcloud [Public Cloud] with their dedicated server offering, their VPS servers are also highly competitive against Linode's VPS servers - in the 2 years we've used OVHcloud [Public Cloud] VPS's we've had zero downtime associated with OVH actions such as host-node reboots or cpu theft or host node upgrades, a stark difference compared to Linode which regularly experiences those types of downtimes and many more on a very regular basis.
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
