AlgoSec Reviews

Our main use case for AlgoSec is automating firewall policy management and compliance auditing across multiple firewall vendors, which helps us reduce manual rule reviews and improve visibility into network security changes.

We use AlgoSec to automate firewall rule change requests, so when an application team needs new network access, the tool analyzes the path, checks compliance risk, and helps implement the rule much faster than our previous manual approval process.

Besides firewall policy automation, we also use AlgoSec for compliance reporting and network visibility, which helps us identify unused or risky firewall rules and prepare for security audits more efficiently.

AlgoSec has improved our network security operations by reducing manual firewall management work, speeding up rule change approvals, and helping us maintain better compliance visibility across different security devices.

After implementing AlgoSec, firewall change requests that previously took days of manual review were often completed within hours, and the automation significantly reduced configuration errors and time spent preparing compliance audit reports.

The best features of AlgoSec in my experience are automated firewall rule analysis, risk and compliance reporting, application connectivity mapping, and multi-vendor firewall support because they make security policy management much faster and reduce manual errors from the networking.

The automated firewall rule analysis in AlgoSec helps our team quickly identify risky, unused, or conflicting rules before changes are implemented, which reduces manual review time and helps avoid security or connectivity issues during firewall updates.

One feature I also find very useful in AlgoSec is the application connectivity mapping because it gives clear visibility into how applications communicate across the network, which makes troubleshooting and migration planning much easier.

One area where AlgoSec could improve is the UI and UX because navigating complex workflows in policy analysis and reporting can feel heavy at times, especially for new users. Better dashboards, simplification, and faster drill-down into rule-level insights would make day-to-day operations smoother.

Another improvement for AlgoSec would be more intuitive reporting customization and faster integration setup for newer cloud-native environments, since aligning hybrid cloud policies sometimes requires extra effort and configuration tuning. Improving real-time change simulation and recommendations would also help, as the impact analysis could be even more interactive and easier for non-specialist teams to understand before a firewall rule is pushed.

One additional improvement for AlgoSec would be deeper native support for modern cloud-native services and Kubernetes environments because policy visibility and rule mapping in highly dynamic cloud workloads can still feel limited compared to traditional firewall environments.

I have been using AlgoSec for one year.

Overall, AlgoSec has been very effective for improving firewall governance, reducing manual effort in rule management, and strengthening compliance visibility across our hybrid network environment. It is especially valuable once the initial setup and network mapping are in place.

My advice for anyone considering AlgoSec is to first map out your firewall and application dependencies clearly before implementation because the tool delivers the most value when your network inventory and policy structure are well-organized from the start. I would also recommend starting with a pilot on a small segment of your network and involving both security and network teams early, because AlgoSec works best when policies, firewalls, and application owners are aligned before scaling it across the full environment. I would rate this product a 9 out of 10.

Hybrid Cloud

Amazon Web Services (AWS)

My main use case for AlgoSec is to manage firewall rules and control network access in a centralized way, so instead of logging into individual firewalls, we have them connected to it and use its rules to process access requests all from one place.

For example, when the application team asks to allow access from server A to server B, we can use AlgoSec to see if the rules are there and it checks which firewall.

Recently, the application team has requested to allow access from server A to server B; with the help of AlgoSec, we have identified the firewall and AlgoSec suggested the exact change, so we have gone and applied it.

AlgoSec has positively impacted our organization by improving firewall change management, leading to fewer mistakes, better visibility, and easier audits.

Since we are using this solution, we have seen that the number of firewall mistakes has been reduced by 90% and we are getting visibility on the connection.

The best features that AlgoSec offers include traffic path analysis and risk analysis to check if the rule is safe.

Out of those features, I find myself mostly using risk analysis and traffic analysis the most because they are really useful for the real environment.

I believe there is no need for improvement in AlgoSec. I think it is an excellent solution.

I have been using AlgoSec for three years.

AlgoSec is stable.

