AlgoSec Reviews

Our primary use for AlgoSec is to automate our firewall configuration. We use the AlgoSec system to remotely configure the firewalls, making our life easier.

We are in a multisite environment with plenty of firewalls for perimeter security and LAN segregation for specific proposes. This solution helped us to make the process more dynamic.

It has reduced the workload for the firewall team thanks to the API integration with our ticketing system, doing the standard type of request automatically. Before having it, we had to create a lot of standard rules that now can now be just pushed from the AlgoSec system.

The automation of the firewall rule deployment, working together with our ticketing system, is the most valuable feature of this solution. The needs as required by a user request are automatically validated and configured in the specified firewalls without any human action. This improves the firewall team's workload.

I would be nice to have a good tool for network map discovery in the GUI to make it more user friendly and be able to check and modify network maps in graphical and more intuitive way . This will improve our network overview for new deployments and troubleshooting. 

I have been using this solution for three years.

In three years, we have only had one issue with respect to stability.

When we had the issue they responded well.

We did not use another solution before AlgoSec.

We deployed this solution using our in-house team.

The reduction in workload reduces the cost in terms of human time.

We primarily use the AlgoSec Firewall Analyzer.

We have more than ten cluster firewalls and we have deployed the AlgoSec solution suite. We want to check compliance status of our devices. We also need to reduce the number of rules in each of the policies.

In our new data center, we want to automate the firewall policies.

Now, we can easily track the changes in policies. With every change, AlgoSec automatically sends an email to the IT audit team. It increases our visibility of changes in every policy. 

Every month, I use the optimizer to reduce firewall rules. In the summary tab, I can easily track the number of changes in the firewall policies.

The most valuable feature is the reporting, including the policy report and regulatory compliance reports.

In the Intelligent Policy Tuner, the tighten permissive rules tab allows us to reduce the number of rules in each policy. I can easily control, report, and reduce the rules for policies. Also in the Rules Cleanup tab, I am removing unused rules as I feel confident in deleting these types of rules.

Our Information team read Regulatory Compliance Reports that can easily track the compliance status of each device.

Cisco Firepower device support is limited in our AlgoSec system and I think AlgoSec can improve in that area. For example, in FireFlow we can easily track using the ticketing system to integrated Check Point devices. However, with Cisco Firepower devices, we couldn't integrate with them.

We have been using AlgoSec for almost six years.

We did not use another solution prior to this one.

The pricing of AlgoSec is fair.

Before purchasing AlgoSec, we implemented a PoC with each of AlgoSec, Tufin, and FireMon.

We have more than ten clusters behind our firewall. It is essential that we track the changes in policies and the compliance status of devices. AlgoSec can easily do that.

We use this solution for managing an environment with more than five thousand registered devices across firewalls, routers, balancers, and VMware. Highly critical banking environment.

We use FireFlow as our primary ticket management tool.

With AlgoSec, it was able to conduct the environment so that it was possible to get more accurate and fast information about the changes that the environment went through.

It has reduced the time for firewall rule requests to be implemented in the environment.

The most valuable feature is traffic simulation because, with this function, it has become more practical to know if something is released or blocked in my environment.

IPT is valuable because this function is of great help to have a more effective security policy.

I believe Active Change needs to be improved because not all products are supported, and some functions cannot be implemented by Active Change either.

Technical support needs to find solutions more quickly.

Active Change could implement routes in Firewalls, it should also be able to perform the creation of APP control and URL filter rules.

We have been using this solution for six years.

In general, it is a stable product. We have rarely had a problem that resulted in the total unavailability of the solution.

AlgoSec requires a large amount of processing power to perform its tasks, making it a piece of equipment that always requires monitoring to be optimally optimized.

Some troubleshooting took months to resolve. So, I think we have to improve this point.

I used Nipper and FireMon, but I started using AlgoSec due to the great recommendations I received.

The architecture was defined with one master, four slaves, and one remote.

Our internal team handled the deployment.

I do not have many details of this commercial part.

I evaluated FireMon and Nipper in addition to this solution.

Many users have the tool but don't use it with everything it can offer. What I recommend is that you explore all of the features of the product.

We use this solution for managing risks, device compliance, a ticket system, and active change.

It definitely helps a lot to manage the complexity of environments with many devices and many vendors.

The most valuable features are the network map, risk analysis, and tickets for firewall changes.

Very helpful automatic implementation of requested changes.

