Panorama objects to be used in a local firewall config through expedition

Arne-VDH — Fri, 10 Apr 2020 12:29:51 GMT

Hi,

In a somewhat unusual case I'm trying to use objects pushed through Panorama, in a policy in expedition. Both Panorama and the firewall are linked & imported in the expedition project.

Moving the firewall policy to an all Panorama policy isn't an option here (yet). Is there a way I can use a Panorama object (already present on the firewall) and use it in local policies through expedition (or the find/replace functionality)?

Re: Panorama objects to be used in a local firewall config through expedition

dgildelaig — Tue, 14 Apr 2020 10:56:46 GMT

If the current FW policy is using the object, the object should appear in Expedition when importing the configuration.

This would be one of our called "ghost" objects.

We identify those objects if we see them used in the configuration but not being declared (as it is the Panorama push config the one declaring the object).

One trick would be to create a disabled rule using the object, or an object group using that object in the FW, and when importing the configuration into Expedition, those objects would show up.

We do not directly go to the Panorama configuration to see which are the objects that may have been pushed to the NGFW.

topic Panorama objects to be used in a local firewall config through expedition in Expedition Discussions

Panorama objects to be used in a local firewall config through expedition

Re: Panorama objects to be used in a local firewall config through expedition