Next-Generation Firewall
Configure a Policy Based Forwarding Rule
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
-
- Cloud Management of NGFWs
- PAN-OS 10.0 (EoL)
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0
- PAN-OS 11.1 & Later
- PAN-OS 9.1
-
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0
- PAN-OS 11.1 & Later
-
-
-
- Cloud Management and AIOps for NGFW
- PAN-OS 10.0 (EoL)
- PAN-OS 10.1
- PAN-OS 10.2
- PAN-OS 11.0
- PAN-OS 11.1
- PAN-OS 11.2
- PAN-OS 8.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 9.1
Configure a Policy Based Forwarding Rule
Configure a Policy Based Forwarding (PBF) rule for your
managed firewall.
Contact your account team to enable Cloud Management for NGFWs using
Strata Cloud Manager.
Where Can I Use
This? | What Do I Need? |
---|---|
|
|
Use a Policy Based Forwarding (PBF)
rule to direct traffic to a specific egress interface on the firewall
and override the default path for the traffic.
- Log in toStrata Cloud Manager.
- Selectand select the Configuration Scope where you want to configure the PBF rule.ManageConfigurationNGFW and Prisma AccessNetwork ServicesPolicy Based ForwardingYou can select a folder or firewall from yourFoldersor selectSnippetsto configure the PBF rule in a snippet.
- Add Rule.
- Enter a descriptiveNamefor the PBF rule.
- (Optional) Enter aDescriptionfor the PBF rule.
- Select the PBF rulePosition.
- Pre-Rule—Policy rule is added to the top of the rule order and evaluated head of any locally defined policy rules and post-rules.If no position is selected, the PBF rule is created as a pre-rule by default.
- Post-Rule—Policy rule is added to the bottom of the rule order and evaluated after the pre-rules and locally defined rules.
- (Optional) To trigger the specified forwardingActionat a daily, weekly, or nonrecurring frequency, select or create aSchedule.
- Configure the traffic Source.
- Select the sourceTypeto which you’ll apply the forwarding policy rule.
- Only Layer 3 interfaces are supported; loopback interfaces don’t support PBF.To enforce symmetric return, you must select a source interface.
- Specify the sourceAddressesto which the PBF policy rule applies.Individual addresses, address groups, or external dynamic lists (EDL) are supported as source addresses. A PBF policy rule is configured to apply toAny Addressby default.ClickNegateto exclude one or more source addresses from the PBF rule.
- Specify the sourceUsersto whom the policy rule applies.Individual users or user groups as source users. A PBF policy rule is configured to apply toAny Userby default.ClickNegateto exclude one or more source users from the PBF rule.
- Configure the traffic DestinationAddressesto which the PBF policy rule applies.Individual addresses, address groups, or external dynamic lists (EDL) are supported as destination addresses. A PBF policy rule is configured to apply toAny Addressby default.ClickNegateto exclude one or more destination addresses from the PBF rule.
- Select the Applications and Services that you want to control using PBF.
- (Optional)Add Applicationsto add one or more applications to control.Any Applicationis selected by default if you don’t add any applications.Palo Alto Networks doesn’t recommend application-specific rules for use with PBF. PBF rules might be applied before the firewall has enough information to determine the application. Whenever possible, use a service object, which is a Layer 4 port (TCP or UDP) used by the protocol or application. For more details, see Service Versus Applications in PBF.
- Add Servicesto add one or more services to control. You can alsoAdd Service Groupsto add multiple services as a single service entity.Any Servicesis selected by default if you don’t add any services or service groups.
- Define the Forwarding action and network information for packets that match the PBF policy rule.
- Select theActionto take when matching a packet.
- Forward(default)—Directs packet to the specifiedEgress Interface.
- Discard—Drops the packet.
- No PBF—Excludes the packets that match the criteria for source, destination, application, or service defined in the rule. Matching packets use the route table instead of PBF; the firewall uses the route table to exclude the matched traffic from the redirected port.
- (Forward only) Select theEgress Interfaceto forward matching packets to.
- (Forward only) Select theNext Hop.
- None(default)—The destination IP address of the packet is used as the next hop. Forwarding fails if the destination IP address isn’t in the same subnet as the egress interface.
- IP Address—Enter an IP address or select an address object of typeIp Netmaskto which the firewall forwards matching packets. An IPv4 address object must have a/32netmask.
- FQDN—Enter an FQDN or select or create an address object of type FQDN to which the firewall forwards matching packets. The FQDN must resolve to an IPv4 address.This FQDN must resolve to an IP address that belongs to the same subnet as the interface you configured for PBF; otherwise, the firewall rejects the resolution and the FQDN remains unresolved.
- (Optional; Forward only) EnableMonitorto verify connectivity to a target IP address or to theNext HopIP address if no IP address is specified.
- Select a monitoringProfileorCreate Newto specify the action when the monitored address is unreachable.
- You canDisable this rule if nexthop/monitor ip is unreachable.
- Enter a targetIP Addressto monitor.
- (Required for asymmetric routing environments; Optional otherwise)Enforce Symmetric ReturnandAddor more IP address in theNext Hop Address List.You can add up to eight next-hop IP addresses. Tunnel and PPoE interfaces are not supported as a next-hop IP address.
- Save.
- Push Configto push your configuration changes.