The setup was quite easy. 

if I were to take out the fits and starts that were our responsibility, the installation was less than four hours. Then, the upgrade was done because we went from version A30 to A32. That took about an hour and a half. It was very simple and straightforward. Now, when I need to do regular releases, i.e., patches, I can do them myself. It is menu-driven. It's pretty easy.

We ran into some errors/issues, so it probably took us a week to fully deploy it. The process was straightforward except for the typos that we had in the programming. Without those typos, it would have been up within half a day.

We had an implementation strategy that we laid out beforehand and went forward with that.

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. 

Deploying it is easy. We spent some time on it because, in the beginning, we didn't have a lot of guys to work on AlgoSec. But when we designated one guy to do it, it took him about two weeks or three weeks.

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.

The product offers an almost straightforward setup. It is easy to install and integrate.

The initial setup is very straightforward. It is very easy to integrate network devices into AlgoSec and manage them. It's even getting easier with the latest version. We integrated Palo Alto devices into AlgoSec and it is very simple to bring it in. We have a development server that we're testing out the latest version on, and that came in in minutes. It brought it all in automatically.

The earlier versions of AlgoSec, especially when they came out originally, would not integrate properly with Panorama. So at that point, we had to integrate AlgoSec to actually reach out to every firewall individually for configurations and change status. The current releases are now integrating directly into Panorama. It's just basically one connection into Panorama and it pulls in all of the configurations from there. It's much more simplified.

The initial setup is very straightforward, and the online documentation and AlgoSec engineer support are more than adequate.

The initial setup is good.

The setup is not difficult. The professional services were outstanding in installation and knowledge transfer.

The initial setup is straightforward.

It was pretty straightforward. We started implementing AlgoSec in April this year. We are not fully into production, but we have been using it since May. Technically, it took less than a month, but we still have to do some paperwork in terms of security procedures, security monitoring, etc. So, it has been all paperwork from May till today.

The patching process of this solution is also pretty straightforward. They provide monthly patches, and it doesn't take a whole bunch of people to maintain it. Just one or two people can do the job.

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.

The setup is fairly straightforward.

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

It was very easy to setup and easy to get firewalls working with the manager. 

For our implementation strategy, we used their JumpStart process where they actually had an AlgoSec representative come to us and get us through the implementation. That resource was here for about a week. By the end of the week, it was up and running enough for us to complete the more organization specific components of the implementation.

We had three staff involved in the deployment and there's typically a team of about five of us involved in the daily maintenance and operations. We were all part of the JumpStart. 

About a dozen people now use the tool regularly and that number continues to increase.

The setup is easy when you know what to do. The solution has many options to customize and tune.

Our Initial setup was not so straight forward as we were exploring all the features to its depth so lots of engagement was done with OEM level to explore and implement in our environment.

The initial setup is straightforward, and we had no issues during the installation.

I wasn't part of the implementation. 

The initial setup was complex.

Initial deployment was straightforward. The FireFlow workflow can be configured to match the existing flow - customizing this to match any workflow permutations takes the most time. 

The setup is very straightforward; we use VMs, so our customers don't need appliances. We can set up a VM and install AlgoSec in 15-30 minutes, then further configuration such as DNS, names, IP addresses, and adding the firewalls takes two to three hours.

The upgrade process is also straightforward; when the upgrade package is released, we download it, import it to a machine, and implement it with one SSH command. The solution doesn't require any further maintenance. 

The setup was long in the past but recent upgrades were flawless and support engineers knowledgeable 

This initial setup was tough because of the network map configuration. There is no visibility on the provider (ISP) because they cannot grant access to us. So, the configuration was mostly set up manually.

The initial setup is very intuitive and not an issue for those with a good understanding of security, networks and the company's use of them.

If you are knowledgeable about the firewalls that you intend to manage, the initial setup is really easy. The most difficult steps are configuring checkpoints for LEA integration where you need to create the object in each firewall, establish connectivity, install the database, install the policy, etc.

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

Straightforward, it needs to run for a period to ensure accuracy.

Initial setup was very simple. Using Quickstart help, any member can take part in deployment and administration from basic to advanced level. 

Only the firewall integration could take time due to some complex interactions. 

The initial setup was straightforward.

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

The setup is pretty straightforward and AlgoSec did provide support during the process.

