AlgoSec Reviews

The most common use cases include:

• Performing audits on an annual basis with the help of information security
• Remediating risky rules by trusting them or remediating them at the firewall level
• Unused rules and disabled rules are addressed on a regular basis
• All firewall changes are monitored through AlgoSec with the help of change notifications
• Improving compliance and risk management and connections revolving around the network Layer 3
• Locating objects and addressing any issues on a much quicker basis

We were able to improve the security ratings of our firewalls. It helped us with annual audits, change notifications, rule assessments, and visibility in general.

It improved compliance and risk management and connections revolving around the network Layer 3.

We can get all the firewall-related data with a single click and effectively work on synchronizing with all the firewall gateways including the management server.

It helps us with firewall audits on an annual basis with the help of information security.

We remediate risky rules by trusting them or remediating them at the firewall level.

We address the unused rules and disabled rules on a regular basis.

All firewall changes are monitored through AlgoSec with the help of change notifications.

It improved compliance and risk management and connections revolving around the network Layer 3.

It helps locate objects and address any issues on a much quicker basis.

RFEs are kept open for too long. We had requested a couple of features, including the ability to trust implicit rules, and IPT doesn't run on IPSEC-enabled firewalls (Cisco to be specific). We had reported these issues for over four years now and still we do not see any resolution.

There is no visibility for the changes made to the NAT rule policies.

Adding objects or object groups on the firewall also do not generate a change notification.

There is no visibility for changes made to the secondary standby firewall if the firewalls are added as a cluster.

I've used the solution for more than five years.

We did not previously use a different solution.

We did not evaluate other options. 

We use it for planning firewall changes and traffic simulation queries.

We use AFA (AlgoSec Firewall Analyzer) and FireFlow. Our network environment is mostly on-premises.

It has improved the way our organization functions in that, for our change process, we now require all changes to be planned using AlgoSec so that the security team has visibility into the changes and we're aware of any risks. We also are using the covered rules and risky-rule detection to improve our security posture.

We haven't fully implemented the processes, so we haven't measured any reduction in human error as a result of using the solution, but subjectively, it has reduced human error.

It has also helped to simplify the jobs of our security engineers.

The most valuable features for us are the functionality it provides for our two main use cases: planning firewall changes and traffic simulation queries.

We haven't used it yet to prepare for audits and ensure our firewalls are in compliance, but I think it will be very helpful for that. That's one of the main reasons we bought it.

We are using it with a couple of Cisco technologies and we're also sending events out to our Microsoft Sentinel workspace. We have a couple of other security technologies in there as well. AlgoSec integrates well with the Cisco ACI environment and with our Firepowers, our FTDs. There are still some bugs but it generally works well.

The overall visibility it gives us into our network security policies is pretty good but it has some bugs and shortcomings. It doesn't support all features on our firewalls. For instance, planning changes, which include net rules, doesn't work. It didn't integrate so well with the ACI network. It doesn't work with all firewall rules or with net rules on our firewalls.

For about 70 percent of firewall changes it does show us the risks, while for 30 percent of the changes, we can't plan because of these bugs and shortcomings.

I have been using AlgoSec for about a year.

The stability is good.

We've had no problems in terms of scalability.

I'm sure we will continue to add firewalls to it and we want to do more with the FireFlow.

Their technical support is good but it can be slow.

Neutral

The initial setup was straightforward.

We have about 10 engineers using it, and just one person who looks after it, maintenance-wise.

We used their personal services to help us set it up. We had an onboarding package. It wasn't me doing the configuration but it seemed straightforward with their support.

Our experience with them was good overall. We had some frustrations and surprises in the early days with the product not being completely compatible with our environment. But over the last year, they've been fixing the bugs which is making it much more usable. When we started, it had a lot of problems with our environment. We were only able to plan something like 40 percent of the changes, and the traffic simulations weren't working with our network environment. But now, we're up to close to 70 percent.

It took about nine months before it was properly integrated and enough of the bugs had been fixed for it to be helpful.

We are not measuring the effort saved or the errors avoided, but we think it's a good investment.

Initially, it was more expensive, but we managed to negotiate the price. It's about average now.

