topic Please share an example of correct CSV for NAT import in Expedition Discussions

Please share an example of correct CSV for NAT import

Per_Westerlund — Wed, 19 Jun 2019 16:40:51 GMT

I'm working on producing a CSV file to use as a source for NAT rules. Right now I only need interface hide NAT (using default interface address as hide address).

I have not been able to find any documentation (including the latest published CSV import guide) that has an example that gives any hint to how the fields 'tp_source' and/or 'interface' should be formatted to get this behaviour.

I don't need updated documentation, but would very much appreciate a single example of a line from a CSV file that Expedition can ingest correctly, getting the expected interface hide NAT result.

/Per Westerlund

Re: Please share an example of correct CSV for NAT import

Per_Westerlund — Tue, 09 Jul 2019 15:13:38 GMT

Bumping this.

No help?

I have tried to export NAT rules from Expedition (to Excel) that contains interface hide, but even that export removes the interface that is present in the original NAT rule in Expedition.

Please give us a way to handle importing NAT from CSV, there are still some firewalls (Clavister) that are not natively supported.

/Per

Re: Please share an example of correct CSV for NAT import

sjanita — Tue, 09 Jul 2019 19:42:07 GMT

There are certainly improvements that need to be made to the CSV import specifically for import of NAT policies using CSV.

The current supported field mappings are described in the link below. The current CSV for NAT does not support the interface option as a field mapping.

https://live.paloaltonetworks.com/t5/Expedition-Articles/A-How-To-guide-on-the-Import-CSV-option/ta-p/258388