I did not find the initial set up very complex. It's advanced, but not complex. Their documentation for implementation is very good.

It really depends on the customer. Some places, when you go for a POC or a deployment, we can always plan and tell them that if they are integrating these kinds of things, these are the levels of provisions that we need. These are the things that they need to do from their end. 

The POC for some customers goes three or four days because of their delays. But with some customers it goes fairly quickly, like a day and a half or two days. For one customer it took five days because they had a procedure where you have to fill a form and send it before creating your user for AlgoSec when it's with the firewall integrations. Because of that, it took a little bit longer. So depending on that I give it three to five maximum days to integrate four or five clusters. It really shouldn't have taken that long to do the work. Then you need to contact different teams to get the support. It all causes delays.

In terms of implementation strategy, I'm always looking at what their components are. I always have to go with the Firewall Analyzer components and to check what type of devices  they are willing to integrate for this particular unit. I check if it is a Check Point cluster, or the Palo cluster, or a Forti cluster, and what the additional features are that they are looking for. Based on that, I complete the Firewall Analyzer unit as soon as I can. Since I have worked with the product, I have similar use cases. What are the things that we can use to demonstrate for firewall change flow? I'm always asking for input from them. What are the things that you need for base level policy changes, etc...?

In terms of actually deploying AlgoSec, most of the time it's me only. But I have to contact the other end. There is always a direct contact person and a support team when it comes for integrating the firewalls. 

When it comes to maintaining AlgoSec, we have another colleague also. They can always give the support.

The initial setup is pretty straightforward. It's not complex. We don't face any challenges on that front.

Setup was not too difficult.

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.

The initial setup is straightforward.

Straightforward initially, and versatile well into production.

Some changes in setup are ongoing as we are growing.

The initial setup is not complex.

The initial setup is straightforward. The complexity sometimes comes from the fact that the company scenario is not so easy.

I have AlgoSec Firewall Analyzer and FireFlow certifications which helped me a lot during initial set up. It was straightforward and easy. 

If the scope of work is just firewall management, it is easy to deploy. However, when you add the flow information, since AlgoSec can also import the flows of your firewall rules, that is live traffic. Then you include FireFlow, or it becomes a nightmare, because what you have to do is take a copy of traffic from different segments/firewalls and bring it into AlgoSec. Doing that becomes a challenge because a lot of companies, such as banks, will not allow you to sniff the firewall traffic live traffic because they have credit card information. 

These days, the traffic has changed to HTTPS, which is all encrypted. Four or five years back, it was HTTP, which was all plain text. Even if you take a mirror of the traffic, how can you decrypt it? You need a decryptor to look inside. FireFlow looks at the packet of the transaction. In order to look at the packet/payload, I have to decrypt it because now it is encrypted. But, who will decrypt it? Then you have to buy another product that does decryption.

The initial setup is very straightforward. You just find the resources on the virtual machine and download.

Completely straightforward except with the configuration of Check Point devices which requires additional steps.

Setting up AlgoSec isn't complicated. You can install it in half an hour, but the configuration time depends on the environment. Sometimes, it takes a day, but it could take up to a week to analyze the files, etc. We have a two-person team responsible for deployment and maintenance, but we also have partners. In all, we have about 10 technicians supporting our customers.

We have been using the OVA file on a virtual box. Once we slam it on the VM, it is quite straightforward. Once you are done with that, then you define the IPs.

The initial setup is straightforward. If you understand your infrastructure, it will be easy to deploy in a central location.

The initial setup was fairly straightforward; however, with the usual initial setup niggles and teething issues.

The initial setup is very straightforward and easy. Further, AlgoSec provides better documentation and self-support services where we can learn, reference, and be empowered.

Find a good integrator.

The initial setup was carried out using professional support and the company was happy with the integrator. We moved our ticketing up to AlgoSec using FireFlow. I wasn't around but I think it took some time.

To deploy AlgoSec properly it is important to understand the client's environment. To that end, we have a questionnaire that we send to our clients and that helps clarify what the client's requirements are. It also provides information on the architecture of their environments. Once we receive the questionnaire, we go over the project specifications with them to make sure they didn’t miss anything, such as integrations with other systems. 