In addition to the standard fees, we bought the Jumpstart package to help us configure it.

We looked into Tufin. We chose AlgoSec because of its support for Cisco ACI. Tufin was just releasing that and we felt that AlgoSec was a more mature product.

At the moment, it hasn't reduced the time it takes to implement firewall rules in our organization. It's being used to improve the quality of the changes we make and improve visibility. But we haven't fully implemented the FireFlow features. That's our problem, rather than the tool. We just haven't finished implementing it.

We're only using AlgoSec for on-premises, but we do have environments in the cloud and we plan to use it for those in the future. It would help us manage these multiple environments in a single pane of glass, but for the moment we aren't using it in that way. However, we do have a number of firewalls that we have onboarded from acquisitions, so we are not just using it for our data centers. We're using it for smaller acquisitions' firewalls as well to understand the security posture of companies that we are purchasing.

My advice would be to make sure that the solution is completely compatible with whatever infrastructure you have. We should have spent more time evaluating its support for our infrastructure to avoid some of the problems or surprises we had when we implemented it.

As an administrator, I ensure the platform works as well as possible. We are responsible for everything on the platform, such as onboarding and offboarding devices and managing the information on there, access, etc. AlgoSec has a good security component, but we primarily use it as a network and firewall appliance. It communicates with firewall and router vendors and integrates well with major vendors, such as Palo Alto, Check Point, and Cisco. However, it has some limitations with other vendors. It depends on the brand, but all the vendors we use work well with AlgoSec. 

We use AlgoSec Firewall Analyzer, FireFlow, and AppViz. All of our AlgoSec devices are on-prem. We average about 15 users daily, at least. We divide AlgoSec users into requesters and actual users. Requesters have limited access to only FireFlow, where they can make a request. We have about 100 requesters and 20 direct users from the network, security, and other teams. 

AlgoSec made troubleshooting much more manageable. For example, we can quickly determine the cause of routing issues and do traffic simulations to discover if something is open. It helps us perform analysis faster. That's one of the significant advantages. 

AlgoSec simplifies the work of security engineers in two ways. First, it simplifies approvals. Every time a flow is requested, it goes to security for approval. The security team assesses the risk of each request and makes a decision based on that. Second, it made audits easier because analyzing firewalls and permitted traffic is effortless. All these little aspects don't seem like much, but they add up. We have lots of audits. The risk metrics help us to identify specific risks as long as we can define solid risk metrics. If that doesn't work, you can also use the API to gather much of that information.

FireFlow provides multiple ways to create tickets involving numerous teams. Our existing ticketing solutions are not as easily configurable. They have some more restrictions. AlgoSec is a significant improvement. It has considerably reduced the time we spend implementing firewall rules. For example, we had previously implemented some rules manually and others via FireFlow. We started to use FireFlow for all of them. Because even if the network review on FireFlow isn't as accurate, it's still a net reduction compared to the time it would take to implement everything manually. It's worth it to spend a little more time analyzing everything. We can select the firewall and let FireFlow take care of everything. It's not comparable because we can press a few buttons, and everything is done.

AlgoSec reduced human error and misconfigurations, especially in terms of firewall implementation. AlgoSec doesn't make many mistakes. Implementation errors are rare. For example, let's say that we are trying to analyze something. Creating things by hand requires us to look at a file with 25 lines. It's easy to forget something, but AlgoSec doesn't forget anything. 

AlgoSec provides us with all the information, and we have to check to see if it's working correctly. Of course, it's not perfect. Sometimes there's some routing missing. When it doesn't implement something, AlgoSec usually informs people it's not going to. 

My company is a massive enterprise with several DCs globally and various types of environments. In addition to those DCs, they also have several subsidiaries, so it's a giant network. We work on incorporating all these environments into a single pane of glass using AlgoSec. Previously, every DC had its own AlgoSec, but we're currently merging them all into a single global AlgoSec because it's best to have everything in one place managed by the same people. It will enable us to control and standardize everything. It's also better in terms of visibility. 