AlgoSec is a very scalable solution; it can handle a thousand firewalls.

The customer support for AlgoSec is excellent, as they are good in their technical competencies.

Since the beginning, we have been using this solution, so I have not used a different solution before AlgoSec.

AlgoSec is providing less manual work and faster changes, with no need to increase the team size.

My experience with pricing, setup cost, and licensing was straightforward, and there is no issue with these areas.

We have not evaluated any other options before choosing AlgoSec.

My advice for others looking into using AlgoSec is that it helps to manage firewall rules easily, getting changes with traffic and checking it. I am providing this review with a rating of 8.

On-premises

Other

My client is from a finance background and has more than 100 firewall clusters deployed, that too from different OEMs, for added security. Thanks to historical reasons, some of the firewall policies are poorly managed with tons of rules, and nobody knows what policies are in use and what are not, what policies are redundant, and what are vulnerable.

On top of this, the client Info-sec policy enforces strict one-to-one rules, which, considering the size of the business, leads to the implementation of hundreds of new policies every week.

Firewall Rule analysis & New rule implementations were a challenge, and there comes the AlgoSec.

We started using AlgoSec to review existing firewall rules. To our surprise, thousands of policies were redundant, and many risky rules were also present.

Due to their large rule bases, firewalls used to have high CPU usage during peak business hours. The client was able to remove redundant rules and strengthen risky rules to save the network from compromises.

Implementing firewall rules was another challenge. The same rule had to be implemented on multiple firewalls from different OEMs. AlgoSec made our life easy.

Both analysis and Implementation engines/features are found to be very much valuable since they helped the client to manage the show better.

Implementations used to take a long time, both in terms of approvals and manual implementations. Errors during implementation were another challenge. Delays in policy implementations impacted new feature rollouts or application developments. AlgoSec auto implementation came into the picture, which helped the right departments to approve policies and implementations.

AlgoSec is slow when it is loaded with too many firewalls and policies. A plan to take care of heavy usage is to be considered. Support of all firewalls and policy features to be enabled.

AlgoSec should support in identifying most hit rules and re-ordering existing firewall rules - this is a very key to manage firewall CPU.

A clustering of AlgoSec can also be considered. A group of AlgoSec servers managing large client bases geographically or datacenter-wise or function-wise. A head reporting unit and child processing units.

I've used the solution for seven years.

The stability is good.

The solution needs to improve scalability.

The customer service is good.

Positive

No other solution used before.

The initial setup was straightforward.

The implementation was handled in-house.

I am into operations and not aware of cost or pricing. 

AlgoSec was the only option considered.

On-premises

I used AlgoSec for risk assessment and managing firewall rules, including risk assessment and firewall policy automation.

My use of AlgoSec included the FireFlow module, which is a firewall automation tool. Additionally, AlgoSec's risk analysis module was beneficial.

The user interface for AlgoSec has remained unchanged for the last ten years and could benefit from being more interactive and informative. Additionally, a cloud offering as a SaaS would relieve the burden of managing hardware, applying numerous patches, and monitoring the health state of the solution. Implementing a SaaS service would allow for immediate value realization.

I used AlgoSec from 2020 to 2025, approximately four to five years.

I rate the stability at eight out of ten, indicating a reasonably stable solution.

I rate the scalability at nine out of ten, demonstrating a robust ability to expand and cater to large enterprises.

I rate customer service at six or seven out of ten. Both response time and quality need improvements. While there is a dedicated engineer program that provides consistent support, regular support without this subscription is lacking.

Neutral

At my previous company, I used AlgoSec but shifted to using Tufin in my current role.

The setup process for AlgoSec is fairly simple.

Pricing for AlgoSec is fairly competitive. Rating the pricing on a scale from one being high to ten being low, the price is considered competitive without being specified absolutely.

