Palo Alto Networks PA-Series Reviews

There are various use cases, particularly for desktop scenarios. One of them involves exploring contacts. Virtual firewall use cases revolve around different scenarios, such as transitioning to the cloud. For instance, when Barclays uses Azure or AWS, there's a focus on meeting security obligations and implementing threat prevention to comply with regulations like GDPR or PPA. This includes creating segmentation to align with regulatory standards. As part of this process, security features available in cloud platforms like virtual firewalls and threat prevention are incorporated.

After the implementation here, especially since I work in the data center, I've noticed the significance of security. For example, Veeam, CDL, and other aspects became crucial, especially during the COVID period when users started working from home. 

This situation led to numerous blocks, and user profiles were getting blocked due to issues with IP addresses ending up on blocklists. However, after implementing the 3M series virtual firewall, we were able to effectively manage security for our cloud applications, like those in AWS. This enabled us to monitor remote workers and take necessary actions, such as blocking problematic IP addresses. Consequently, we reduced the number of tickets raised with ISP providers.      

A valuable feature that we can consider is the deployment time, which is significantly reduced, almost 90% faster compared to other solutions. This leads to quicker deployment and less downtime.

I have found that the tool works well for me, but there are areas where security testing and protection could be improved, especially in virtual or cloud environments. However, in this project, once we deployed it, we haven't encountered any issues.

The cost is currently manageable, but as we migrate fully into the cloud, additional features like capacity upgrading and improvements to hardware resources will be necessary, especially since our equipment consists of older-generation switches and routers. I'm looking for additional capabilities in these areas.

I've been working on my current project for more than two years now.

I would rate it 9 out of 10. 

I would rate it 8.5 out of 10. 

The deployment is quite straightforward, and it's faster than it used to be. This means that the deployment process is quicker, and there is less downtime involved.

From my perspective, managing the price is important, especially because we're a small business. For larger organizations like Barclays, we provide our requirements to the client, and they place the order on BigFix. It's their responsibility to consider their budget and make decisions accordingly. We appreciate the features we get, but the cost-sharing still depends on the client.

The client needs to provide approval for the POCs used by our team; it's not within my control.

When evaluating options, we should consider team members who are knowledgeable in supporting next-generation firewalls like NGFW. We also need to factor in the specific product offerings. For instance, if we have options like the PA-440, PA-850, and PA-8350, we should compare their prices and features. It's important to make decisions based on the situation and the needs of the organization.

Considering factors like availability and the specific situation, I would rate this an eight. It's important to explore other potential cases as well.

On-premises

Firewall implementation and firewall rule edition are the primary use cases.

It's very secure. It inspects the application. Compared to script-based or CLI-based firewalls, it's easier to use the GUI (graphical user interface) to implement the firewall. 

It has its own logging system. You can go to monitoring and check the logs to see if a connection is getting blocked. You can use multiple types of logs to check if a file or a port is getting blocked or if there are any TCP resets from the source or destination. It's easy to troubleshoot with the monitoring and logging it provides.

There seem to be some issues with TAC (Technical Assistance Center) or Palo Alto support. Anytime you open a case, a level one engineer joins, and then you have to escalate it to level two or three. The support system has changed in the past few years, and that's something they need to look into.

In future releases, I would add one feature where we can take a subnet or take an IP and create a list of rules that are for that IP. There is an option, but it's not as expansive as I would like. When you run a report, you have to run it for a hostname. And when you look at the report, you see the hostnames, but you don't see the IPs. Like, there is no additional column for seeing the IP of the hostname or the subnet of the hostname. So that creates an issue. You have to go into the file and take the export list of firewall rules, and then you have the hostname got have the IP, then you have to note down the IP addresses.

I have been working with this solution for more than eight years. 

It is a very stable product.

