The solution has a one-time setup that is easy. The granularity during cloud setup is very good. 

Custom signatures might require a bit of engineering work but are doable. 

Firewalls automatically get the feed from clouds and dump it to the firewall at intervals ranging from five minutes to 24 hours.

The initial setup is straightforward. I have experience working with similar technologies, such as Palo Alto, Firepower, and Panorama

The usage of the technology is extremely high at 99.95%. The firepower management center also shares 99% similarity with Palo Alto and Panorama.

The initial setup of Palo Alto Networks Threat Prevention is not as straightforward as its competitors, such as Fortinet and Cisco. It takes more time and skills to implement Palo Alto Networks Threat Prevention.

The time it takes varies on the company and the environment. For example, for a bank or other large institution, the time will increase.

The initial setup was very complex as the solution does not have these APIs to facilitate the configuration. Therefore, we had to manage some scripts to perform the configuration.

Our deployment took, approximately, eight months.

The initial setup is complex compared to FortiGate. Deploying the product on a VM is more complicated than other vendors. It takes three to four days to complete the process and requires eight network security engineers to execute it.

We have installed it in a lab test environment. After this stage, we will propose the solution to our customers. We provide local support and preventive maintenance, including BPA and firmware updates.

The initial setup is very complex.

The time taken for deployment depends on the complexity of the process.

The initial setup is straightforward.

One of the reasons that our clients choose Palo Alto is because they have complex networks, therefore the setup is typically also complex.

The initial setup was pretty straightforward. 

The initial setup was simple, but it's been ten years since then and we have grown. The migration has also been simple and straightforward.

You can have a network with thousands of machines with only a few security rules to migrate, or you can have a network with only a few machines and thousands of security rules that make it difficult to migrate.

One of the reasons we chose the Palo Alto firewall is because it's probably one of the simplest firewalls to set up, it's very intuitive. We've done probably around 50 deployments and depending on the size and scope it takes around five hours but sometimes an implementation could take five months. It's very difficult to say how long it takes, but if you compare it with other firewalls, the implementation cycles of Palo Alto beat them hands down.

We just replaced a firewall, so we didn't find the setup to be complex. We have network rules to convert. For the rules and connections, we use tools from Palo Alto to convert them.

We implement the firewall setup for our customers. It generally takes a little bit of time, i.e. one or two weeks to customize the policy that they use. 

The old rules we can remove with Palo Alto Threat Prevention, which is nice.

The deployment is easy.

The initial setup was straightforward. It's quite easy. Deployment took one to two weeks.

The deployment was straightforward. It wasn't difficult for us. 

We used an expert to help us with the initial setup and installation.

The setup is neither complex nor easy. We worked with the vendor and they have more experience than us. For the PoC they did the configuration for us and we were able to learn from them.

Our deployment took about two months.

It is not very complex, actually. Firewalls can handle it. 

The setup of Palo Alto Threat Prevention is very easy and straightforward. From initial configuration to deployment, it took maybe one day.

The initial setup was not so complex but not so simple. It depends on the requirements of the deployment. Sometimes it should be simple but sometimes you need more knowledge to connect the device.

The deployment can take around one month. Sometimes the project manager wants to extend the session with the customer and maybe upgrade the migration. Then he asks the customer if there are any problems or is there are any additional issues that come up after the migration. In terms of the configuration, it takes less than five days but in terms of the project, we saw more cases that took around a month.

We only need a project manager and engineer for the deployment. Some deployments require additional engineers. From our customer's side, we usually discuss the deployment with the security team.