Palo Alto Networks Panorama can be used for managing all your files at once. Its primary use case is that it's a centralized management system for firewalls. For example: we have a company with four different sites, and each one of those sites has two Palo Alto networks in there, so rather than do one integration, then replicate it four times, what we do is we plug it all into Palo Alto Networks Panorama and make the change once, and it pushes out to all the firewalls, regardless of where those are located.
What I find brilliant in Palo Alto Networks Panorama is that you can create variables. The template stack function of the system is also valuable. You can create one profile for several firewalls, and I find that really, really cool. If there's a file on the network that needs to have an address arrangement, you can just import it similar to how you do a CSV import. It's a solid product and it does what it's supposed to do.
The ease of use of Palo Alto Networks Panorama is an area for improvement, because it's not very easy to use. The downside with the system is that you need a lot of comprehension to understand what it is. There are also risks associated with making a change, e.g. you can accidentally break your network which knocks off the firewall, and then you can't get back on again. If you know what you're doing, e.g. if you're a specialist, then there won't be any problems, in general.
It's important to gain an understanding of Palo Alto Networks Panorama, or the concept, before you start. It works like Palo Alto, but it doesn't at the same time, because you have templates, and the templates have to be applied before your variables, and then those variables directly affect your objects. It's important to understand how it works. I wish they could make it easier, and a bit more intuitive, but if you're doing the training, and you're properly in the system, then it will make sense the way it's explained to you, otherwise, it'll be hard to make sense of it.
It could be difficult to get to the stage you want to be on with this system. It's similar to a different language, and it's so hard to just do it on your own, but if you are in the culture and you're speaking to other people, then it becomes easier because you're doing it. That's the learning curve right there, e.g. if you've never done it before, you'll sit and look around saying: "What is this? I don't understand." If you're doing the training, and you're more involved in the product, or even if you speak to specialists, they will be able to help you, then you start to learning it and what it can do.
I've been dealing with Palo Alto Networks Panorama for four years now.
Palo Alto Networks Panorama is very, very scalable. The way the system works is that you have clustering, so you can have all these machines connect to each other in stacks. It's a completely scalable system.
Technical support for Palo Alto Networks Panorama is good. I'm giving them a score of four out of five.
The setup for Palo Alto Networks Panorama is quite difficult, because you're essentially building this one machine, then you have to create all the log ins, then once you've done that, you start registering your files, but you have to do an ingestion on them. You have to bring the file all in, and then it takes the config then puts the config back out again, but that config will then be a "protected config", so if I was logging onto that machine locally, I can't change that file.
The setup is quite easy just to build the machine, but to get it to work is quite difficult.
I've been dealing with version 10.0 of Palo Alto Networks Panorama. I'm a reseller of this solution.
One person could do the deployment and maintenance for Palo Alto Networks Panorama, but what we do in our office is: we have a buddy system. If there's a change that needs to be made, e.g. if someone does the work, someone verifies it, and then catches any problems there, because if you're managing several firewalls, one more change might break all of them. That's the risk that you're in.
My advice to others who are planning to implement Palo Alto Networks Panorama is to look at the use case, e.g. if you have two firewalls, or if you have several firewalls across the country, it's best to get a specialist in to help you deploy it. For a regular IT guy who works in a company managing the server, etc., it'll be such a hard learning curve to go through. Try and learn it yourself if you can, but if not, always defer to a specialist.
I'm rating Palo Alto Networks Panorama seven out of ten, just because it's quite difficult.