We have integrated AlgoSec with Cisco ACI, but I wouldn't say it adds much. ACI is replacing our previous architecture, which was also Cisco. It's mostly the same. The way AlgoSec collects information hasn't changed much. ACI is good at organization, but it doesn't add much to AlgoSec's security functions. AlgoSec comes in handy during cloud migration. 

When migrating to the cloud, we typically extract information from old servers and provide that to the migration technicians so they know what they need to open for the new server. If the migration goes well, we aren't usually too involved with it. Afterward, if they find issues, we can help detect them and understand why something is missing.

FireFlow is great. In a company that gets a large volume of requests to open firewall rules, it's helpful to have one place that summarizes the requests, enabling you to clearly understand why they need to be implemented and also implement them. Firewall Analyzer can help you identify missing routing or check information on the firewall without the need to log into a firewall or router to check the routing. We have all that access in three clicks.

AlgoSec provides excellent visibility. We can easily see our devices, how they're connected, and what information is on them. AlgoSec allows you to define your own risk metrics based on a set of rules. It gives you a report based on that, so it's highly customizable. 

A few features could be more customizable. For example, one of our issues is related to the comments. When using FireFlow and ActiveChange, the comments by AlgoSec can be changed, but they always have the FireFlow number first. That's mandatory. It can be a bit bothersome because that's sometimes not exactly what we want. The templates we use have some scripts running in the background that aren't easy to change or remake. 

These options could be improved. Some features take time to learn and understand. It would be hard to figure out without AlgoSec support. Every bug or every problem we encounter is challenging to understand and fix without them. We try to solve our own issues, but sometimes we can't, and we need AlgoSec support. 

I've been using AlgoSec for a year and a half.

I think the solution is pretty stable. There has rarely been an instance when we needed to reboot to fix something. It has happened, but it's uncommon. Overall, I would say it's highly stable.

The scalability is excellent. We are changing the architecture, including the remote agent. It has been easy to scale like this. 

I rate AlgoSec support a six out of ten. Our experience has been inconsistent. Sometimes, support is fast and clean; other times, not so much. Occasionally, they take a while to respond or provide an inadequate workaround instead of a solution. It also depends on the support we purchase because AlgoSec has different levels. The premium levels have 24-hour support. 

Neutral

I wasn't involved in the initial setup, but we had a migration in which we changed the server where it was hosted and changed the architecture a bit. It was pretty simple. We had the support of AlgoSec engineers, so it went smoothly and quickly. We have two platform administrators and a third person who is the product owner. He helps us a lot, especially with the bureaucracy and everything, but we can primarily manage the solution well with two people. 

We've seen a return on investment. We continue to use AlgoSec a bit more each day. We're not investing more in AlgoSec monetarily, but we're investing time into learning its features so we can use it to the fullest extent.

It comes down to the amount of work AlgoSec reduces. The volume of flow implemented monthly would be challenging to handle manually. It would take much longer to analyze and execute. Not counting security, one guy using FireFlow is enough to implement requests these days. One member of the network team and one person from security can implement all the requests within our SLAs. I'm unsure how many people we would need to do that manually. It would probably take five times as many people to do the same work. That's not even counting all the security and troubleshooting benefits AlgoSec provides. 

I know AlgoSec can be expensive. I've heard from some of the platform users who worked at other companies that wanted to use AlgoSec, but it wasn't within their budget. Large enterprises can use it if they have a huge network with several devices. It's worth the cost if they spend a lot of time auditing and dealing with security concerns. It pays off in the long run.

You must pay for the basic AlgoSec license and the number of devices onboarded. There are licenses per firewall and network device. I believe you also must pay extra for firewalls with ActiveChange. I don't know the precise figures because I don't work with them, but I think they change. 

I rate AlgoSec a nine out of ten. It makes life easier. Without AlgoSec, you need to deal with one or two layers of extra work, doing tasks manually and logging into devices to run commands. It simplifies a lot of daily work. I've grown accustomed to the ease of use, so it'll be hard to adapt if I get a new job at a place without it. 

