Akamai Bot Manager vs. F5 Distributed Cloud WAF (Web Application Firewall)

One of the most serious issues with commercial websites is dealing with bots. Even a good bot can slow down or render a website unresponsive. Because not all bots are evil, Akamai Bot Manager allows us to handle the bots that are required and those that are not. It adds an extra degree of security where typical solutions fail.

Incentivized

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.

Incentivized

• Bot detection
• Good selection of actions in case of bot detection
• Easy implementation of its standard features

Incentivized

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

Incentivized

• Support might not be as fast as we want for custom implementations.
• At the beginning the interface might be confusing.
• Some new features they introduce might break existing features.

Incentivized

• Lack of warnings, currently the console does not provide a warning when deleting key-value entry.
• The web GUI could use some tweaking, currently no undo option when removing exclusion rules.
• Configuration complexity, currently menus and options are hidden, making it hard to configure vs on prem.

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.

Incentivized

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.

Incentivized

Seems no issue

Incentivized

Unnoticed slowness

Incentivized

I never contacted support for this product.

Incentivized

Online training saves me lots of time

Incentivized

Just make sure you origin servers have F5 IPs allowed.

Incentivized

Security concerns call for the deployment of Akamai Bot Manager. It assists in preventing bots from being unable to target our website and applications. The Akamai lab rejects the request or attack before it reaches my cloud infrastructure or my applications. My application is more secure as a result.

Incentivized

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.

Incentivized

Dont see any issue so far

Incentivized

• Reduce overall infrastructure maintenance due to less incoming traffic and leverage of caching rules
• Better user experience on the website due to better overall performance

Incentivized

• 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

Incentivized