Integration with Oracle on the cloud is not supported. I would also like to see integrations with network devices in Layer 2. While it's very focused on some goals that we must apply for security, everything related to network devices, it would help if we could double-click on the network devices of Layer 2 for WiFi and other types of networks.
systems security engineer at a tech company with 1-10 employees
Real User
Dec 4, 2022
When we are integrating AlgoSec with a SAML or 2FA authentication tool, there is a small drawback to the solution. When we enter our user ID and password to log in, we get redirected to the console. However, there is no option to log out from the console. We have to close the entire web page in order to log off. The logout page is a mandatory feature that is missing from AlgoSec. AlgoSec cannot be integrated with solutions that require two-step or multi-factor authentication. Embedding multi-factor authentication capability into the solution would be a valuable feature.
Network Infrastructure Engineer at Cigna/Express Scripts
Real User
Oct 21, 2021
When we send multiple requests across at once, sometimes it causes errors and FireFlow gets stuck. In cases like this, we have to go back in and fix it.
Sr. Design Architect - Network Security at a retailer with 10,001+ employees
Real User
Aug 3, 2021
There is a little bit of scope for improvement in the risk profiles that come with the AlgoSec Firewall Analyzer module. Currently, AlgoSec provides only three standard zones within a risk profile. These standard zones are external, internal, and DMZ. Everybody's network is divided into different zones within a data center, but AlgoSec only provides three zones. This is a limitation that I see for the risk profile analysis. If there was an option to customize these zones, it would be great. Risk profiles currently require a lot of understanding. The UI needs a little bit of flexibility in terms of rearranging risk rules within a profile. For example, when I create rules in a risk profile, it numbers them as Rule 1, Rule 2, Rule 3, and so on. If I delete Rule 2, it doesn't reorder them on its own. Rule 2 is deleted, but I just cannot place any other rule as Rule 2. There needs to be more flexibility in building risk profiles. We would like to have AlgoSec integrate with Cisco SD-WAN. We are a retail company, and we have about 2,500 stores. We have the SD-WAN solution across all stores. So, we need to manage a high number of zone-based firewalls. If AlgoSec can add integration with Cisco SD-WAN in the roadmap, it would be awesome. After you add a load distribution node, there is no dashboard to tell us how the performance has improved. I can raise a couple of tickets, or I have to do a lot of permutation and combination in terms of testing to figure out whether it has really optimized the process and latency. If we can have a performance dashboard to give us information about the performance change with the AlgoSec tool, it would be great.
The analysis part can be improved when I make a flow request. There should be a clear analysis of which metric part needs to be opened and which firewalls will be opened. It should give you a bit more graphical visibility about these. I don't know if it's possible, but there could also be policy enforcement. The reason why firewalls have problems is that standards are not being followed. If the tool that allows you to enter a request doesn't enforce standards, there's too much room for error. Automation does not solve this unless automation follows defined policies and standards. I don't know to what extent those tools can indicate the predefined policy and standards that you put in place. For instance, if you define your level of zero trust, the tool should be able to advise you on what you should do.
Cyber Security Architect at a tech services company with 5,001-10,000 employees
Real User
May 24, 2021
The API integration could potentially improve. I didn't get a chance to look and see how well this solution can integrate with ServiceNow or our GRC environment.
IT Security Analyst at a retailer with 5,001-10,000 employees
Real User
May 3, 2021
We work with multiple security vendors. It's rather difficult to integrate the vendors. AlgoSec is a platform that hasn't really been developed as much as we would like to just because of its complexity to set up. If it was easy to set up and easy to get integrations with other companies, then we would be doing it. But the thought is that we are relatively stretched thin in our team as it is and the complexity of configuring AlgoSec doesn't make it any easier. Overall, setting up new features is something that needs improvement in my eyes. It has a cool feature where it has multiple firewall rules that say "You're allowing this IP page address to talk to this IP address on port A, port B, and port Z." For example, if AlgoSec detects that that rule was being used but it's only being used for port B and C, then it'll actually notify you that this rule can be trimmed down and you can remove port A, as it's not being used by your rules anymore. That's something we really like as well.
Consultant at a consultancy with 10,001+ employees
Real User
Top 10
Apr 22, 2021
We would like the full features of automation. That would definitely be helpful. Then, we would be capable of pushing policies to the Algosec as well as finding the path. We would like to get the network nodes from all the different firewall analyzers. For example, in Tufin, we can find other network tools, like router switches, which show the path between source and destination.
Prevasio is an agentless cloud-native application protection platform (CNAPP) that provides increased visibility into security and compliance gaps, enabling cloud operations and security teams to prioritize risks and ensure compliance with internet security benchmarks.
Prevasio combines cloud-native security with SRI International's proprietary AI capabilities and AlgoSec’s expertise in securing 1,800 of the world’s most complex organizations.
Integration with Oracle on the cloud is not supported. I would also like to see integrations with network devices in Layer 2. While it's very focused on some goals that we must apply for security, everything related to network devices, it would help if we could double-click on the network devices of Layer 2 for WiFi and other types of networks.
When we are integrating AlgoSec with a SAML or 2FA authentication tool, there is a small drawback to the solution. When we enter our user ID and password to log in, we get redirected to the console. However, there is no option to log out from the console. We have to close the entire web page in order to log off. The logout page is a mandatory feature that is missing from AlgoSec. AlgoSec cannot be integrated with solutions that require two-step or multi-factor authentication. Embedding multi-factor authentication capability into the solution would be a valuable feature.
When we send multiple requests across at once, sometimes it causes errors and FireFlow gets stuck. In cases like this, we have to go back in and fix it.
In the new version H32, there are many, many bugs.
There is a little bit of scope for improvement in the risk profiles that come with the AlgoSec Firewall Analyzer module. Currently, AlgoSec provides only three standard zones within a risk profile. These standard zones are external, internal, and DMZ. Everybody's network is divided into different zones within a data center, but AlgoSec only provides three zones. This is a limitation that I see for the risk profile analysis. If there was an option to customize these zones, it would be great. Risk profiles currently require a lot of understanding. The UI needs a little bit of flexibility in terms of rearranging risk rules within a profile. For example, when I create rules in a risk profile, it numbers them as Rule 1, Rule 2, Rule 3, and so on. If I delete Rule 2, it doesn't reorder them on its own. Rule 2 is deleted, but I just cannot place any other rule as Rule 2. There needs to be more flexibility in building risk profiles. We would like to have AlgoSec integrate with Cisco SD-WAN. We are a retail company, and we have about 2,500 stores. We have the SD-WAN solution across all stores. So, we need to manage a high number of zone-based firewalls. If AlgoSec can add integration with Cisco SD-WAN in the roadmap, it would be awesome. After you add a load distribution node, there is no dashboard to tell us how the performance has improved. I can raise a couple of tickets, or I have to do a lot of permutation and combination in terms of testing to figure out whether it has really optimized the process and latency. If we can have a performance dashboard to give us information about the performance change with the AlgoSec tool, it would be great.
The analysis part can be improved when I make a flow request. There should be a clear analysis of which metric part needs to be opened and which firewalls will be opened. It should give you a bit more graphical visibility about these. I don't know if it's possible, but there could also be policy enforcement. The reason why firewalls have problems is that standards are not being followed. If the tool that allows you to enter a request doesn't enforce standards, there's too much room for error. Automation does not solve this unless automation follows defined policies and standards. I don't know to what extent those tools can indicate the predefined policy and standards that you put in place. For instance, if you define your level of zero trust, the tool should be able to advise you on what you should do.
The API integration could potentially improve. I didn't get a chance to look and see how well this solution can integrate with ServiceNow or our GRC environment.
We work with multiple security vendors. It's rather difficult to integrate the vendors. AlgoSec is a platform that hasn't really been developed as much as we would like to just because of its complexity to set up. If it was easy to set up and easy to get integrations with other companies, then we would be doing it. But the thought is that we are relatively stretched thin in our team as it is and the complexity of configuring AlgoSec doesn't make it any easier. Overall, setting up new features is something that needs improvement in my eyes. It has a cool feature where it has multiple firewall rules that say "You're allowing this IP page address to talk to this IP address on port A, port B, and port Z." For example, if AlgoSec detects that that rule was being used but it's only being used for port B and C, then it'll actually notify you that this rule can be trimmed down and you can remove port A, as it's not being used by your rules anymore. That's something we really like as well.
We would like the full features of automation. That would definitely be helpful. Then, we would be capable of pushing policies to the Algosec as well as finding the path. We would like to get the network nodes from all the different firewall analyzers. For example, in Tufin, we can find other network tools, like router switches, which show the path between source and destination.