The solution's initial setup is easy if you have training and know what to do. The solution's deployment time depends a lot on the customer's requirements. It takes around half an hour to install the solution.

We have both private cloud and hybrid. Some of the services are on the cloud and some are on-prem in our data center. Setting up Palo Alto firewalls is quite easy compared to other vendors.

Migrating our old infrastructure to Palo Alto took four to six months. 

We did some pilot project testing with Palo Alto. If, for example, we want to migrate from XYZ vendor to Palo Alto, the very first thing we had to do was capture all the existing security and NAC policies and all the NGFW functionality. Palo Alto has specific features. For example, you can capture the logs in an inline environment, such as what traffic is going to the network, what security policies are there, et cetera. We deployed the Palo Alto firewalls in that way to only capture the traffic. We then analyzed the traffic, and we worked with Palo Alto TAC to understand the security policies and the exact throughput to determine the hardware we were going to use. We monitored all of that for a few months and then we started the migration from other vendors to Palo Alto.

We had 10 engineers involved in the deployment, but each on-site location had its own team as well. Three were senior network architects and the other seven were staff network engineers.

If you want to keep up to date in the network, it requires quite a bit of patching. It has many features, like Unified Threat Management and antivirus that can be auto-updated by scheduling an update for them. But the major patching has to be done manually. In our organization, we do it quarterly.

The initial setup is straightforward but the deployment portion is complex. We require 15 minutes for one VM deployment.

The setup requires professional people to work on it. It's not straightforward. Knowledge is needed to adapt it to your platform. 

So, it's not an entry-level solution; it requires professional and expert-level skills.

The solution’s initial setup is straightforward.

The initial setup is quite complex. There is a steep learning curve and we failed at it a couple of times.

Our final deployment took between three and four hours.

The product's deployment phase is not complex. The tool is easy to deploy.

The solution is deployed on the cloud.

We deploy AWS VPC as a virtual appliance, as a security VPC. The initial deployment was moderately easy. It is not complex, though.

The setup is not complex, but it is not simple. We get everything from Microsoft Marketplace. We buy the license outside Microsoft Marketplace because it is more cost-effective. All our VMs are deployed on the cloud.

The initial setup is easy. We managed and configured it with the help of existing management tools and courses. We deployed it on the cloud and on-premises.

The deployment time depends on specific business requirements and bandwidth. It takes around one to two weeks to migrate and configure for large organizations. For small organizations, it takes one or two days to complete.

I rate the initial setup process an eight out of ten. It takes eight hours to complete and requires one security engineer to execute the process. The deployment involves setting up security policies. The on-premise installation is simple. However, VM installation is complicated in terms of the network interface.

The initial setup was complex, but we were able to work through it.

The solution’s initial setup is very easy.

I rate the initial setup process a nine. It takes a few hours to complete.

We had some complexity because we had no experience in implementing it in the cloud, but with the support of the partner and the endorsement of the brand it was solved quickly. It took us a couple of weeks to implement it, and then we started testing. (traffic stress, fault escenarios, scale up, vulnerability assessment, etc.)

Deploying a firewall is not easy until we have a basic knowledge of routing and security. If we have the knowledge, we can find the proper document on the website and do it easily. We should know the basic configuration. The deployment process is user-friendly. We can configure it easily.

The tool's deployment is simple. 

Setting up VM-Series is completely straightforward. You have to download the VM, and there is a free interface for internal and external management. You configure the interface and the root table within Azure, then the device is good to go. Lastly, you need to activate your license, and Palo Alto is integrated into Azure.

We had to purchase the license from the vendor and download the VMs from the Cloud market. You can download VM-Series from the Azure marketplace, it is a simple process. You configure everything in the management interface. Once that's done, you configure the access list so that others cannot access it from anywhere. 

After you purchase the license, you have to put the license in Azure VM. There's a similar license you have to implement in the Palo Alto portal. Your Palo Alto is ready to use once that goes through. It took us one week to deploy. An issue came up, and we had to raise a ticket, so it took seven days to complete the implementation within Azure Cloud. One person is enough to deploy it. I deployed two firewalls within seven days, so I didn't need anyone's help. One or two people are enough to manage it.

It is easy to maintain because we have various tools to manage and monitor the system. 

We did a fresh setup for this, but it was pretty easy. We could easily integrate with the VM-Series, then just create our business servers. We were able to do this with the help of the tech team.

It took around seven to eight hours to deploy this solution and configure it to our environment.

Palo Alto's installation process is easy because we use Panorama tool to manage it. We can communicate and implement traffic policies, filtering, and other specific options with its help.

It requires two to three engineers and takes two days to complete the deployment. For maintenance, it requires a team of two engineers.

With any organization, if you want to change the firewalls that are being used in production then it's a hectic task. You have some rules and engines that can be used, but it's a step-by-step process.

Migrating from an existing solution to Palo Alto needs to be done in phases. Phase one would be installing the devices. Phase two is testing a lab setup and diverting traffic, then analyzing it. Finally, the third phase is to enable other features like threat protection, malware detection, and other advanced options.

Depending on the size of the organization, if a migration is well planned then it will take three to four months to complete.

The configuration is different between our branch offices in order to meet our requirements. Some use the hardware appliance, whereas others use the software version.

I rate the implementation process a six or seven on a scale of one to ten, where one is difficult and ten is easy.