Next, we usually do a PoC to test AlgoSec in their environment and that is when we calibrate the solution to the client’s specs and do the necessary customizations. Then we purchase the licenses and roll out AlgoSec into the client's production environment. We also provide technical support for the client for at least a year to make sure that they become familiar with the solution.

The amount of time it takes to deploy always depends on the complexity of the client’s requirements. For example, for firewall management setup without integration with other systems like a service desk or reporting systems, deployment generally takes up to one month. If we need to integrate AlgoSec with solutions like a service desk, then the deployment can take up to four months because there are major changes to the whole business process and these changes require planning, documentation, implementation, and training of end-users.

There are usually three people involved on our side: a salesperson and two engineers, with the latter actually implementing AlgoSec.

It is somewhat complex to initially setup.

It is pretty easy to set up and run.

It is moderately easy to set up AlgoSec.

The initial setup was straightforward.

We started its implementation in January with the help of a partner company. It was very easy to implement, and we didn't have to contact AlgoSec.

We completed the deployment in February. We put it in our environment and started the server. After that, we did the configuration and started to add our devices to AlgoSec.

The initial setup is simple.

After that, it is possible to make customizations to adapt the tool as desired.

The initial setup is easy and simple.

No.

Setup is easy. Just run the script and all seems fine.

It is pretty straightforward and a piece of cake for the network engineers.

It is straightforward and easy to deploy. Two to three days was enough time to complete the configuration along with the device integrations.

For implementation, I always follow these steps:

1. Understand the customer's infrastructure, e.g., what are the customer expectations and primary pain points?
2. Deployment architecture
3. Hardware requirements and prerequisites
4. Port prerequisites
5. initial configuration and setup
6. Onboard devices with default configuration
7. Monitor devices for seven days, then apply the recommendation based on the AFA solution.

For the migration, it is really helpful because we all capture all their policies. We can clean up things with Firewall Analyzer. When doing a migration, we take a backup and that is really helpful for the migration process.

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

The initial setup is not cumbersome at all. The documentation and training videos are definitively a big plus.

The initial setup was not complex. It was easy.

The initial setup is long. The more knowledge you have of your network, the faster it will be.

The initial set up is a bit complicated, because you have to open special ports in the firewall, and give open access to be able to read the configuration topology mapping in the firewall. This means that the process of scanning and monitoring AlgoSec can run smoothly.
Unlike the case with the initial setup for monitoring IP tables, you must use the root access serve (sudo su) so that the process of scanning and monitoring AFA could run smoothly.

The initial setup has been easy. The only difficult thing was the part in which we needed to onboard non natively supported switches. That part is a bit more complex.

Initially, we found this as a complex deployment. Later, it was easier than anticipated. We referred to the technical documents and AlgoPedia portal to understand more and deployed successfully within the proposed timelines.

It is quite easy to deploy and manage.

It was not so complex and didn't take more than several days until we integrated all of the important networking devices.

The setup is very easy, as it comes as a virtual appliance you deploy in your own virtual environment. The setup is straightforward, and you can very quickly add your firewalls and start tracking changes, query the traffic simulator, and so on.

AlgoSec helps us be ramped up on our technical expertise on the product.

Initial setup is straightforward; some custom options can be tricky to set up, but will not be used by most customers.

Initial setup was straightforward because we got support from vendor.

Setup does take some time to customize to your environment.

The initial setup process is excellent.

It was straightforward on a virtual machine.

The initial setup was simple, and only firewall integration could take time due to some complex interaction.

It was straightforward.

There were some issues when setting up the cluster and getting it to synchronize properly.

Deployment was fairly easy. There were no issues. 

The initial setup was simple.

Initial setup and deployment was straightforward.

There were guides available, and the more you read, the easier it becomes.

It was straightforward.

The initial setup is straightforward for many of our customers. However, when we integrate with some newly supported network devices there is a challenge in getting support from the AlgoSec team.

The initial setup was extremely complex due to our large environment.

The initial setup is straightforward, but also complex because of the onboarding of different vendors.

Be prepared for a long deployment and optimization time, which in the end is typical for these kinds of solutions.

I wasn't involved in the original implementation.

Initial setup is very straightforward and it is easy to implement.

We were not part of the implementation team.

Initial setup is easy because it is a virtual appliance with its own OS.

It was straightforward on an appliance.

Simple to setup.

It was straightforward.