The setup is pretty normal but might be slightly more complicated than Fortinet. If you are familiar with the interface or have a technical background, then you won't have issues with the setup. New engineers might find the setup a bit complicated until they get used to it. 

I rate NGIPS nine out of 10 for ease of setup. The process was smooth and straightforward. After deployment, it requires some maintenance like updates and creating or changing the policies. We have more than a hundred policy categories now. 

The initial setup was extremely complex for a firewall that did nothing but accept traffic and filter it. It provides IPS, IDS, and it provides URL filtering, which isn't as good. The categorization leaves a bit to be desired. That leaves you to do extensive whitelist blacklisting.

The product's setup was smooth and easy. The implementation was not a big deal and took two weeks to complete.

The initial setup is pretty straightforward, and it's like a plug-and-play. The graphical user interface is understandable, and their documentations are clear. In addition, they have an SOP document that can be used as a guide.

The initial setup was straightforward and easy to deploy. It was very quick.

The ease of installation depends on the engineer. If they aren't trained in Cisco NGIPS or they aren't skilled enough, it's not easy to implement. You have to implement with a highly skilled engineer because it's not simple to deploy Cisco products.

We had one project where we implemented Cisco NGIPS along with a few other products and it took perhaps a week to fully deploy. 

The implementation of Cisco NGIPS is straightforward.

The initial setup is not complex; we only need to define the IP address and add the SMC IP. Both STD and SMC have the capability of SDM. Also if we don't have SMC, we mainly require the anti-SDM in UI. However, after we enroll the Cisco file from the SMC, we can no longer manage the STD from there. Therefore, it is very difficult to roll back if there is a connection loss between the STD and SMC, as SMC cannot manage the STD via the UI. In comparison, if there is a connection loss between Palo Alto Panorama, we can simply lock it with Palo Alto following the file and do some configuration. 

The tool's deployment is not straightforward. You need a technical and competent person to do it. A four to five-member technical team can handle its deployment and maintenance. 

The initial setup is straightforward. With the Firepower Threat Defense (FTD), everything is in one box. You can do everything from firewalls to IPS and more. It also includes the next-generation firewall.

It is an easy upgrade process that is easy to understand. I would say that from version 3.0, it has improved.

The installation is complex.

The initial setup was complex and the upgrade took a lot of time with a very big image to download and everything else. We had many versions and patches that had to be installed. The deployment took between two and three hours.

The initial setup is a bit complex because it requires a lot of configuration, firewall and zoning. The deployment was done in-house. We just purchased a box and installed it on our own.

We initially had some difficulties, but now we have no problems.

It requires some background in IPS and IT security to fully understand it, so it is somewhat complex to deploy.

The initial setup is easy because I am very familiar with the product.

The initial setup of Cisco NGIPS is of a medium difficulty level.

The product's initial setup phase was easy.

I rate the product's initial setup phase a nine on a scale of one to ten, where one means a difficult process, and ten means that it is an easy process.

The solution is deployed on an on-premises model.

The solution can be deployed in a couple of weeks. We take care of the testing phase in our company before installing the solution only when the signatures are updated in our environment, which takes around a time frame of less than two weeks.

Around three or four engineers take care of the product's installation phase.

While I didn't set it up, my understanding is the implementation is straightforward. You read the documentation. It's this continuation from the old Cisco ASAs. People have used it for many years. Cisco's quite easy to set it up and keep up and running. You just need to add things on top of it, however, it's all quite easy. I have done an installation of the previous Cisco firewall. It's really straightforward. The upgrade is quite simple as well.

We have three technical personnel that can handle deployment and maintenance. We have to cover the whole globe, so we have three people on to handle everything 24/7.

It was quite complex. It required some workarounds with other network components in our system. It could have been a lot less complicated. Nexus Switches that we had were a little bit older, and they didn't integrate as well with Firepower as they could have. So, we ended up having to buy some new switches. 

The deployment pretty much took about three weeks. It involved moving all of our stuff from our old firewall onto the new one. Rules were a little different, so we had to work on it for a while. Fortunately, we could run them in parallel, so it worked out okay.

The solution's initial setup process is complicated. But we can manage it with the right team for installation and technical support from Cisco.

I think the installation of Firepower NGIPS is really easy. You configure the device, you connect that to the Firepower Management Center, and you have deployed the Firepower.

Three years ago the setup was very complex. We had two different cables or software. It's like two appliances and one appliance. We had to set up ASA first and then set up Firepower and do the redirect from the old HTTP traffic, from the ASA for a detailed inspection by Firepower. Initially, it was complex. That was a few years back, but now with the newer version, it's just a piece of cake. Deployment took about 40 minutes. I also handle the maintenance myself.