The solution is excellent, but you need to customize it for your own purpose. Before I joined this company, the previous administrators worked closely with AlgoSec support to build the platform to their specifications. They were the ones that customized what we needed. After that, everything is straightforward. There are a few tweaks here and there, and everything is good to go. The biggest hurdle is getting started. It's good to work with support. If not, we'll constantly be dealing with modifications, bugs, errors, and stuff that doesn't work. Getting the platform right in the beginning makes it a lot easier.

We use Firewall Analyzer from AlgoSec. We are mainly using AlgoSec Firewall Analyzer for auditing and analyzing firewall configurations. We have added different vendors inside AlgoSec for analysis. We have added Palo Alto firewalls, Fortinet firewalls, and Cisco firewalls. We are using all of these in our network.

There's an option to collect logs and send them to AlgoSec, but we are not using this option. We have other solutions for this purpose. We have Darktrace, IBM QRadar, etc.

In terms of our network environment, for the on-prem network, we have different security zones. For the data center, we have different DMZs for internal applications. We have different networks in different locations connected to our corporate network. About 90% of our applications are on-prem, and we only have the websites on the cloud.

It's helpful for auditing firewall configuration. If there is any mistake on the configuration side, it helps us to fix it. If there is a complication or there are unused security policies, it suggests removing or double-checking them. It's a good product. It's stable and gives us accurate results.

We have a network with more than 10,000 users. We have a lot of security devices for finance, remote sites, and corporate. AlgoSec is helping us to review and do auditing of the security device configuration. It's helping us to audit and review the configuration for any mistakes for firewalls, web application firewalls, proxies, etc.

When we add a security device, such as a firewall, it analyzes the configuration files for the firewall and gives us a brief of everything, such as security policies, routings, and objects. It lets us know if there is any mistake in the configuration, which is helpful for us. It gives us good visibility of what we have inside our security devices. For example, one of the firewalls that we have has more than 500 security policies. With manual auditing, we cannot analyze or review such a huge configuration. So, we are using AlgoSec Firewall Analyzer for this purpose, and it has saved more than 70% of our time.

It reduces human errors and misconfigurations. It lets us know if there haven't been any traffic hits for a policy for a long time. We can then review the configuration to see why there are no new hits for this. We are reviewing all of this every six months. It makes our work easier. It simplifies the job of security engineers.

Being able to analyze the environment and audit firewall configuration is most valuable. We are working here in the oil sector, and it's a critical environment. Every six months we have auditors coming from the main office and doing auditing for security. We are using AlgoSec Analyzer to help us to do the audit before the auditors come to our office and do the auditing of our security devices. So, it's helping us to do good work and analyze all security devices, including firewalls.

My only concern is related to how they count the number of licenses. We have active and standby devices. If someone adds the standby device by mistake and does an analysis, it consumes two licenses. They need to improve the way they are counting the number of licenses because someone can do analysis on a standby device by mistake. We need a way to fix or solve this issue.

I noticed that some of the oil companies in Kuwait have started to use AlgoSec Analyzer. I see AlgoSec solutions in Kuwait. AlgoSec needs to have sales engineers here. They should have presales or sales consultants so that they can offer solutions to companies in Kuwait.

We have been using AlgoSec for more than four years.

It's a stable solution.

It's scalable. We have 10,000 users accessing services and the internet. We only have two users who are accessing and working with AlgoSec. They are security engineers.

They are cooperative. If we face any issues, we just send an email or open a case through the portal. We can contact them directly. We don't face any issues with their support. I would rate them a 10 out of 10.

Positive

I have not used other tools. We know AlgoSec is a leader in this industry. We haven't faced any issues in the last four years while using the AlgoSec solution. We haven't done any research on other solutions because we haven't faced any issues with AlgoSec.

It's very easy to do the initial setup. It's not a big issue. In about two days, you can configure your device, activate the license, and add security devices. If you have an admin account, you can allow AlgoSec Analyzer to access security devices. 

Its management is not a big issue. Only one person can maintain it.

We have seen an ROI. That's why we got this solution. We knew how we would use it and what would be its benefits. We have seen about 60% or 70% ROI.

We purchase licenses based on the number of security devices in our network.