The solution scales easily. For example, when we did a migration, we brought in more than 14,000 firewall rules from Juniper into our Palo Alto. After importing, obviously, that's a huge number. But, after doing that, the CPU went really up because we have so many rules. And after having to talk with Palo Alto, they told us to get a better model. We have the 5500 model. So, we were asked to replace the Palo Alto with a bigger or better model. That's what we're gonna be doing.

We can absolutely update the firewalls with a better GPU and CPU. With a better CPU, it can handle more connections. Especially when the environment grows, adding new data centers and more applications. So, after a year or two, there is a need to either bring in more firewalls or upgrade the existing ones you have.

Currently, there are around 12 end users using this solution in our organization.

There are certain issues when we open a ticket with TAC (Technical Assistance Center), the issue goes to engineering, and then they inform us that the fix for the issue we're having will be included in the next software update. 

So, there are some issues in the backend or with new features that don't work correctly. We usually open tickets for that, and then usually, they assure us that this issue will be fixed in the next update.

Neutral

Juniper environment we had was reaching the end of life. That's why, rather than bringing in new Juniper devices, the enterprise architecture team decided to go with Palo Alto.

The initial setup was easy. I was migrating from the Juniper SLX firewall to Palo Alto, so I had to move a lot of firewall groups and create a script on the engine tool to facilitate the move. There were some hurdles. But, personally, it was pretty smooth. The transition was pretty smooth.

So we have physical on-premises, and also instances on the cloud, AWS Cloud.

I would recommend using this product , but it's important to have whiteboard sessions with the network and another team to give them information on exactly how to check the BGP settings. You need to go over with the team the things they need to do on the GUI and on the CLI. So, you definitely need to educate the team before using it.

Overall, I would rate the solution an eight out of ten. It's very stable. There are some tools for pushing the rules to Panorama, pushing the rules to the device, especially if you're working with a team, if you're working on a rule and someone pushes to Panorama, or if they want to push your firewall rules. Someone could push you if you have set up something for a change and you need to the changes at a certain time, if another member comes in and puts a change, you definitely need to have your changes or your pushes to the device or to Panorama, you need to have good communication between the team. So there are some good and bad things with Panorama. As you work on it, you adjust.

In my role as a tech, I provided support for various firewalls, including the PA, PM, and virtual series. It wasn't limited to a specific product like the PA-800 series, PA-1000 series, PA-9000 series, PA-7000 series, or PA-5000 series. We received training for all firewall types.

Palo Alto gives proper training for the product, not cutting corners over that. They don't assume you have previous knowledge and experience and start working directly, which happens in most companies. 

So, they provide product training very thoroughly. This helps the support system to have the necessary knowledge, not just before starting to work or troubleshoot. 

In the 11 months, we were initially trained on various OS versions and given tools like vSphere because we didn't have access to the Palo Alto environment. 

Later, when we got access, we were given a tool to design our own networks, study them, and, if needed, raise concerns about issues. 

The engineers or senior engineers would then study and guide us. They trained us for new upgraded versions of the OS regularly. Even as a third party, we had complete access to the Palo Alto Networks domain, tools, database, knowledge base, and everything. 

This gave us the opportunity to build our skills and understand what Palo Alto requires us to do. We could troubleshoot it properly with customers. 

There are constant updates for the operating system. It is a nice thing also, but it has its own disadvantages. Continuous updates are there. The users face issues like, how often do I need to update that? 

Within a period of five months, I'm updating it two or three times. It gives them a feeling that they are not confident about their product and have to update it so frequently. 

Plus, there are certain bugs, like in the 10.1 version, it's had some bugs. Then, they are upgrading it to the 10.2 version. They are updating that for the bugs. But the time duration between the two is less than the others. 

If we go for Cisco, they don't have their OS upgrades frequently as parallel to us. So that's the disadvantage.  

I was working on a project outsourced from Palo Alto to a company. I was employed in that company for 11 months. During that time, I received guidance and training directly from Palo Alto Networks. I served as a tech engineer for the entire duration. It was quite recent, about three or four months ago.

