Configure NAT for threat defense
The NAT policy is a shared policy. Assign it to devices that need similar NAT rules.
Each rule applies to a device if its interface objects (security zones or interface groups) include an interface for that device. When the interface objects include one or more interface for the device, the rule is deployed to the device. You can target subsets of devices within a shared policy by designing interface objects accordingly. Rules using the "any" interface object apply to all devices.
If you change an interface type to one not valid for NAT on an assigned device, the policy marks the interface as deleted. Click Save in the NAT policy to automatically remove the interface from the policy.
You can configure multiple NAT policies if groups of your devices require significantly different rules.
Procedure
Step 1 | Navigate from Security Cloud Control to Cloud-Delivered Firewall Management Center |
Step 2 | Select .
|
Step 3 | Decide what kinds of rules you need. You can create dynamic NAT, dynamic PAT, static NAT, and identity NAT rules. For an overview, refer to NAT types. |
Step 4 | Decide which rules should be implemented as manual or auto NAT. For a comparison of these two implementation options, refer to Auto NAT and Manual NAT. |
Step 5 | Decide which rules should be custom per device. Because you can assign a NAT policy to multiple devices, you can configure a single rule on many devices. However, you might have rules that should be interpreted differently by each device, or some rules that should apply to a subset of devices only. Use interface objects to control on which devices a rule is configured. Then, use object overrides on network objects to customize the addresses used per device. For detailed information, refer to Customize NAT rules for multiple devices. |
Step 6 | Create the rules as explained in these sections. |
Step 7 | Do these to manage your NAT policy:
|
Step 8 | Do these to manage your NAT rules:
|
Step 9 | Click Save. You can now go to and deploy the policy to assigned devices. The changes are not active until you deploy them. |


