What is our primary use case?
The AlgoSec solution is really helpful for us, as we need to review all of the rules that have been implemented or we intend to implement, everywhere in our organization, independent of the country or even region.
With AlgoSec, it is possible to check the risks for each rule in terms of security and it is possible to easily decide if the implementation is valid or risky. This allows us to keep only the rules that are following our internal security standards.
AlgoSec helps to keep order and improve efficiency for operations teams supporting the solution.
How has it helped my organization?
In short, this solution makes it possible to increase efficiency by simplifying the life of our engineers. They support the daily interactions with the Firewalls through the implementation of the requested rules. We can easily and quickly identify all of the rules on the firewall and avoid the individual review and analysis of each rule. This keeps the firewalls clean and under our security policy, following our internal standards.
What is most valuable?
I think that perhaps FireFlow could be the most valuable feature, according to the feedback from our technical teams. This allows them to easily add, modify, and remove rules from the firewalls.
Another good point is that we avoid the old procedure of end-users requesting rules, a security team in the middle validating, and then the final implementor doing the job. With this feature, you can directly permit the end-user to request what he or she needs, and if the security policy is respected then it can directly be approved and implemented.
What needs improvement?
What the technical teams report to me is that the network maps are a concern and should be improved. It would be easier if the network maps could be updated using the GUI portal instead of from the OS. This would benefit the operations teams working daily with this tool.
In the end, we are striving to improve efficiency, and taking into account that Operations are really under pressure from SLAs to keep support ticket queues clean, and with the least amount of backfill possible, it is key to get better tools that make it easier and faster to update the network maps.
For how long have I used the solution?
I think we are roughly in the third year since the first time we started using the AlgoSec tool in our company.
What do I think about the stability of the solution?
In terms of stability, this tool is really good and more than you could expect.
We are still involved in debugging a lot of stuff because we have to accommodate the solution to our large IT network. As our company and network are really large, we have a lot of jobs to do. Even with this powerful tool, it is not immediate.
What do I think about the scalability of the solution?
Scalability is really good with this tool as it is flexible, as long as we can move this solution to hybrid or fully cloud deployments. This is something we are really focusing on right now.
How are customer service and technical support?
As I know, until today, all issues raised so far have had a good response time and solution. No bad reports or specific or important complaints were reported from the technical teams.
Overall, technical support is really pleasant and smooth.
Which solution did I use previously and why did I switch?
Before knowing and using the AlgoSec tool, we were managing daily activities with Firewalls the standard way. It was done rule by rule, creating, modifying, removing, analyzing, and finally compiling once all it was decided that everything was under control and following internal security policies.
How was the initial setup?
The initial setup was hard and made more difficult because of the network map configuration. There is no visibility on the provider because they cannot grant access to us. So, the configuration has to be manually done for the most part. This part was really hard and time-consuming.
Which other solutions did I evaluate?
My team was not involved in testing or pilots of any other solution prior to making a decision. Another global team was part of the negotiations, study, and comparison. My team and I were involved once the decision was made.
What other advice do I have?
It is clear that it is difficult to have the perfect tool with all that you need. As we expect, it is not an ideal world. AlgoSec is, in general, doing fine.
Today, this tool is very stable and permits us to improve the efficiency of the day to day work by our technical teams. It also allows the end-user to be more directly involved in the requests, highly reducing the time between the request and the final implementation.
The only advice or remark I can add here is what concerns me with the network maps. This is the cause of what makes the initial setup harder than expected. The reason is because of the network map configuration. There is no visibility on the provider because they cannot grant us access, meaning the configuration has to mostly be performed manually.
Which deployment model are you using for this solution?