Migrating from Cisco ASA, strange DNAT rules

[ay.marusov]

Hi all,

I'm trying to migrate configuration from Cisco ASA to Palo Alto NGFW using Expedition.

In the security policy I see a lot of strange rules with word "DNAT" prepended in a name and in a tag. These rules always placed immediately after some legitimate access rule and duplicate it almost exactly except:

- Destination IP is different

- Service field has value 'null' (which of course causes Palo Alto to fails validation of those rules when I import configuration from Expedition).

I assume that those rules have something to do with NAT policy, but it is really unclear what exactly and I cannot find any article in the Expedition documentation that will explain what it is trying to do by creating such rules.

I attached screenshot with the example of such rule.

If someone had similar problem, please give me a clue as to what am I looking at here.

[lychiang · Accepted solution]

Hi @ay.marusov  The DNAT rule is auto created based on your NAT policy, if you double click on the rule and go to "Warning" tab , it will show you which NAT rules associate with this security rule, same thing, you can go to NAT rule and double click on the the NAT rule and go to "Security Rules Match" , it will show you the matching security rules for the NAT rule.