SSH Service Profile

[securehops]

Question regarding SSH Service Profiles.  If you create a SSH Service Profile in Panorama for a template that is associated with firewalls running 10.x and 9.x, will it fail when you commit the changes for the 9.x firewalls?

I'm in the process of upgrading all firewalls to 10.1, so in the meantime I've been creating the profiles locally, but would be easier to create in Panorama.  I wasn't sure if the commit will fail or it will just be ignored on 9.x firewalls

[PavelK · Accepted solution]

Hello @securehops

thanks for post!

Prior to upgrading Panorama to 10.2, we used to have Panorama running 10.1 and Firewalls running mix of 10.1 and 9.1. When did not come across any major issue with pushing Device Group / Template Stack to Firewalls running 9.1, however we are not using SSH profiles in Template, therefore I can't speak for this particular setting. The only thing that comes to my mind are supported cipher suites of  versions 9.1 versus 10.1. Some of them were deprecated, so if you try to push something to Firewall running PAN-OS that does not support it, it might fail.

https://docs.paloaltonetworks.com/compatibility-matrix/supported-cipher-suites/cipher-suites-support...

https://docs.paloaltonetworks.com/compatibility-matrix/supported-cipher-suites/cipher-suites-support...

Kind Regards

Pavel

[securehops]

Thanks @PavelK , I forgot to update the thread after I posted.  I pushed the SSH Service Profile out and didn't have any issues

[dwharam]

While you can use Panorama and a template to create the "SSH Service Profile", it doesn't look like you can use a template to actually set this SSH Service Profile on the MGT interface on all your firewalls.  Am I missing something?