AlgoSec, from the company of the same name in Ridgefield Park, New Jersey, is a firewall security management option. The service now includes the CMDB capabilities of Prevasio, which was acquired by AlgoSec.
N/A
FireMon
Score 7.9 out of 10
Enterprise companies (1,001+ employees)
FireMon is a real-time security policy management solution built for today’s complex multi-vendor, enterprise environments. Supporting the latest firewall and policy enforcement technologies spanning on-premises networks to the cloud, FireMon delivers visibility and control across the entire IT landscape to automate policy changes, meet compliance standards, to minimize policy-related risk. Since creating their policy management solution in 2004, FireMon states they've helped…
N/A
Spot by NetApp
Score 7.0 out of 10
N/A
Spot by NetApp, now including CloudCheckr, helps companies to run their cloud investments. The Spot product suite uses machine learning and analytics to automate and optimize cloud infrastructure, to ensure that workloads and applications always have the best possible infrastructure that is available, scalable and available at the lowest possible cost. Spot’s technology provides insights into cloud costs, recommendations for how to optimize utilization and costs, and automation to implement…
Algosec has multi vendor support including cisco aci, nsx, aws and azure security groups. While most other vendors are lacking in the spectrum of the vendors. The ROI is best on this product.
Algosec is user-friendly and easy to implement and manage. The best part is it can be installed on-premises as well as on the cloud. It visualizes the complex networks and creates a dynamic network topology map. Using Firewall Analyzer, security and operations teams can …
I already had experience with the Tufin and AlgoSec products, and the customization that FireMon provides is just not available with the other products. The licensing of FireMon over AlgoSec is another winner for us.
We performed a head-to-head PoC between FireMon and AlgoSec several years ago. Both platforms were well developed, but FireMon had the upper hand in three areas:
Its UI was more unified and intuitive across the different components and products
AlgoSec and Tufin both have initial issues during the POC stage, and FireMon even though with the changes they have made still works better and is more user friendly.
I has worked with AlgoSec and while they are very similar product, I find the FireMon is easier to understand and get rolling with. While both require some learning, FireMon is by far the easier one. Once you have an understanding of how things are arranged and labeled you can …
To be blunt, at the time of purchase most of these products appeared to do the same things in the same ways. What really brought us to the table with FireMon six years ago was their willingness to earn our business, and to this day they remain just as committed to keeping our …
FireMon has the most supported devices. The UI is easy to use and intuitive. There is a comprehensive list of built in compliance controls that are missing in the competition.
We were impressed with FireMon's native cloud support and compliance reporting, in looking at other vendors we were not too impressed by their ability to support cloud-native technologies and their reporting was less than stellar. We did not want a solution that would last only …
FireMon is best used in a large environment (for example, I have >100 firewalls in my environment). It's best used when trying to improve security posture and showing changes in firewall security over time. It might not be the best choice for smaller environments or those that aren't concerned about security management.
CloudCheckr is fantastic for those that are purely in the Cloud as it provides everything you need under one roof for a comprehensive configuration and usage monitoring tool. It has SysLog capabilities though so you can farm out the alerts into a SIEM or other log management system, so hybrid environments could also benefit from its use.
Detailed Best Practices. It's important to align your cloud to industry best practices for security and cost—it just performs better if it's used the way it's meant to be used. AWS is very flexible, and that's great when you have special requirements, but you've got to at least know when you're using something in a non-standard way so you can think through the implications.
Cost Reduction. Some recommendations are almost impossible to make at least for our setup, but many, many others are easy. We only have to log into CloudCheckr every few months and make a few changes for it to more than pay for itself.
Right-Sizing. This is related to the other points, but for some reason is separate from their cost module. The metrics it's able to pull only tell half the story, so it's good to verify it's sizing recommendations before making changes. But it does show you what instances to focus on first, and even if you choose a slightly different size to move it to, it does clearly indicate it's current size isn't appropriate. And this works both ways, if the size is too big, you can save some cash by making it smaller, but if it's too small, you want to be sure to scale up before you run into performance problems.
CloudCheckr features have a tendency to break without warning. Functionality in place for months could suddenly stop working.
CloudCheckr support often delays work on support tickets for fixing broken application functionality.
The CloudCheckr platform and documentation website often crash or experience performance degradation.
CloudCheckr cost reporting is often impacted by faulty code or broken report functionality. This can contribute to a low level of confidence in CloudCheckr's ability to deliver accurate cost reporting.
The shell is locked out and we can't run any general centos commands. The implementation and maintainence of the arch is very complex. Even with the right identifiers on log messages the log collection keeps failing. The warning messages on the device are ambiguous. The log messages on firemon are a bit confusing and don't show the exact issue.
Overall, CloudCheckr covers all our AWS monitoring needs and great integration through SysLog into our SIEM to capture alerts for investigation. The reports are great and allow for an easy daily review. Small improvements could be made to the interface and better filtering in places would be good. Great product and the price is fair.
FireMon has been relatively stable overall. However, there have been a handful of times where we had issues with the console. For example, we couldn't update which devices to include in a security assessment. The initial suggestion from support was to just reboot it. It seems like there weren't many other options available such as to restart services before going to the extreme of a complete reboot.
I'm not sure we have the largest implementation of FireMon out there but we do have a few 1000 devices being probed by FireMon. Overall, the system's performance has been rock solid. The console refreshes quickly and reports are generated within an expected timeframe.
FireMon technical support is awesome! They respond quickly to our requests and they are well trained and very knowledgeable about the tool. Some issues have to be referred to the development team, but technical support largely provides solutions for any issues that we may have.
I has worked with AlgoSec and while they are very similar product, I find the FireMon is easier to understand and get rolling with. While both require some learning, FireMon is by far the easier one. Once you have an understanding of how things are arranged and labeled you can easily import firewalls and begin to work on them to improve them
There are a few products out there that'll do an aspect or two of what CloudCheckr does, but I honestly couldn't find anything nearly as comprehensive as CloudCheckr.
Firemon Is easily scalable and maintainable with any size team. Although it requires some tech debt, it is well worth the time to invest to ensure compliance is visible and reports are accurate. Although our environment is very large we do not fully utilize the scalability of the Firemon product.