It is stable. It's just the thing about the frequent updates. So that's the only issue there. So if they somehow reduce that frequency, all these will be easy.

It is scalable. But that depends on what model you are using.

However, other PA-Series models, such as the device on the APAC, are highly scalable and support other vendors.

Moreover, within the network, the device is scalable. 

The customer service and support are really good. And they continuously ask the support team to go through some training updates. So, continuously, we have these updates on the KPIs on a knowledge basis. And the last time, we had this training on the latest version upgradation. So they continuously give the training.  

I was physically present during the setup processes because many times, customers come saying, "I have purchased this new product, but I don't know how to install it." 

There were two teams: the sales team was there, and they had their own engineers. They used to provide the customers. 

But at times, we also had to get involved in case there were any technical glitches or issues because the sales engineers did not do troubleshooting. 

So for that, some of our engineers got involved. At that time, we used to give the setup, whether it was a VM, a cloud, or a physical device. 

At times, customers lack the knowledge of installing and deploying it into the system. So, we used the knowledge base to supply them with articles on the basic level. But even if the customer couldn't understand that, then we used to set it up ourselves directly.

The setup and everything was pretty much given in the KB articles in the knowledge base. So that was pretty much good. And if the customer is not able to understand, then I used to do that.

I supported both the cloud version, which is a VM version and the physical device.

For the cloud deployment of this product, you don't need to buy physical hardware, a modular device from Palo Alto, which is cost-effective and cost-efficient. It can be deployed in AWS or Azure, any cloud provider.

However, the disadvantage or the downside, I can say, is that it is on another network and it is software-based. It is not 100% under your control because it is mostly connected to the AWS or Azure environments. Some controls are not 100% with the user.

If I deploy a VM on the Azure network, then I have to define something compatible with the Azure network. That is the con for cloud deployment. But if the user needs cost-effective solutions, they can go for the cloud.

With the physical device or hardware, it is under your control. You can manage it properly and get excellent tech support directly from Palo Alto, unlike the cloud, where support has to be from both ends.

Sometimes, this creates confusion or complexity, but not always, but it may create complex support. In the case of the physical device, it does not because it is provided by one single vendor.

The disadvantage is that Palo Alto devices are costlier than other devices in the market, like Fortinet or CheckPoint. However, Palo Alto has an advantage in continuously striving to provide better support and upgrading their software or operating system.

On average, the time taken to deploy the solution actually depends on what the environment is and what other vendors are connected to it. So, if it is a Cisco router, where is it connected with what else is in the environment? It actually depends on that. 

And it also depends on how much the customer has, like network knowledge. So, if they need to have some policies to block or allow, IP addresses, and more, if they have all that handy, then it is like two hours or something, not more than that. So it's pretty well done. It is a faster thing. But if the customer is not that handy, then it makes it difficult for us.

Maitaince is not required unless there is some issue, like a manufacturing defect once or twice. It wasn't, of course, too many times. 

But sometimes, it occurs because the device gets old or there is a manufacturing defect. It was a hardware replacement directly. So,  it was pretty much good. That process was a piece of cake. 

Palo Alto Networks has a program that allows customers to transfer their device licenses to another company. This means that if you have purchased a Palo Alto Networks firewall and you no longer need it, you can sell it to another company, and they will be able to transfer the license to their name. But for that, I need to go to Palo Alto and first discuss it with them. So they have this other team. So they check and verify everything.

This is something that I have never encountered with any other vendor.

The pricing is a bit on the higher side but it is reasonable because they give that kind of level of support and everything else.

Overall, I would rate the solution an eight out of ten. The one con is that it's a little more expensive than others. But the pros here are that it has good support.

Overall, it is a good product, and you can definitely have it with other vendors. So it doesn't have any issue. If you only have Palo Alto, you cannot have others in the environment. You can definitely have others connected there. There is no issue. 