I currently work with Tufin and have observed that AlgoSec is slower in adopting new technologies like cloud compared to Tufin and FireMon. Tufin and FireMon are leaders in technology change adoption.

My overall rating for AlgoSec, based on my last experience in January, would be seven out of ten. AlgoSec is suitable for enterprises that manage about 300 firewalls, and the burden on the solution is more about the number of firewalls and policies managed rather than the number of users. For technical functionality, I find Palo Alto to be better since AlgoSec does not support time-based objects or specific categorization groups.

On-premises

AlgoSec's primary use case is for change auditing and change monitoring on security devices. It helps in receiving regular alerts about changes happening on devices, making it much easier to audit those changes, identify any issues, and figure out which recent changes caused them.

We experienced a critical issue when our perimeter firewall, which was a Check Point firewall, was not processing traffic. All traffic through our data center going towards the internet and requests coming from the internet to our data center were not working, creating a complete outage situation. To identify what caused it, I verified the AlgoSec logs through the auditing functionality and checked the recently made changes that might have caused the issue. This helped us determine what changes were made recently. We rolled back those changes, and the issue was fixed without spending more time on troubleshooting.

AlgoSec also helps us in auditing. We have auditing happening every year, and we track what changes we make, what the change requests were against those particular changes, and ensure that changes had required approvals in place, making overall auditing and compliance easier for us.

The standout feature of AlgoSec is real-time monitoring and alerting. We receive emails for every change that happens on any of the devices, with the ability to customize the email and integrate it with ticketing tools to review whether a change request was raised or not. AlgoSec also provides historical auditing of the devices with changes, allowing us to store logs at an external syslog.

In my day-to-day work, I rely most often on real-time monitoring and change auditing.

The impact of AlgoSec on my organization has been positive. Manual intervention has completely decreased because when the compliance or legal team comes to us asking about what changes happened in the last quarter or two quarters, it used to be a manual task. Now we can export the logs within a few minutes by selecting the target device and the time period for the changes, making it very much less time-consuming and more productive.

I would like to see automation support on AlgoSec, allowing me to run scripts and API calls to export whatever I need.

I have been using AlgoSec for more than two years, and I also used it in my earlier experience when I was part of previous companies.

AlgoSec is quite stable in my experience with no downtime or reliability issues.

AlgoSec handles growth well, demonstrating good scalability.

When we are unable to export audit logs for a specific firewall or device, we raise the case with their support team and receive timely help from them. I can give the customer support a rating of ten. Although I did not have many requests, I received timely assistance whenever I raised a case.

We did not use a different solution earlier, but we did explore various products while selecting AlgoSec. Before choosing AlgoSec, we evaluated a few options, including NetMRI as one of the solutions.

I have seen a return on investment with AlgoSec. It is a complete time-saver, reducing the workload on the individual or team and enabling them to invest that time into more productive tasks.

If you are looking for an auditing tool to check or audit the changes happening around your network devices or security devices, and you want to export auditing logs or track changes, you should definitely evaluate AlgoSec. I would rate this review a nine out of ten.

Private Cloud

Other

In our company, we primarily use AlgoSec to analyze and optimize firewall policies. This solution is invaluable for cleaning up rules and objects. It allows us to identify which rules are redundantly covered by others, detect unused objects in rules or groups, and pinpoint duplicated objects. Additionally, AlgoSec aids us in reducing overly permissive rules that have accumulated due to legacy changes.

Our environment consists of several systems with different policies, all managed under a single management console. This unified approach helps us maintain a clean and efficient object rule base across the board. 

By using AlgoSec, we can ensure our firewall settings are both streamlined and effective, significantly enhancing our security posture. Furthermore, the insights provided by AlgoSec empower us to make informed decisions about which rules are necessary and which can be consolidated or removed, ultimately optimizing our network performance and security management process.

