Palo Alto NAT and Security Policy Practice

Practise PAN-OS NAT and security policy for the Palo Alto Networks NGFW Engineer and Network Security Analyst exams. Each problem is a new firewall with source NAT or destination NAT, and Check my answer names your slip, such as the post-NAT IP in the security rule or the post-NAT zone in the NAT rule.

FW1 interfaces
NAT rule
First packet of the session
Security rule that allows it

Security rules match pre-NAT addresses and post-NAT zones. NAT rules match the zone of the pre-NAT address. FW1 sends each interface's subnet out that interface and everything else on the default route.

Exam practice

NAT policy is task 2.2 of the Network Security Analyst exam, zones and routing are tasks 1.2 and 1.4 of the NGFW Engineer exam, and security and NAT policy implementation is part of task 2.1 of Network Security Professional. Start with the free real exam questions, then get the full pack.

Palo Alto NGFW Engineer143 real exam questions · US$39
Free: 36 questionsGet the full pack
Palo Alto NetSec Analyst118 real exam questions · US$39
Free: 44 questionsGet the full pack
Palo Alto NetSec Pro108 real exam questions · US$39
Free: 27 questionsGet the full pack

NAT and policy FAQ

Why does a security rule use the pre-NAT IP but the post-NAT zone?

Palo Alto describes the order like this: on ingress the firewall does a route lookup to find the egress interface and zone, checks the NAT rules, then applies the security policy that matches the original (pre-NAT) source and destination addresses but the post-NAT zones. Translation happens last, on egress. NAT can change the outgoing interface and zone, so the zone is taken after NAT, while the addresses are still the ones in the original packet.

Which destination zone does a destination NAT rule use?

The zone of the original destination. Palo Alto says the destination zone in the NAT rule is determined after the route lookup of the destination IP address in the original packet. In its one-to-one example, users in Untrust-L3 reach a DMZ server on the public address 192.0.2.100, so the NAT rule goes from Untrust-L3 to Untrust-L3, while the security rule goes from Untrust-L3 to DMZ with destination 192.0.2.100.

Does the post-NAT zone apply to the source zone too?

No. The post-NAT zone is the zone the route lookup finds for the translated destination. The source zone is the zone the packet arrives in, and source NAT does not move it. In Palo Alto's example the direction of the policy matches the ingress zone and the zone where the server is physically located.

What is DIPP source NAT?

Dynamic IP and Port (DIPP) lets many inside hosts share one public address, each with different port numbers. The translated address can be an address object, or the address of the egress interface itself, which is why DIPP is sometimes called interface-based NAT. The security rule still matches the inside host's own address, because translation happens as the packet leaves.

When does the packet get the translated address?

Only as it leaves the firewall. Palo Alto: the translation of the IP address and port do not occur until the packet leaves the firewall, and the NAT rules and security policies apply to the original IP address. So in a destination NAT example the packet arrives for the public address and leaves for the server's private address.

What about inside users reaching a DMZ server on its public address?

That is U-turn NAT. Palo Alto's procedure uses a destination NAT rule from the internal zone to the external zone, because the firewall routes the public address to the untrust side. The security rule then follows the same rule as before: the post-NAT zone, the DMZ, with the public address as the destination.

Why does the drill use addresses like 203.0.113.80?

The inside networks use private addresses from RFC 1918, and the public addresses come from the three blocks RFC 5737 sets aside for documentation (192.0.2.0/24, 198.51.100.0/24 and 203.0.113.0/24), so no real network appears in a problem. Palo Alto's own examples use the same blocks.

Sources

Checked 20 November 2026 against Palo Alto Networks' NGFW NAT documentation, its knowledge base and the current exam datasheets.

More free tools

All free tools