And the technical support team is also there to guide you. It's a very good team. So you can always go ahead and purchase Palo Alto. It's a little bit pricier than others. But it is worth it because you'll get other support and everything is very good.

We use Palo Alto Networks firewalls for our perimeter security defense.

We use it for threat prevention in our networks. Check permission, advanced URL filtering, and DNS security. There are different subscriptions, and we are actually using them all. 

We are really satisfied with the firewall's throughput and its threat prevention performance regarding network traffic. We can easily decrypt our SSL traffic and thanks to the technology named App-ID, it recognizes network protocols without relying on port numbers.

It operates at Layer 7, and its ability to recognize protocols even if they use a default port for another protocol is impressive. It alerts you to such anomalies. 

The single-pass architecture technology is particularly noteworthy because it allows for the addition of new functions to existing hardware without any performance degradation, even when all modules, like self-encrypted encryption, malware protection, threat protection, and industrial filtering, are enabled. This results in outstanding performance.

That's why we use Palo Alto Networks in our IT firm and recommend their devices to all our customers.

We also have functions related to network visibility and control. We use Panorama controllers, which operate in a geographically distributed architecture, allowing us to easily control, configure, and manage network devices. 

With single-touch provisioning, you can effortlessly add new files to your Panorama VM. It offers extensive features that we currently use.

Panorama is a Palo Alto Networks product optimized for firewalls. As for integration, we can easily integrate the PA-Series with popular brands, switches, and routers like Cisco, Extreme Networks, or HP Aruba across your local area network's switches and routers, enhancing application-based policy enforcement.

It offers  application-based policy enforcement. Palo Alto Networks firewalls help us recognize protocol anomalies, contrasting with other vendors that may require policies based on port numbers. 

With Palo Alto Networks, the port number isn't a constraint because their devices handle protocol traffic at Layer 7, allowing for accurate identification of protocol usage and port numbers.  They can identify which protocol actually uses which port. So, if there's an unplanned issue, like, for example, a hacker trying to create a DNS tunnel using a non-standard port (like 1536 instead of the usual 53), Palo Alto's Endpoint UI will easily detect it and allow you to take measures.

PA-Series includes built-in network packet brokers, a valuable feature as it allows SSL traffic to be decrypted just once. If you need to inspect this decrypted traffic further, there's no need for a third-party solution—Palo Alto Networks firewalls handle it themselves. 

In future releases, maybe Palo Alto can enhance and enlarge their portfolio with SIEM solutions. They already have an endpoint protection solution, SOAR solution, that's fine. 

But when it comes to standalone IDS/IPS solution or email security solution, for example, we don't have any product in that category for Palo Alto.

I have been using it for two years. 

It's very reliable. Even if you have only one firewall, failures are rare. Moreover, the high availability feature allows two firewalls to sync with each other for continuous operation, ensuring stability.

The customer service and support are good. Both local and global support teams are readily accessible and they report back in a short period. I've never encountered any issues with their support.

Positive

The setup's ease depends on your experience and the resources at hand, like Palo Alto Networks' documentation. With the right information, it's not a problem.

For me, the deployment took around 30 minutes. 

Many people think Palo Alto firewalls are expensive, but I don't feel that way. Let's compare it with Fortinet firewalls.

With Fortinet, every two or three years, the firewall generation changes, and they have limited support for older devices. But with Palo Alto, you still get support from the vendor for seven or eight years.

Also, many vendors prepare data sheets for their firewalls with most features disabled. For example, they might say their firewall has 20 gigabit throughput, but they don't mention if threat prevention or service encryption is on or off. With Palo Alto, even when you enable all the modules, it still provides the exact throughput they advertise.

If you're buying two firewalls, one from Fortinet and one from Palo Alto, both rated at 20 gigabit throughput, and you enable all the modules on the Fortinet one, it might downgrade to 10 or even 5 gigabit throughput. But with Palo Alto and all security modules enabled, you still get the full 20 gigabit throughput.

