ASA to PAN - Security Rule Based on pre-NAT Issue

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

ASA to PAN - Security Rule Based on pre-NAT Issue

L2 Linker

Not sure if anyone else ran into this.


ASA's security policies are built based on post-NAT rules (post 8.3 OS)


With the tool, it builds the same rules with the post-NAT rules, private IP ... which will not work with PAN as the rule is built based on post-NAT, public IP.


Is there an option in the tool to convert the IP to pre-NAT?


L5 Sessionator

The migration should have used the post-NAT IP as the destination address in a corresponding security policy.


If you open the NAT rule then open the 'Security Rules Match' does the security policy show the pre or post NAT IP address?

The migration tool is building the security policy based on the private IP, post-NAT.


PAN matches based on pre-NAT, public IP.


In the NAT rule, the Security Rules Match does not have an entry. The first 4 reviewed has the same behavior.


What's interesting is that the migration tool prepends the NAT rule name with "Nat Twice" Not sure if there is a reasoning for it.



NAT-twice indicates its likely a bi-directional NAT rule learned from the ASA config. If you can share you config to: I can look at it.

  • 3 replies
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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!