When I have active and standby firewalls, if I do an analysis of the active firewall and by mistake, I also do an analysis of the secondary or standby firewall, it'll consume two licenses from the total number of licenses I have. So, I need to change the license and make the active firewall secondary. They need to improve how they are counting the number of licenses. We have discussed this with the consultation team of AlgoSec.

I would rate it a 9 out of 10. It's a good product. It's working fine without any issues. We don't face any issues. Our only concern is how they are counting the total number of licenses.

With AlgoSec, I hope to achieve network visibility, application connectivity, and so on, which is the way it was designed.

I am hoping AlgoSec will help solve specific problems by clearing and speeding up change management while providing needed network visibility and simplifying management.

AppViz stands out to me, and I think all of the features are interesting; AppViz is a really cool thing.

My experience with using the best features AlgoSec offers is minimal, but I am most excited to try AppViz.

Based on my initial impressions, I think there's room for improvement, but I haven't encountered anything that stood out as confusing or challenging.

I have not been using AlgoSec for very long.

My experience with customer support has been perfect.

I would rate the customer support a 10.

Positive

I previously used Skybox before considering AlgoSec, but I decided to switch because Skybox ended.

I evaluated other options before choosing AlgoSec, but I don't know the names of them.

My advice for others looking into using AlgoSec is that it's great, so do it.

I choose to rate AlgoSec 10 out of 10 because it is the best solution for our use case.

I was indeed offered a gift card or incentive for this review.

I have no additional thoughts about AlgoSec before we wrap up.

We have four firewalls and two routers in our environment. We also have a business application. At first, it was very difficult to connect to each firewall individually, see my environment as a whole, and determine where traffic was being blocked and who made changes. AlgoSec provides a solution to all of this in a single platform.

Being able to see where traffic is blocked using traffic simulation provides me with great convenience. Additionally, with FireFlow, I can handle this in a single action instead of taking actions on each firewall individually.

Thanks to Algosec, especially with the FireFlow and AppViz modules, I have managed the regulation compliance I need to adhere to through baseline compliance and checked my compliance with it. Without connecting to my firewalls one by one, I was able to handle all my changes with FireFlow in a single-handed manner according to a specific plan. I was able to clearly see the accesses to the application in my environment and the vulnerabilities of the application. The reports section was very useful in tightening up my policies.

Country-specific regulations should be added when required. Doing this on my own with baseline compliance is quite difficult.

Additionally, I would like AlgoSec to provide suggestions such as "this object includes that object" for my objects on the Check Point firewall. For my Fortigate manager, the support of the active change feature is important to me. 

Lastly, the FireFlow interface could be simplified a bit more. I agree that it is user-friendly, but on the other hand, it can be difficult to organize and find certain things.

I have been using AlgoSec for one year. 

We haven't encountered any interruptions while the product is running. It operates very stably.

We can add devices very quickly whenever we need to, with additional licenses.

I received sufficient and useful responses within a maximum of one day.

Positive

Straightforward. We imported the ova file and that's all, then just clicked add devices.

It has been a very useful and suitable investment for us.

The setup is very easy, and while I can't say anything definitive about the pricing in terms of competition, licensing is also quite straightforward.

We have tried Tuffin.

Our primary use of AlgoSec is to ensure the smooth operation of our network infrastructure. 

We are responsible for device onboarding and offboarding, managing access, and overseeing information security. While AlgoSec offers robust security features, we primarily utilize it for network and firewall management. 

It integrates seamlessly with major vendors like Palo Alto, Check Point, and Cisco, although there may be some limitations with other brands. We employ AlgoSec Firewall Analyzer, FireFlow, and AppViz, all of which are deployed on-premises. On average, we have around 15 daily users, including requesters and direct users from various teams.

AlgoSec has significantly enhanced our troubleshooting capabilities. We can quickly pinpoint the causes of routing issues and conduct traffic simulations to identify potential problems. This has streamlined our analysis processes, which is a major advantage.

Moreover, AlgoSec simplifies the work of our security engineers in two key ways. First, it streamlines the approval process for flow requests, with the security team assessing risk and granting approvals. Second, it facilitates audits by providing effortless access to firewall configurations and permitted traffic data, making compliance checks much smoother.

