Palo Alto Networks VM-Series Reviews

The most valuable features are security and support.

The packet routing speed is very good.

There should be an option for direct integration with the Azure platform. This would allow this product to take advantage of the auto-scaling that is offered by Azure. Because I am purchasing it as a SaaS model, I should get the complete functionality.

I would like to see the direct support and product ownership from the principal vendor. Ideally, the vendor should maintain ownership and be responsible for the system, including that it is operating correctly. This would give my company a better value when purchasing the product.

The pricing could be improved.

The Panorama management license should come with this solution. We have eight nodes and we still have to purchase it separately. Everything should come with a single license, rather than something that is broken into many parts.

I have been using the Palo Alto VM-Series Firewall for a few months.

This solution is stable.

This is a scalable solution but it would be better if it had direct integration with Microsoft Azure.

Currently, we have three administrators and more than 5,000 end-users through our public website.

Technical support is very good and I would give them full marks.

This firewall is easy to implement. 

Everything from Palo Alto is good and I recommend that people implement this firewall.

I would rate this solution a ten out of ten.

We use it to protect applications and data on AWS.

Embedding it into my application development lifecycle prevents data loss and business disruption, allowing the adoption to operate at the speed of my AWS Cloud.

It prevents data loss and business disruption.

It can definitely improve on the performance.

I would like more scalability included on the next release.

It has a good performance which helps you with the stability of your virtual environment.

It has to be more scalable for the deployment of VMs on the cloud.

You have to be an expert administrator of a virtual environment to know how to integrate it with your AWS environment.

Purchasing through the AWS Marketplace is a secure way to purchase this solution. Our organization chose to procure this solution via the AWS Marketplace because we have clients who were interested in the solution. Also, for out proof of concept, we decided to purchase it.

The pricing and licensing of this product on AWS should be from $1.28/hr or $4,500.00/yr. Then, it would be a good price for the performance that it delivers.

It solves several challenges protecting your AWS workloads with good security features, delivering superior visibility, control, and threat prevention at the application level when compared to other cloud-oriented security solutions.

I have not tried integrating Palo Alto with other products.

We use this as our primary security barrier between trusted and untrusted zones.

App-ID and User-ID have repeatedly shown value in securing business critical systems.

In AWS, Palo Alto provides us a better view than flow logs for network traffic.

We have ran into issues with Palo Alto’s limitations for resolving large IP lists from DNS lookups, as well as the antivirus interfering with App-ID.

I would like to see a more thorough QA process. We have had some difficulties from bugs in releases.

I see more improvements needed from AWS than from Palo Alto on the VM-Series, namely a design centered on NGFW.

We are typically at only about eight to ten percent load.

The limit of the product is based on resources that we can obtain from AWS. We have approximately 3500 users and 200 servers leveraging the Palo Alto product.

We used BYOL, because of the cost to own.

We procure the solution through AWS Marketplace because previous experience with their physical appliances.

The pricing and licensing of this product on AWS for a three-year commitment is a great deal, if you can plan that far ahead.

It is a good product, but there is room for improvement.

We use this with Microsoft AD, N2WS, IIS, MySQL, MS SQL, and a number of proprietary applications.

Primary use case is network protection, next-generation IDS, and IPS protection.

• It provides better protection.
• There is seamless integration.
• It provides complete security posture from end-to-end. This has given us better visibility into what our security aspects are.

The next-generation features of its IDS and IPS.

The product could provide protection above Layer 3, which gets into the application layer and provides better visibility into those aspects of application security. This would be very helpful. This way, there would be one tool that we could continue using.

The data aspects of data security and data loss prevention could provide visibility which would be very useful.

It is stable. We haven't had any issues and don't think about the stability.

One of the great features that we liked and selected it was its  scalability. We can autoscale and put it in Auto Scaling groups, which is very useful.

We have hardly any issues. We have had some patches of data needing some help, but that was it, and the technical support has been spot on.

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

We used technical support in the initial stages when we were setting it up and configuring some of the features. We used their Professional Services, who were very useful.

We have already seen ROI. 

We continue using it, because the concept was at six months, we should receive value back out of it. If the value is seen, only then would we continue using it. It is two years later, and we still continue using it.

Because the solution was getting deployed on AWS, it was the best place to go and it was available there.

One of the factors for selecting Palo Alto was they had flexible pricing. They had a pay-as-you-go model. Comparable to other products, such as Check Point, the price point was definitely a plus. It was expensive but it was comparable.

We looked at Palo Alto, Check Point, Fortinet, and some other vendors.

We chose Palo Alto because its features, especially its advanced features from the IDS and IPS. We were existing customers with Palo Alto from the on-premise side along with the integration aspects of its hardware.

Identify a use case first of all. If the use case is a match, then use the product.

We use it in the cloud for both AWS and non-AWS versions. The AWS version is far better. It works seamlessly and integrates very well with some other services. 

We have integrated it with Splunk for the security aspects and with identity and access management for configuration purposes. 

We use Palo Alto for the VPN, firewalls, and the hybrid site-to-site.

We have purchased Palo Alto VM for one of our customers. It has been a year since we have been using this product.

We use Palo Alto's on-premise version for a different purpose. We are using the cloud version for our contractors to VPN to the AWS environment.