This product is straightforward to install. A CCMP can complete the deployment in one day.

The initial setup is straightforward, it took a few hours. As the consultant, I deployed the solution. 

The initial setup of this solution is not complex. They have a graphical user interface for managing all of these things, which helps make it easy to deploy.

The initial setup of Cisco NGIPS was straightforward.

It is very straightforward, clear, and easy.

The initial setup and configuration of this solution was straightforward.

Setting up NGIPS was complex. We needed help from a Cisco specialist. 

Installation is straightforward and took half a day.

The initial setup is very simple and in one or two hours, it can be up and running.

The initial setup for this solution is complex.

The deployment took four months.

The initial setup was a bit complex. One had to read so many areas to understand the navigation feature. It took about three years to reach maturity. For deployment, we required about eight people, but for maintenance, we only require four to six.

The initial setup is complex and requires someone with a background in firewalls to set it up. Inexperienced users will find it very difficult to set up. For experienced users, deployment will take around forty-five minutes. I would rate the setup process five out of ten.

The initial setup is straightforward.

The initial setup of this solution is straightforward if it is only the standard package being installed. However, configuring this product is complex and requires a lot of time commitment.

Deployment of the solution usually only takes a few hours, but if it is being implemented in a more complicated environment it can take up to three days.

We have a somewhat complicated environment over here. We have also implemented SSG Juniper, SSG140, so basically their firewall is working as a router.

The initial setup is straightforward and the deployment took about three weeks.

The initial setup is a little bit difficult. It's pretty straightforward, although if we look at it relative to other products on the market, we feel that the other products are easier to set up compared to this one.

We attended the Cisco training, as we always do. When we buy equipment from Cisco, they also give us learning credits. With those learning credits, it makes it easy to attend training. In terms of the knowledge they share surrounding the equipment, it's very good. We don't have a doubt about what to do.

The initial setup of NGIPS was fine. Firepower took the most time. We took about three months to deploy the solution. 

You only need two people for deployment and maintenance. 

The setup is easy, you do not need hardware. You can just sign up for AWS or Azure and you can deploy it there.

The initial setup is complex. It requires that NGIPS be optimized such that it has the best results with the best performance. The deployment model, be it on-premises or cloud-based, depends on the client.

The length of time required for deployment also depends on the client. In a small office, I can do it in a few hours. For an enterprise, it could take half a year. I have worked on many different scales.

The installation is straightforward. You have to install the device, but if you want to actually manage it, you need a GUI for it. For deployment, you will need two engineers, maximum. 

The solution has a moderate amount of difficulty. You need to go over and use the documentation.

Cisco has a device manager now but this device manager is not like all device managers from ASA. It lacks a lot of features, and some of these features are very important. It makes it a challenge to configure because of the graphical interface. You have to install the management center and that itself takes time and it's not so simple.

The initial setup is not complex. There is a wizard so it's not complex. There is a difference in the complexity of the deployment. Depending on customers and infrastructure, sometimes it takes one day or two days if we're talking about a little infrastructure. Sometimes it can take eight days or more to couple the firewall with ASA, and to do some more complex architecture. If we have a complex architecture, we need 2 people to implement, but if we have an implementation that is not so complex, one person can do it.

The initial setup wasn't complex or complicated. Everything was clear. The initial configuration took a day, but the company that we support has a very complicated topology. During the deployment, they had a different idea about how the configuration should be. Because the customer didn't know what they wanted, the files and the deployment took approximately three or four months. 

For deployment, it depends on the company. It depends on the company's complicated topology. If it's too complicated, then maybe you need two engineers to support Firepower. For employees, you need only one, with a second as a standby in case something goes wrong with the primary engineer, so I'd say you need two engineers to maintain the solution.

Signature tuning is automated in Cisco Firepower. This is the most powerful feature, which most vendors don't have. It makes deploying the solution straightforward for the customer and us implementers as well. So the automation and the fine-tuning are effortless in Firepower.

I was not involved in the installation.

We have a team of four of five, including four engineers, and one supervisor to maintain this solution.

The initial setup is complex. That's just the nature of that product. It's a really advanced product so it takes a lot of technical knowledge to implement it.

It's very straightforward and very easy to set yo the solution. It's not overly complex. 

It took us one to two days at a maximum to install everything and to get everything going. 

We have two technicians and three engineers that can handle any deployment or maintenance tasks.

The initial setup of this solution is straightforward.

The initial setup is fine.