Firewall Policy cleanup and export

Reply
Highlighted
L1 Bithead

Firewall Policy cleanup and export

Hi All,

 

Hoping to use Expedition to clean up an ASA config without migrating to Palo. Understand it's not the intended purpose but wondering if the imported ASA config can be cleaned up and extracted somehow, perhaps as a raw file?

I can see Project Snapshots are stored as .sql files under /home/userSpace/Projects/<project-name>/Backups.

 

Have used Expedition many times for migrations to Palo and it would be great to have this ability for Customers who are thinking about migrating.

 

Thanks


Accepted Solutions
Highlighted
L5 Sessionator

You can do your tasks as if you were going to push later the configuration into a PANOS device nd, instead, export the resulting Security Rules grid view in Excel.Notice that on the Security Rules view, there is a menu icon on the top right and has an option called Export to Excel.

 

Not sure if this is what you are looking for but if so, that is one way to export it instead of using the database backups that you referred to. Those are only useful within Expedition, as they have all the tables and relationships across the different identified objects.

 

We did not put efforts on doing other vendors config clean up that would allow a config export for other vendors. I mean, Expedition has not been prepared to generate Cisco ASA configurations as an output, so the Excel format is option I could point you to. Also notice that you may get your Cisco ASA configuration improved to use L7 rules, having converted some L4 services into L7 applications, as the goal of Expedition is to help you use the benefits of the PANOS platform.

View solution in original post


All Replies
Highlighted
L5 Sessionator

You can do your tasks as if you were going to push later the configuration into a PANOS device nd, instead, export the resulting Security Rules grid view in Excel.Notice that on the Security Rules view, there is a menu icon on the top right and has an option called Export to Excel.

 

Not sure if this is what you are looking for but if so, that is one way to export it instead of using the database backups that you referred to. Those are only useful within Expedition, as they have all the tables and relationships across the different identified objects.

 

We did not put efforts on doing other vendors config clean up that would allow a config export for other vendors. I mean, Expedition has not been prepared to generate Cisco ASA configurations as an output, so the Excel format is option I could point you to. Also notice that you may get your Cisco ASA configuration improved to use L7 rules, having converted some L4 services into L7 applications, as the goal of Expedition is to help you use the benefits of the PANOS platform.

View solution in original post

Highlighted
L1 Bithead

Thanks @dgildelaig, appreciate the response.

Output to CSV is helpful but was hoping to output as ASA config.

It would be great if we could convince every Customer to migrate to Palo

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!