The initial setup is a little difficult compared to other products in the market. It depends on the environment. The deployment of a green-field environment might be completed in a week. If we are doing any migration, it might take months in a brown-field environment.

The setup for Cisco Sourcefire SNORT is straightforward and well-documented. Enabling SNORT on Cisco Sourcefire is straightforward. Once you have configured everything properly, you need to go to the device and click one button. After that, SNORT is activated, and deployment is required. It may not be difficult, but it's easy to set up.

We have a complex environment because of the limited number of ports we have against the cost of acquiring more ports, the initial setup becomes more complicated. On a scale of one to ten, I  rate the setup a three for complexity.

The deployment took around 100 working days.

The initial setup of Cisco Sourcefire SNORT took a couple of hours to complete.

The initial setup of this solution is straightforward.

The deployment took approximately two days, which included applying the IPS rules in the Sourcefire policy.

One person is suitable for deployment and maintenance.

For me, it was straightforward, maybe because I'm used to it. 

The first step is to install Linux because the product is based on Linux OS. Then, I just install the Firewall Management Center. After installing that, I install the full Firepower Firewall. From there, I would make sure that the Firewall Management Center and Firepower can ping each other, that they have connectivity. If that works, then I would add all the IPs of Firepower to the Firepower Management Center. Once that is finished, the whole installation is done, and I can try to call the Firepower Firewall directly to the grid from within Firepower Management Center.

I think the installation is okay. It is easy for me.

Deployment time varies from customer to customer. It depends on what things they want to deploy.

The initial setup was very straightforward. Deployment took roughly two months.

The initial setup was fairly simple. We did it a couple of years ago but I remember it went well. It was, I think, a three-month project and rolled over pretty easily into our expansion.

The initial implementation is pretty straightforward. It's just an appliance. We are using an appliance and it is predominantly for SSL encryption. We have a lot of applications on the cloud and on the web application. 

Your IPS, DLP, everything can be done on a single appliance itself. Predominantly, we are using it for SSL encryption to a larger extent. 

It doesn't take much time for installation. It depends on what you want to and what traffic you want to allow on Sourcefire. 

For example, if I have a proxy path, where my users are accessing through a proxy path, that traffic needs to be encrypted. In cases where I have a direct path, and if I have a CMD path, it depends on where exactly you want to enable your SSL encryption or which data needs to be analyzed and used. If you have too many paths from which the users are accessing the data, then it is important that you use all the paths. If you are using it on a single path and if there are no other kinds of encryption used there, then obviously it doesn't make sense. If your traffic is going from north-south traffic, then you can use its product to ensure that your encryption and other tasks are happening.

We only need maybe one or two people for maintenance. Our data center specialist can handle the device. After implementation, it is just a configuration of our traffic. One or two people are more than enough.

The initial setup was not complex at all. It was very straightforward. We were able to handle it easily.

Deployment, in total, took about a week.

The initial setup is straightforward and the configuration is easy.

We implemented this solution in stages because it could not be done all at once.  It took us perhaps just over a month to finish moving all of our servers from IDS to IPS, from detection to prevention.

The initial setup is quite complex and some set parameters are definitely needed. However, the more you try it, the easier it gets. When we push a specific policy, it takes from two minutes up to five minutes to deploy. So it depends on the deployment configuration. For the general deployment, it depends on the expert. 

The initial setup is straightforward.

The initial setup of this solution is a little bit complex compared to other solutions.

The average deployment takes approximately half a day. It depends on the environment. If we are connecting braches versus only connecting the head office, the length of time to deploy can change.

It is easy to setup. For a basic deployment, it can take up to three or four days to deploy in a minimal setup. If it's a huge project with a huge data center, a lot of configuration, a lot of work, and a lot of integration, it will take two or three weeks up to one month. 

You only need one person for a basic deployment. 

The initial setup and configuration are easy.

You can create panels with deeper functionalities, but you need a bit more experience with the technology.