FireFlow, a component of AlgoSec, has been particularly valuable for us. It serves as a centralized platform for managing firewall rule requests, making it easy to understand and implement these requests efficiently. Additionally, Firewall Analyzer helps us identify missing routing information and check firewall status without the need to access individual devices.

AlgoSec has significantly reduced human errors and misconfigurations, especially during firewall implementation. It provides comprehensive information, minimizing the chances of oversight or omission. While it's not flawless, it typically alerts us when something cannot be implemented, ensuring transparency.

The standout features of AlgoSec include FireFlow, which simplifies firewall rule management, and Firewall Analyzer, which enhances visibility by identifying missing routing and firewall data. AlgoSec's flexibility in defining custom risk metrics and generating reports based on them has been highly beneficial.

AlgoSec's scalability has been excellent for our needs. We've made architectural changes, including incorporating remote agents, and scaling up has been straightforward. The integration with Cisco ACI has been somewhat seamless, although it hasn't added significant functionality to AlgoSec's security features.

We've also found AlgoSec invaluable during cloud migrations. It aids in extracting information from old servers to guide migration technicians on what needs to be opened for new servers.

While AlgoSec offers many advantages, there are some areas for improvement. Certain features, like comments in FireFlow, could be made more customizable. Additionally, some features require a learning curve and may necessitate support from AlgoSec, which can be challenging at times.

While AlgoSec offers many advantages, there are some areas for improvement. Certain features, like comments in FireFlow, could be made more customizable. Additionally, some features require a learning curve and may necessitate support from AlgoSec, which can be challenging at times.

I've used the solution for one year.

We didn't use a different solution.

We did not evaluate other options. 

Our team operates within the support division, assisting customers who primarily utilize AlgoSec through on-premises deployments. They rely on this solution to analyze and manage firewall policies, enhance their security measures, and receive recommendations for optimizing their firewalls.

Specifically, we utilize the AlgoSec Firewall Analyzer component of the solution. Recently, we conducted a proof of concept (POC) of AppViz for a customer who utilizes FireFlow. This POC was successful, and it is likely that some of our other customers may express interest in implementing AppViz within the coming year.

Implementing firewall rules within our organization has been significantly expedited thanks to AlgoSec. 

This product plays a crucial role in preparing us for audits and ensuring firewall compliance. With its assistance, we are able to assess security and firewall rating points, offering valuable advice to our customers regarding the optimization of their firewall and security rules.

One of the key benefits of AlgoSec is its ability to simplify the tasks of our security engineers. By providing essential guidance to administrators responsible for managing firewalls, streamlines their responsibilities and enhances their efficiency in carrying out their duties.

The Firewall Analyzer component of the solution offers remarkable compatibility and proves to be highly valuable and easily manageable.

Our customers have found the Intelligent Policy Tuner to be incredibly helpful, and during the proof of concept (POC), it emerged as a significant selling point for our clients. They expressed great interest in utilizing this feature.

Setting the log options to "extensive" provides us with excellent visibility into our network security policies. This extensive logging enables us to generate detailed reports and receive change notifications, thereby enhancing our overall visibility.

AlgoSec plays a crucial role in providing comprehensive visibility into the risks associated with firewall change requests. This feature proves especially important when presenting security reports to upper management.

The solution's automation capabilities significantly contribute to reducing human error and misconfigurations. If the tool detects a drop in security and firewall policy points, it promptly notifies administrators via email about potential misconfigurations. This proactive approach allows us to promptly address and rectify any issues, ensuring that the security and policy points are restored.

Introducing greater flexibility in editing alerts would be a highly appreciated improvement.

The solution currently faces visibility and compatibility challenges when it comes to Palo Alto firewalls, making it difficult to generate reports. Since the reports heavily rely on logging, the product encounters obstacles with Palo Alto's logging system. Enhancing compatibility with Palo Alto firewall reports is crucial for seamless reporting.

A notable customer demand is the implementation of a user-based policy within AlgoSec. This feature would enable the solution to provide advice on user policy rules while also ensuring compatibility with identity awareness functionalities. Meeting this customer requirement would be highly beneficial.