Apache Web Server (Apache HTTP Server) is an open source HTTP web server for modern operating systems including UNIX and Windows.
N/A
Radware Bot Manager
Score 10.0 out of 10
N/A
Radware Bot Manager (formerly ShieldSquare) is a non-intrusive API-based Bot Management solution to detect, eliminate, and manage bot traffic from websites, mobile apps, and APIs in real-time. The solution leverages Intent-based Deep Behavior Analysis, device fingerprinting, and domain-specific detection technologies to identify and eliminate invalid traffic with zero false positives. The vendor states they protect users against automated attacks such as account takeover, application…
As I mentioned earlier, the Apache HTTP Server has a small disadvantage compared to the competition (NGINX) in terms of performance. If you run websites that really have a lot of visitors, NGINX might be the better alternative.
On the other hand, the Apache HTTP Server is open source and free. Further functionalities can be activated via modules. The documentation is really excellent.
All new upgraded non-human bot detection feature is widely used across all the platforms open for customers and it is a great success. It provides zero access to malicious bots.
Street Cred: Apache Web Server is the Founder for all of Apache Foundation's other projects. Without the Web Server, Apache Foundation would look very different. That being said, they have done a good job of maintaining the code base, and keeping a lot of what makes Apache so special
Stability: Apache is rock-solid. While no software is perfect, Apache can parse your web sources quickly and cleanly.
Flexibility: Need to startup your own Webpage? Done. Wordpress? Yup. REST Endpoint? Check. Honeypot? Absolutely.
ShieldSquare provides an easy to implement way of identifying website users that could be bots.
By rating the potential of the user of being a bot, we are able to handle that user in the proper way.
False positives are extremely rare with ShieldSquare. Plus, their support staff is also available to analyze traffic to specific content, and they can customize their algorithms when necessary to optimize the performance of their solution to suit our needs.
The default configurations which comes with Apache server needs to get optimized for performance and security with every new installation as these defaults are not recommended to push on the production environment directly.
Security options and advanced configurations are not easy to set up and require an additional level of expertise.
Admin frontend GUI could be improved to a great extent to match with other enterprise tools available to serve similar requirements.
It would be nice to allow for more granularity when selecting which bots I'd like to allow through. I contacted support and asked about this and they said this was in the works.
If you select to show captchas instead of blocking, I feel their captcha screen could use some improvement on the UI/UX to make it more intuitive for users to know what to do. I contacted support and made them aware of this.
Would be nice to see captchas information in the statistics (i.e. how many captchas were presented, from what IP addresses, how many were filled out correctly),
I give this rating because there is so much Apache documentation and information on the web that you can literally do anything. This has to do with the fact that there is a huge Open Source community that is beyond mature and perhaps one of the most helpful to be found. The only thing that should hold anyone back from anything is that they can not read. RTFM, my friend. And I must say that the manual is excellent.
I has a lot more features, except that IIS is more integrated in a Windows environment. But now with .net core also possible from Apache it would work anywhere really. Only in a full Windows environment where full integration is needed I would chose to go for IIS. Otherwise Apache it is.
When I compared these two products, Distil Networks only offered a solution where their bot detection sits in between your website and the visitors, similar to how Cloudflare works. I didn't want this so I decided to go for ShieldSquare that uses connectors. I want my visitors to hit the website directly, not have something sit in between.