That's the key difference. That's why customers trust Palo Alto, and that's why it's a big player in network security.

Overall, I would rate the solution a ten out of ten. 

On-premises

There are various use cases, particularly for desktop scenarios. One of them involves exploring contacts. Virtual firewall use cases revolve around different scenarios, such as transitioning to the cloud. For instance, when Barclays uses Azure or AWS, there's a focus on meeting security obligations and implementing threat prevention to comply with regulations like GDPR or PPA. This includes creating segmentation to align with regulatory standards. As part of this process, security features available in cloud platforms like virtual firewalls and threat prevention are incorporated.

After the implementation here, especially since I work in the data center, I've noticed the significance of security. For example, Veeam, CDL, and other aspects became crucial, especially during the COVID period when users started working from home. This situation led to numerous blocks, and user profiles were getting blocked due to issues with IP addresses ending up on blocked lists. However, after implementing the 3M series virtual firewall, we were able to effectively manage security for our cloud applications, like those in AWS. This enabled us to monitor remote workers and take necessary actions, such as blocking problematic IP addresses. Consequently, we reduced the number of tickets raised with ISP providers.        

A valuable feature that we can consider is the deployment time, which is significantly reduced. It is almost 90% faster compared to other solutions. This leads to quicker deployment and less downtime.

I have found that the tool works well for me, but there are areas where security testing and protection could be improved, especially in virtual or cloud environments. However, in this project, once we deployed it, we haven't encountered any issues.

The cost is currently manageable, but as we migrate fully into the cloud, additional features like capacity upgrading and improvements to hardware resources will be necessary, especially since our equipment consists of older-generation switches and routers. So, I'm looking for additional capabilities in these areas.

I've been working on my current project for more than two years now.

I would rate the stability a nine out of ten. 

I would rate the scalability an eight and a half out of ten. 

The deployment is quite straightforward, and it's faster than it used to be. This means that there is less downtime involved.

From my perspective, managing the price is important, especially because we're a small business. For larger organizations like Barclays, we provide our requirements to the client, and they place the order on BigFix. It's their responsibility to consider their budget and make decisions accordingly. We appreciate the features we get, but the cost-sharing still depends on the client.

The client needs to provide approval for the POCs used by our team; it's not within my control.

When evaluating options, you should consider team members who are knowledgeable in supporting next-generation firewalls like NGFW. We also need to factor in the specific product offerings. For instance, if we have options like the PA-440, PA-850, and PA-8350, we should compare their prices and features. It's important to make decisions based on the situation and the needs of the organization.

Considering factors like availability and the specific situation, I would rate this an eight. It's important to explore other potential cases as well.

I would rate the solution a nine out of ten. 

On-premises

The primary use case for Palo Alto Networks PA-Series is for the previous firewall.

The most valuable feature of Palo Alto Networks PA-Series is that it is highly customizable. So far, it works well in terms of threat prevention capabilities.

The interface of Palo Alto Networks PA-Series should be made much more user-friendly.

I have used Palo Alto Networks PA-Series for five years.

I rate the stability of Palo Alto Networks PA-Series as nine.

I rate the scalability of Palo Alto Networks PA-Series around seven.

I rate the technical support from Palo Alto Networks as eight.

Positive

The initial setup of Palo Alto Networks PA-Series is very complicated.

The same device has been used for nine years and could be cost-effective.

The price of Palo Alto Networks PA-Series is expensive.

Although I would recommend Palo Alto Networks PA-Series to others, it would depend on budget and familiarity with the system. If they have the budget and know-how, it might be suitable. However, for users not accustomed to using Palo Alto, I would not suggest it. Overall, I rate this solution as an eight.

On-premises