I would like to seem improvements in performance and software stability.

AlgoSec helps us by giving an overview of our Layer 3 network devices. With the solution, we can uncover bottlenecks, streamline, and clean up our firewall rules.

AlgoSec saves our IT department a lot of time and also creates transparency. A large number of reports can be generated quickly. The reports are based on all known catalogs and are important for management and department heads. The products interlock and share relevant information with each other.

The most valuable feature is the interaction between AlgoSec's different solutions. From Firewall Analyzer to FireFlow to BusinessFlow, the solutions add value for us and our customers. The basis with the Firewall Analyzer and the corresponding Network Map is one of the core features for transparency.

The ticket system informs all of the people involved with respect to the next steps.

The reporting and documentation components help us to comply with the ISO catalog.

It is always possible to improve the product.

We would like to have a kind of "Time Capsule" to be able to restore to a certain state from a backup.

We would like to have a BSI Compliance Report for Germany.

Interfaces are worked on continuously, and small firewall manufacturers such as Sophos should still be included as standard.

All manufacturers on the market are constantly improving. The beautiful and simple thing about AlgoSec is the short distances and that you are heard. If you want a feature implemented, or a report for a certain country adapted or created, then they will take your request seriously right up to the C-Level. The implementation takes place promptly and is customer-friendly.

The primary use for this solution is to clean-up and fine-tune firewall rules.

I found that for policy optimization it does a great job. It handles covered rules, duplicate rules, and consolidated rules.

The most valuable feature is the ability to reorder rules because of the enhancement of firewall CPU performance when they are applied.

I would like an intelligent tuner where it could help update rules with the application ID.

We utilize this solution to manage policies for our firewalls. At first, we used it to keep a record of our policies: Who changed something, when, and whether the policy is allowed or not. We now use it to map our traffic flows and to flag a policy that is not allowed by the criteria we have set for our different types of firewalls.

We used it initially to go through all of our policies on over 800 firewalls, to organize the policies and map out our policy flows to certain zones. That enabled us to know how to structure our policies.

We spent a year going through our firewall policies to clean them up because before, when we were on Cisco ASA firewalls, we had a very hard time regulating what types of firewall policies were being created, and it was even harder to review them. After we moved to Palo Alto firewalls, we decided that that was the best time to load our policies into AlgoSec and review them. That way we not only converted to a more capable next-generation firewall, we could also ensure the policies were strong.

AlgoSec has helped significantly with our firewall compliance. Before AlgoSec it was a very manual job to go through firewalls and look for risky rules. Now, we get alerts when a risky rule is created. This allows us to maintain compliance and run compliance checks monthly. As a result, we have saved many hours of work by our operations folks. They were the ones who had to manually review all of the firewall policies and create evidence of their review in a very scrappy fashion.

With AlgoSec, we can show a view of firewall compliance that is clean and easy to read and present. This also helps our business units ensure their policies are clean. With that data, we are able to show management that the firewalls connected to our network, but owned by other business units, meet our standards.

We like that we have been able to identify risky rules, based on the criteria we have set. We also like the ability to push policies from AlgoSec to the firewalls to ensure risky policies are never created in the first place. That's a feature that will help us in the future as well.

We are moving towards an automated environment so the ability to work with Ansible, ServiceNow, and Palo Alto gives us the ability to automate our firewall policy creation. And it does so in a manner where we do not have to worry about a policy being created that may put our organization at risk.

Support for Layer 7 policies, including User-ID and threat profiles with Palo Alto firewalls, has been a pain point from us. We would like to include the additional info specifically because we believe it changes the riskiness of the rule if it is only set for a specific user or a group of users. For example, if we have what looks like an "allow all" to a certain /24 network, but for only one user, we would give that a different score than if no user was identified.

AlgoSec has been very stable for us.

It scales well.

We have had our issues resolved very quickly.

We used Tufin. 

The initial setup was very simple. We just set up SNMP.

We used a vendor team and they were great.

The ROI for us is the great assurance we have in the security of our firewall policies.

Be sure to scale properly.

We evaluated Tufin.

This solution will help you significantly with compliance, the part of your job that may not be your favorite.

We are using AlogSec mainly for firewall compliance reporting as well analyzing and evaluating firewall policy. That, in turn, means we can actively work on firewall policy optimization and elimination of unused and risky rules. We also using it for compliance reporting. 

The solution has helped us a lot in improving our firewall security optimization as well in evaluating security policy to eliminate the risky rules or secure them. 

