The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
My main use case for Imperva Application Security Platform involves using WAF policies and rules for mitigating WAF attacks, OWASP Top 10, and bot rules.
A specific example of how I use those policies and rules to mitigate web threats is related to a recent attack involving Node.js and PHP vulnerabilities. During a recent PHP attack, Imperva provided us with rules that allowed us to temporarily block the attack on our application security WAF.
The best features that Imperva Application Security Platform offers in my experience include user-friendliness during onboarding. The onboarding process was user-friendly because of the interfaces and documentation provided.
Imperva Application Security Platform has positively impacted my organization as I have noticed that 95% of attacks have been mitigated. I measured that 95% mitigation rate through the Imperva dashboard.
Imperva Application Security Platform could be improved by adding an exclusive web analytics dashboard where I can extensively add multiple parameters and view graphs and tables for events and security events.
Regarding Imperva Application Security Platform's AI capabilities, I think its governance and security need improvement. The accuracy and reliability of output are good as it is accurate, but it still needs fine-tuning because sometimes it also gives false positives.
I have been using Imperva Application Security Platform for seven years.
Imperva Application Security Platform is stable in my experience.
The scalability of Imperva Application Security Platform is an eight.
The customer support for Imperva Application Security Platform is good as I can get a reply instantly in some cases. On a scale of one to ten, I would rate the customer support a seven.
My experience with the pricing, setup cost, and licensing for Imperva Application Security Platform is that it is budget-friendly.
Before choosing Imperva Application Security Platform, I evaluated other options such as Incent.
On a scale of one to ten, I would rate Imperva Application Security Platform an eight. I chose eight out of ten because its interface and documentation are very good, and it is useful for mitigating 95% of attacks in my organization, but it still needs improvement with a web security analytics dashboard compared to Akamai.
Imperva Application Security Platform is deployed in my organization using a public cloud with Incapsula as my cloud provider for deployment. My advice to others looking into using Imperva Application Security Platform is that if someone is looking for a user-friendly WAF solution, they should consider Imperva.
Our main use case for F5 Distributed Cloud Services is the application traffic management and security for our web applications. We rely on F5 Distributed Cloud Services primarily for load balancing, WAF capabilities, and routing traffic to applications across our cloud environment.
We use F5 Distributed Cloud Services as we migrate our online application away from the previous gateway and WAF solution. The application traffic can be protected and managed through the F5 Distributed Cloud Services platform. We use F5 Distributed Cloud Services as a front end for the application traffic with logical HTTP load balancer and hostname-based rules directing requests to the appropriate origin pools.
F5 Distributed Cloud Services has positively impacted my organization from the security point of view, as all our applications are in a very stable, safe mode. This is important, especially taking into account all the sensitive customer data which flows through our systems. Security is the number one feature right now. The stronger security we have, the more reliable we are as an organization.
Since using F5 Distributed Cloud Services, from an operational perspective, being able to see the actual request through the load balancer makes change validation much easier.
The best features F5 Distributed Cloud Services offers in my experience are load balancing, traffic routing, and WAF. These are the strongest features for us. Traffic visibility is also very useful, especially when we are validating changes or troubleshooting routing issues.
Traffic visibility has helped our team significantly. For instance, after a routing change, we can look at the actual requests going through the load balancer and can quickly confirm that the traffic is reaching the new route. This is the most practical example of how we use the visibility.
An improvement for F5 Distributed Cloud Services could be in usability. It is very powerful, but it can also be quite complex. When you have many applications and routes, the troubleshooting process is not always straightforward. Making it easier to follow the traffic path and quickly see where something is going wrong would be a great enhancement.
We have been using F5 Distributed Cloud Services for almost three years. We are in an established project starting from January last year. We are actively migrating an online application from an end-of-life application gateway to F5 Distributed Cloud Services.
F5 Distributed Cloud Services is stable in my experience.
The scalability of F5 Distributed Cloud Services is good enough from my perspective. We have not hit any major scalability limitations so far.
The customer support experience for F5 Distributed Cloud Services was quite positive.
Before F5 Distributed Cloud Services, we used a traditional on-premise F5 load balancer, and for our cloud application, we also used Azure Application Gateway and WAF. We moved to F5 Distributed Cloud Services because those solutions were outdated and were not aligned with the new requirements, specifically security requirements.
F5 Distributed Cloud Services is deployed in our organization as a hybrid model right now, as we are still using all possible capabilities.
My advice for others looking into using F5 Distributed Cloud Services is to do your preparation.
Regarding F5 Distributed Cloud Services's AI capabilities, governance and security are obviously major parts of the product. I feel the way F5 Distributed Cloud Services handles AI governance and security is promising. The capabilities look promising. However, we are not widely using the AI-specific features extensively enough. AI governance and security are one of our critical focuses. Governance, data protection, and having a clear control area around how AI is used would be very important before expanding the adoption.
I cannot judge F5 Distributed Cloud Services's AI capabilities thoroughly at this time. Our use of F5 Distributed Cloud Services today is much more focused on traffic management. I would say it is still too early to assess AI output.
I rate F5 Distributed Cloud Services an eight out of ten. The reason for this eight rating is that we must keep a buffer for future improvements. If I would score a ten, that would mean the product is absolutely perfect and ideal. However, we need room for future improvements.