Most of our clients in Pakistan deploy Palo Alto Networks PA-Series for a variety of use cases. They primarily use it to target VLANs within their networks, including different types of networks like DMZ. These clients integrate the PA-Series with their applications, servers, and often utilize SSL VPNs for secure remote access. These scenarios are typical in the IT sector and align with the types of deployments we see commonly in our region.

We mostly utilize the Spireware profile within Palo Alto Networks PA-Series for threat prevention, which includes basic subscriptions like URL filtering. Many customers are highly satisfied with the threat prevention and firewall capabilities provided. While some customers use team applications like IBM SIM software, we primarily focus on mini CRMs for releases. Through integration and utilizing firewall data, we maintain a strong network security posture, addressing threats effectively. We also conduct security life cycle reviews and leverage tech support files from customers to continually improve our security measures.

The reporting feature and application ID functionality within Palo Alto Networks PA-Series are incredibly valuable to us. With the firewall, we can precisely control and block applications like WhatsApp, log activities, and prevent certain types of uploads. Utilizing the application IDs provided by Palo Alto Networks helps us secure our network effectively. Integration with other tools and systems further enhances our overall security posture. Some of our customers have integrated the Palo Alto Networks PA-Series with Forescout, and the integration is working exceptionally well. We've created policies using Post Guard to detect and block malicious traffic or duplications. When such threats are detected, both the firewall and Postgres work together to promptly block them within the network.

I don't have any specific suggestions for improving the Palo Alto Networks PA-Series at the moment. I find it to be a very effective solution, and I don't have any major complaints or areas for improvement in mind. However, pricing flexibility could be an aspect worth considering, as it has been a concern for some of our clients.

I have been using Palo Alto Networks PA-Series for 5 years.

Similarly, I find the product's stability to be top-notch, also rating it a 10.

In terms of scalability, I would rate it a solid 10 out of 10, indicating excellent scalability capabilities.

Regarding technical support, Palo Alto Networks has been very responsive and helpful whenever I've reached out for assistance or submitted a ticket, earning a positive recommendation from me for their support services.

Setting up Palo Alto Networks PA-Series for the first time is straightforward and easy, especially if you're familiar with firewalling and network configurations.

When it comes to handling large volumes of encryption traffic, PA-Series is effective when encryption detection is focused on sensitive data, although it may reduce speed for overall traffic. I rate PA-Series a 10 out of 10 and highly recommend it to other users due to its reliability and performance compared to competitors like Fortinet.

On-premises

It's our basic firewall, mainly web filtering and application filtering. We use it in a multi-site environment, especially with cloud-based firewalls.

Web filtering and application filtering are the most valuable features. 

The cloud-based aspect helps significantly. It integrates seamlessly with other Palo products like Prisma Cloud, offers robust VPN protection, and it's all in one convenient package.

The UI definitely needs work. In my opinion, the UI could be simpler and more user-friendly for the average user.

For example, I encountered complexities with policy management. Policy management is one of the areas where the UI is not intuitive, and managing policies can be quite complex.

I have been using this solution for one year. We work with all the technologies from Palo.

It is a stable product. I would rate the stability a nine out of ten. 

I would rate the scalability a ten out of ten because cloud deployment makes it incredibly easy to scale.

High-tech, multi-site, or multi-region companies, regardless of size, can benefit from Palo Alto. 

Faster response times would be more beneficial.

Positive

I have experience with Palo Alto's PA-Series and Fortinet FortiGate. 

However, my preference depends on the setup. If I'm looking at a single site, a straightforward deployment, I'd go with FortiGate. 

If I'm looking at multi-site, complex deployments and a cloud-based design, then Palo Alto.

The initial setup is fairly complex. There's a definite learning curve involved in setting it up correctly.

We require assistance from a third-party company for the setup.

The prices are pretty high, definitely on the upper end. They're among the highest in the pricing tier Firewall category.

In general, I'd rate this solution at least an eight out of ten. It has some room for improvement.

Public Cloud