During the implementation process of the product, I faced some issues related to the networking part and connectivity of VMs. I faced issues with how an end user could connect the VMs to a firewall or connect a firewall to VMs, but the same process was easy for me on a physical device firewall.

It is easy to install. You buy it on the AWS Marketplace, then you just install it. You have already purchased the license and everything else. It is easy to configure and use.

The initial setup is very straightforward and we had no issues with it. It is not complex because the procedures are properly defined, the documentation is available, and there is proper support. Our initial setup took about 15 days, which included migrating all of the data.

Our deployment is ongoing, as we are adding policies and dealing with updates on a day to day basis. We have a very complex environment that includes a firewall for the data center, as well as for the distribution networks.

Setting up Palo Alto is relatively quick. But I also have an absolute rockstar on our team for when it comes to Palo Alto installations. When he is setting it up, he knows what he is doing. The only thing he had to really learn was the difference between the VM-Series and the PA-Series.  

I lay out the architecture and I tell people doing the installations exactly what has to be there. I sit down and create the rule sets. Early on, the person actually doing the fingers-on-the-keyboard complained a little saying that the setup was a little bit more complicated than it should have been. I agree, generally speaking. I generally feel that Palo Alto is more complicated than it needs to be and they could make an effort to make the installations easier.  

But, installing Palo Alto is not as bad as installing Cisco. Cisco is either a language that you speak or a language that you do not. I mean, I can sit down and plot the firewall and get the firewall together about 45 minutes with a good set of rules and everything. But that is me and it is because I have experience doing it. Somebody who is not very well-versed in Cisco will take two or three days to do the same thing. It is just absolutely horrid. It is like speaking English. It is a horrid language.  

Integration on on our AWS environment was one of the points that we liked about it.

You will need to know what are you doing with the firewall. 

It's different than Sophos or Fortinet where you only need to click two or three times, and it puts you in engaged mode in the simplest way. 

With Palo Alto, you need to know where you are going to be implementing and what architectures you want. It is not complicated, but it is not as easy as Sophos or Fortinet, because when you start with these two firewalls, the quick setup wizard chooses for you and it automatically creates for you network rules.

With Palo Alto, you need to do all those steps manually, but it is somewhat better because it gives you the flexibility to choose how you want your network set up and how you are going to segment the networks.

The integration and configuration on our AWS environment was pretty simple. We did not have to ask any questions about anything on it, so it was good.

Users are provided with templates to go ahead with the deployment phase of Azure. There are already prepared templates available for installation, which users can use during installation.

Suppose our company's discussions with the customers are completed, and the design has been frozen. Considering the aforementioned case, the Palo Alto Networks VM-Series installation phase can be completed in a couple of hours, while the only time-consuming task is the creation of policies.

We have been happy with the configuration and implementation on the AWS environment.

The initial setup is straightforward and easy. 

The deployment will take a couple of hours at the max and will depend on the configuration that you are looking for. Palo Alto will give you a report that recommends policies that are based on industry standards. For example, if you have approved Telnet access then you will be warned because it is not recommended and you should be using SSH instead. They will give you lots of recommendations to warn that the configuration does not follow the standard practice and if allowed to remain then it will explain what vulnerabilities you might face in the future. This kind of report is really valuable.

I would say that the initial setup is easy. I have been an IT professional for more than 20 years and can say that this is an example of a product where you simply have to read the manual. If you jump straight into it then you will start struggling.

During the initial setup you begin with the CLI, but you enter a command and it brings you to the GUI. Once you are in the GUI, you will see words on the tabs. All of these things are there if you look carefully.

This firewall is easy to implement. 

The initial setup was straightforward. 

The deployment takes two days. This includes installing the solution on the OVO files, upgrading the firewall panel records, activating the license and configuring basic policies and rules. However, our setup was basic and did not involve business activity, which would necessitate a technical business setup. In such case, the process from start to finish may take a customer up to 10 or 15 days. 

The initial setup is straightforward. It doesn't take too long to deploy, although every company their own set of requirements. For example, the level of compliance varies between companies.

Palo Alto Networks VM-Series is a VMware appliance and very simple to install. It must be turned on to change the default password and to configure the IP address, and that is all. After that, it's easy because it has a very intuitive web interface.

Palo Alto Networks VM-Series' deployment is not difficult. 

I have found the initial setup to be okay. But, then again, I have been using Palo Alto firewalls since 2014, so it's hard for me to say if it is difficult to become familiar with or not.

I found the initial setup okay. I have been using firewalls since 2014, so it is hard for me to say whether it is easy to install or not.

It was easy to deploy.

The deployment works well.

It was complex. We used a lot of professional service hours. 

It is very simple. They have a very unique approach to simplicity. You have to do some basic set up to some parts where it will be needed. Therefore, it is simple compared to Cisco or Check Point. Also, it is very flexible.

The hardware install was mildly complex; it was somewhere in the middle. It was just about working out the best way to monitor our traffic, because you can have a segregation of interfaces. You can use something called vwire, which is like a bump in the wire, or you can use Layer 3 interfaces. It was just working out which way to go with. We could not really configure the Layer 3 interface solution properly, so we just went for a different setup. 

It was not overly complex. There was enough information online and enough support. There is enough info in the community on their website to allow you to do what you need to do.

The initial setup is not complex. It's quite straightforward. The deployment process is great. It only takes about five to ten minutes or so.

I handle the maintenance and troubleshoot any issues that arise. 

The implementation involves setting up policies.