For Palo Alto on-premise, we use it more for security firewalls. On the cloud side, we use it for customer contractors to get into the AWS environment for VPN. we use native routing and native security tools that they developed already in AWS. 

We have big team which can support Palo Alto on-premise. We have engineers which are familiar with Palo Alto products. Our customers are perfectly suited for our use case. They wanted to get onto AWS or be on the hybrid cloud. They want to keep the technology consistent across the board. Therefore, Palo Alto makes sure that they are a leader in this space. We are able to support them, and customers can take advantage of using these products, both on-premise and cloud.

• Firewalls
• VPN

On the cloud side, they need to come up with more HA solutions to support the multi-region.

The stability is fine. The product has been running well so far.

We have about 150 contractors who log into Palo Altos. We don't put heavy stress on them, but they are working fine for now.

You already can scale it if you put it in Auto Scaling groups. If you put it in a load balancer, it should already be able to scale. 

We put our Palo Altos in the public VPC, then we have contractors come over the Internet and VPN into the Palo Altos to get into the AWS environment. 

It depends on the person you get on the call from technical support, but many times I have gotten good people on the call. Sometimes, you get some bad experiences. Most of the time, it has been good.

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 purchase process through AWS Marketplace was easy for us because we are partner to Palo Alto, so it was straightforward. All we need to do was purchase it from AWS Marketplace because we had a license.

AWS is available as a AMI that you can purchase from the AWS Marketplace. Therefore, you need to purchase the licensing, since it is per AMI. Then, you deploy it on a regular EC2. Then, for on-premise, you can use both Palo Alto's software and hardware. So, it depends on your usage.

Compared to other solutions, I think the pricing is efficient.

For on-premise, we evaluated Check Point and Fortinet.

I would recommend the product, and tell people, "Go for it." It has not disappointed us for the purpose that we use it. It is really matured in the networking area.

Because of our use case, we didn't have to integrate the product with anything else.

The AWS side of the product is a seven out of ten rating. The on-premise side of the product is a ten out of ten for a rating.

We use it to secure all traffic leaving and entering AWS.

It allows us to see all our traffic to properly secure it and only allow what is needed through the firewall.

• Full content inspection
• Visibility into the traffic in AWS.

There is work to be done on the integration side, as AWS doesn't integrate well with third-party firewalls.

I would like to see AWS have more integration with Palo Alto from a routing standpoint, so it could become a routing egress without having to redesigning it.

It is very stable, and we are not putting stress on it.

It is fairly scalable. We have a couple hundred servers already.

They are the leading next-generation firewall. I would recommend deploying a next-generation firewall.

I am using the on-premise and AWS version. They are exactly the same.

• To do a lot of intrusion detection.
• Threat prevention.
• As an application firewall, to be able to securely deliver apps to the public.

It gives us the ease that we are secure. We have set up the proper things that help make our data safe. This is the biggest benefit.

It offers a single pane of glass for all the different types of installations.

The easy of use is pretty good.

I would like a way to do everything programmatically, or be able to copy the configs from different prices at different levels.

The stability is excellent. We have about 50 to 60 employees on it per day. Then, we have about 100 edge connected devices coming through it as well.

It is definitely scalable. We have about 100 users with about 200 to 300 instances on the cloud that we protect.

The technical support is really good. It is usually one phone call to get everything done if we are having an issue.

We chose to purchase Palo Alto through the AWS Marketplace because we needed an easy to use firewall and a way to protect our public applications and services.

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.

We haven't had any security issues since deploying it.

Purchasing on the AWS Marketplace was simple, effective, and easy.

The price is not bad. They have a yearly renewal fee, and the pricing is exactly where we expect it to be.

We also evaluated Fortinet, but Palo Alto is sort of the new up and coming product. There were a lot of good recommendations from other security experts.

In addition, Palo Alto is easier to configure when you are building policies on applications. 

Talk to their technical services to make sure you are getting the right size solution for what you want to do.

The product is easy use. I don't have to think twice when I am using it. I know it is doing its job. Customer support has been great.

We are using both the AWS and on-premise versions. Both versions are about the same. The interface is nice and easy to configure. I like that it seems like it is one platform to manage.

We use it for firewall purposes.

We use it mostly for the firewall and its ability to work in AWS. That is why we like it.

AWS has improved our agility to apply firewall rules. It has reduced the amount of time that it takes to apply firewall rules because everything is based in the cloud. It helps us to bring agility to the project teams when applying them.

We still need to understand what are the best practices which we need to implement. 

We also don't know how it will scale once we start putting more load on it.

We like its stability.

We are happy with the scalability. 

We just started migrating to the cloud. Thus, we are slowly adding more volume to it. Maybe next year, we should know how it is scaling in the cloud.

We have in-house experts and a good relationship with the Palo Alto technical support team.

We were using a lot of Cisco firewalls before. We switched because we wanted what works best in the cloud.

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

It takes the bottleneck away from the information security teams and increases their agility on projects. 

We found purchasing process the product on the AWS Marketplace to be very good. We used the AWS Marketplace because we were set to move to AWS. We rely on Amazon and their partners to process our research.

I would recommend to try it out.