AlgoSec has significantly improved our organization by streamlining our firewall management process. With the use of AlgoSec FireFlow and AlgoSec Firewall Analyzer (AFA), we have been able to maintain clean and efficient firewall policies. AFA has been instrumental in helping us clean up existing firewall rules, ensuring that our policies are optimized and free of redundancies. By identifying and removing obsolete or duplicate rules, we have improved our network's security and performance.

FireFlow has been particularly beneficial in automating policy change processes, allowing us to keep our firewall policies clean and up-to-date. This automation not only reduces the potential for human error but also speeds up the implementation of necessary changes.

AlgoSec has saved us considerable time and energy when it comes to various tasks, such as risk analysis and assessing the impact of potential changes. By providing clear insights into which rules are already implemented and effective, we can focus our efforts on areas that truly need attention, ensuring our resources are used efficiently. Overall, AlgoSec's solutions have optimized our security management, enhancing both our operational efficiency and our ability to protect critical assets.

One of the most valuable features we've found in AlgoSec is its ability to analyze network flows to help define new, less permissive rules. This functionality is crucial for enhancing our network's security posture by ensuring that only necessary traffic is allowed. By examining the actual traffic flows within our network, AlgoSec provides insights into where existing rules may be too permissive, allowing us to tighten them without disrupting legitimate business operations.

This feature not only assists in making our security policies more precise but also helps in minimizing the attack surface by restricting unnecessary access. As a result, we can confidently implement rules that align more closely with the principle of least privilege while still accommodating essential connectivity and services. The ability to refine our firewall rules in this informed manner enhances both our security and compliance efforts, making this feature particularly valuable to our organization.

While AlgoSec offers robust capabilities, there are areas where the product could be further enhanced. One specific area that could benefit from improvement is the rule analysis feature, particularly in terms of defining objects within a new rule. Currently, the process seems to be more focused on network-level analysis rather than on objects, which sometimes requires us to perform multiple iterations to achieve optimal results.

Enhancing the tool to provide more object-oriented analysis could streamline the process of rule creation and modification, allowing for more precise and efficient policy management. Additionally, incorporating advanced capabilities for identifying and recommending the most appropriate objects for new rules would minimize manual effort and potential errors, thereby increasing accuracy and saving time.

For future releases, we would like to see more seamless integration between AlgoSec Firewall Analyzer (AFA) and FireFlow. Enhancing the connectivity between these tools would simplify transitioning from AFA to FireFlow, making it easier to create change tickets directly. This improvement would streamline our change management processes, enabling us to implement and monitor policy changes more efficiently and with greater accuracy.

I've used the solution for six months.

On-premises

We use app flow, Firewall Analyzer, and FireFlow. We use AlgoSec to gain visibility on firewall rules and for gap-cleaning projects to clean up the firewalls. We also use the solution as a firewall assurance tool to stay clean, have an optimized set of firewalls, and then automate firewall rules deployed from start to finish.

We have on-prem data centers and 180 sites all over the world.

Additionally, we use cloud services, infrastructure as a service, platform as a service, and software as a service. The majority of it is standardized on Cisco networking with Fortinet security solutions, except for the data centers, which are Check Point.

The purpose is to gain visibility into firewall rules. We used it to go through a gap-cleaning project to clean up the firewalls. We also use the solution as a firewall assurance tool to stay clean and to have optimized firewall rules. In addition, we use the solution to automate firewall rule deployment from start to finish, so we have a complete change process in FireFlow and can automatically deploy the firewalls on appliances. For that, we also built a connection with BMC Remedy because that's the main tool used for change management.

AlgoSec has improved our organization through a safer firewall rule base and better time-to-market IT services provided to the rest of the organization. Those are the two main improvements. In general, AlgoSec has provided a better security posture.

Customizability is AlgoSec's best feature. You can customize everything and build anything you like, and that's a feature we missed in competitors' solutions.

AlgoSec is not a tool where people with little knowledge of security or IT can find their way around. AlgoSec has a less user-friendly interface compared to competitors, but it is comparatively more customizable. As such, the interface is more on the complex side.