Its reporting modules solve all our monthly and quarterly compliance-related reporting requirements. 

Currently, we are using almost all the features of the product to take as much advantage as we can of what it offers. But our primary use is compliance reporting and the Firewall Analyzer helps us achieve our various IT compliance requirements, like ISO-27001.

There is huge scope for improvement in the level of support, especially around the issue of resolution time. That is the only negative point I find in the solution. I hope you guys will work on it and improve your resolution time which will help customers to keep their AlgoSec device healthy.

In the six years we have been using it, we have never seen an outage or failure of AlgoSec or any other software-related failure. 

The product is very scalable. We have never faced any issues related to the scalability of the product. 

As an individual, my experience has been good, but in terms of technical-issue resolution, I am not 100 percent satisfied because of time the AlgoSec team takes to fix issues, some of the time.

Previously, we were using Tufin but we found that solution more complicated when compared with AlgoSec. 

The initial setup was straightforward because of the well-defined GUI platform.

We implemented it in-house.

Given that we have been using this product for the last six years, there is no question about ROI. If we were not seeing ROI, per our expectations, we would not continue with the product. 

AlgoSec is not much more expensive compared to other products available in the market.

We evaluated FireMon but it was more complicated than AlgoSec and did not fulfill our basic requirements. 

Overall, AlgoSec is doing a good job.

We are using this product mainly for firewall and network management. It detects any firewall and network changes that are done manually and not within the change control time window. Finding out the traffic is blocked or not using BusinessFlow is really good.

It didn't improve in my organization. There is a lack of documentation when communicating between the AlgoSec appliance and the other appliance. When we raised these concerns to their support, they were not able to help us with the issues.

We loved the automatic policy or network topology change features in the AlgoSec appliance. It detects the changes and alerts when someone is trying to make changes in the firewalls or network devices during abnormal change-time windows.

It detects if the requested network and ports are getting blocked by the network or firewalls by a simple query, which helps to identify the network blocking firewalls in the topology.

1. AlgoSec support needs improvement, and support needs training to better understand customer issues. ( Support team repeatedly fails to understand the customer issues, Response to the support ticket based on the severity is very poor, support team responses to severity 1 or 2 tickets are very very slow. Customer support representative need training on how to handle severity 1 or 2 tickets)
2. Integration with other appliances needs improvement. ( AlgoSec integration with other ticketing systems like Service Manager / Service now is not good, It needs to have better integration with ticketing systems like Service Now and Atlassian JIRA)  
3. Documentation needs improvement. ( There is lack of documentation integration with other ticketing systems like HP service manager, Rest APIs, SOAP)
4. There are limited sets of Python API calls, so they need to add more features in the API.
5. The FireFlow template does not allow the user to perform external actions like sending an email or triggering a specific action. It needs improvement there.

AlgoSec support is very, very poor. Their support engineers do not even understand the problem or the severity of cases. AlgoSec is pretty bad with handling hardware appliance failure.

This is the first solution we used.

My advice is to please make sure that you evaluate other competitive products before choosing this solution.

The price is high but the support is extremely poor, so keep that in mind before choosing this product.

We evaluated FireMon before choosing this solution.

We use this solution for the management of firewalls on a client with a multi-vendor landscape and a low maturity level in terms of security operations and mechanisms. The AlgoSec tool supported the necessary transformation we were helping the client with, centralizing and simplifying the management of all firewalls in several sites across the globe.

AlgoSec is a powerful firewall management tool. I have supported a client implementing the firewall analyzer in an environment with several firewall vendors and poor management. The implementation went smoothly, with good support from the AlgoSec team. However, the configuration was tricky due to the maturity of the client and the ‘messy’ situation, and the internal know-how available regarding what was implemented on the multiple sites.

The most valuable feature is that the tool is capable of simplifying firewall management and configuration in an automated fashion. Additionally, the fact that it is also possible to implement a FW management workflow clearly supports the improvement of the 'way of working' and operation of the FW environment.

The network mapping interface could be improved in the next version. In a complex landscape, with several nodes/equipment, it can be somewhat more difficult to properly visualize the network map. It requires several zoom-in and zoom-out operations, and it is not so visually appealing. Nevertheless, it is still a valuable feature and was highly used by my team.

We evaluated other options before choosing this solution including Skybox and Palo Alto Panorama.

Do not underestimate the configuration effort, especially on a more complex landscape.