AWS Auto Scaling vs. F5 Distributed Cloud WAF (Web Application Firewall)

It is well suited for scaling up our cloud virtual machines to handle the increase or decrease in workload. It really helps us to satisfy the demand because it doesn't take lot of time to spin up new machines. If there is unpredictability in the demand it is very useful. But it is a over kill if demand is consistent.

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

• Set policies to add more instances when CPU utilization exceeds.
• Prevents downtime, as we don't need to stop the servers.
• Auto Scaling group can be setup for different types of apps.

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

• Update code and configuration when the number of servers is always changing
• How will user-uploaded content make it to new servers

Incentivized

• Better integration between different F5 solutions
• 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.

Incentivized

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

We use AWS auto scaling for scaling up our cloud virtual machines to handle the increase or decrease in workload. It really helps us to satisfy the demand because it doesn't take lot of time to spin up new machines. I gave the rating 10 because it really does help you to handle the sudden spike in number of requests.

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

Used for the below reasons:

• Easy to implement and use
• Pay per use, cost savings
• Automate and build scaling plans
• Automate performance and workload

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

• optimized the cost effectiveness
• save lot of money which help the organization to use it in effective areas
• Not applicable for all use cases.It is specific use cases and business problems

• 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