I have been using AlgoSec for four years.

AlgoSec is a stable solution. There are bugs, but those do not affect the system's stability. We have not had any unplanned downtime since we started.

We use the solution 24x7 to record cyber rules, with about 50 changes per week.

The solution is scalable and we have approximately 50 users.

The initial deployment was complex because we were integrating with ITIL systems since we had integrated with BMC Remedy. The integration with Check Point was complex because we were on the wrong version. We had to go through various administrative processes to update Check Point. If AlgoSec was more flexible in the ways one could integrate and the versions one could integrate it with, that would help.

A team of ten people handled the deployment, including testers, and they took approximately three months. The end-to-end deployment took just over two years. We did not migrate from a previous solution.

We have seen a return on investment only with efficiency gains and improved security posture. That might transfer to a monetary value, but we haven't assessed that.

I find the price too expensive. It looks a bit like SAP, so it does have standard functionality out of the box, but you will spend a lot of money if you want to customize it. However, the price is not as extreme as SAP or Oracle, but the actual implementation does turn out to be expensive. 

We finally chose AlgoSec over Skybox for its customizability, the options for integration, and the workflows. Though Skybox was much more user-friendly, it was weaker when it came to integration options and customizability.

In our organization, we work with multiple security vendors, and integrating with leading vendors for the most part is easy, but there are some exceptions. The solution made integration with the majority of devices really easy, but it was really cumbersome with some devices.

The solution has massively reduced human error through automation by about 95%.

As far as multiple environments are concerned, we have a private cloud, which is just a data center hosted by an external party. We have a public cloud, multiple vendors, and multiple regions. We also have decentralized data centers throughout the world.

We're investigating combining the solution with Cisco ACI.

The cost versus the achieved business goals is in balance.

I recommend that new users do a proof-of-concept before choosing AlgoSec. I would rate the solution an eight out of ten.

Hybrid Cloud

Other

Our primary use case is identifying unused tools and junk rules, including objects that are created but whose exact user and traffic cannot be tracked. I've deployed AlgoSec to address this use case, as it performs its job well by allowing me to block multiple unused rules and objects while permitting only the required traffic.

AlgoSec has helped streamline our environment by interacting with risky users and managing risky traffic. It has minimized manual involvement while providing clear, readable reports based on compliance standards.

One of the most valuable features of AlgoSec is its capability for identifying unused and risky rules, which cannot be done through manual analysis. AlgoSec analyzes logs and provides insights on risky rules and wide-open access scenarios, like when access was granted to too many users. It helps in minimizing security risks by allowing reporting and adjustments accordingly.

There should be improvements in the analysis between internal zones, such as internal to DMZ or guest to DMZ. These scenarios should be considered critical and enhancements should be made, even if the risk score is set high. Improvements are also needed in the area of PCI, specifically the PCI controller.

I have been using AlgoSec for about two years.

The solution is stable, and even if there are issues or it goes down, it does not impact the environment significantly.

Scalability is favorable since the solution is actively being developed. Specifically, for firewall perspectives, scalability is satisfactory.

Customer service is good as we have a dedicated person from the technical team who supports us whenever required.

Positive

Before AlgoSec, we were using Tufin, which required significant manual effort.

The initial setup was straightforward, taking only one or two hours. Once necessary components like VMs and CPUs are ready, implementation is seamless.

Initially, we had assistance from AlgoSec's technical team to set things up, but moving forward, no additional help is required.

I have not directly observed a reduction in costs or resources, but AlgoSec provides training when required, and they visit us for new feature introductions and solutions.

The pricing is manageable. While there are less expensive options available, AlgoSec provides a middle variance solution and is cost-effective in comparison to others.

AlgoSec minimizes manual efforts in creating compliance standards reports that are clear and readable.

Overall, I would rate AlgoSec nine out of ten.

Private Cloud

Other