Configure Routed Layer 3 Security Chains
A routed layer 3 security chain forwards traffic to a series of data inspection and processing security devices and then back to the firewall using two dedicated forwarding interfaces on the firewall.
Before you configure a routed layer 3 security chain, take the steps to Prepare to Deploy Network Packet Broker and ensure that the physical connections between the firewall and the security chain devices are correct. Check to ensure that you have enough free Ethernet interfaces on the firewall for the topology you want to configure.
Each routed layer 3 security chain that you configure on the firewall requires two dedicated layer 3 Ethernet interfaces, which can connect to one layer 3 security chain or distribute sessions (load balance) to up to 64 layer 3 security chains with a properly configured router, switch, or similar device between the firewall and the security chains.
Network Packet Broker cannot forward IPv6 traffic on a routed layer 3 security chain. To forward IPv6 traffic, use a Transparent Bridge (layer 1) security chain.
- Enable two Layer 3 Ethernet interfaces as Network Packet Broker forwarding interfaces.
- Select an unused Ethernet interface to use as one of the two Network Packet Broker forwarding interfaces.
- Set theInterface TypetoLayer3.
- On theConfigtab, select a zone to assign the interface to.You must configure both of the security chain interfaces in the same zone.
- On theConfigtab, as a best practice, use or create a dedicated Virtual Router to assign the interface to. Using a dedicated Virtual Router ensures that the Network Packet Broker interface traffic remains separate from other traffic.
- SelectAdvancedand then selectNetwork Packet Brokerto enable the interface.
- ClickOKto save the interface configuration.
- Repeat this procedure on another unused Ethernet interface to configure the other Network Packet Broker forwarding interface.
- Configure a Packet Broker profile to control how to forward the traffic to the routed layer 3 security chain.
- SelectandObjectsPacket Broker ProfileAdda new profile or modify an existing profile.
- Give the profile aNameandDescriptionso that you easily identify its purpose.
- On theGeneraltab:
- SelectRouted (Layer 3)as theSecurity Chain Type.
- Select theFlow Direction.Your network topology determines whether to use unidirectional or bidirectional flows. The performance is approximately the same using either method.To use one firewall interface to forward both the c2s and s2c session flows to the security chain and use the other firewall interface to receive both session flows back from the security chain, selectUnidirectional.To useInterface #1to forward the c2s flow to the security chain and receive the s2c flow from the security chain, and useInterface #2to forward the s2c flow to the security chain and receive the c2s flow from the security chain, selectBidirectional.
- Specify the Network Packet Broker forwarding interface pair inInterface #1andInterface #2. Both interfaces must already be enabled for Network Packet Broker (see Step 1) to be available for use. Be careful to pay attention to the directionality of flow when you configure which interface isInterface #1and which interface isInterface #2.Session distribution (load balancing) only applies to new sessions. The firewall does not rebalance traffic in the middle of a session. The firewall only distributes sessions to security chains whose status is “up” (active, healthy).
- On theSecurity Chainstab,Addthe IP addresses of the first and last device in each routed layer 3 security chain to which you want to connect. You must specify at least one security chain or the firewall can’t route traffic to a chain and you can’t save the profile.If you specify multiple routed layer 3 security chains, then you also need to place a correctly configured router, switch, or similar device between the firewall and the security chains to perform the proper routing. In addition, specify theSession Distribution Methodto load balance the traffic among the security chains.
- On theHealth Monitortab:
- Select the type or types of health monitoring you want to perform so that you can control what happens if the security chain experiences a failure.You can select one, two, or all fromPath Monitoring,HTTP Monitoring, andHTTP Monitoring Latency.Path Monitoring—Checks device connectivity using pings.HTTP Monitoring—Checks device availability and response time.HTTP Monitoring Latency—Checks device processing speed and efficiency. When you select this option,HTTP Monitoringis automatically enabled as well.
- Enabling one or more types of health monitoring activates theOn Health Check Failureoptions, which determine how the firewall handles security chain traffic if there is a security chain health failure.If you configure multiple security chains on one set of routed layer 3 Network Packet Broker interfaces, then on a security chain failure, traffic fails over to the remaining healthy security chains. If there is no security chain available to handle failover traffic, the firewall takes the action configuredOn Health Check Failure. The options areBypass Security ChainandBlock Session.Bypass Security Chain—The firewall forwards the traffic to its destination instead of to the security chain and the applies any configured Security profiles and protections to the traffic.Block Session—The firewall blocks the session.The method you select depends on how you want to treat the traffic if you can’t run the traffic through the security chain.
- If you select more than one health check option, select whether you want the firewall to consider the health check as failed (Health Check Failed Condition) if any one of the monitoring options records a failed condition (OR Condition) or only if all of the selected monitoring options record a failed condition (AND Condition). For example, if you enable all three health check options and one of the options records a failed condition, if you selectedOR Condition, the firewall considers the security chain connection to be failed and executes the action you specified inOn Health Check Failure. If you selectedAND Condition, the firewall would still consider the connection to be healthy because two of the health metrics are still OK.
- ClickOKto save the profile.
- Configure a Packet Broker policy to define the traffic to forward to the routed layer 3 security chain.
- SelectandPoliciesNetwork Packet BrokerAdda new policy rule or modify an existing policy rule.
- On theGeneraltab, give the policy rule aNameandDescriptionso that you easily identify its purpose, add anAudit Comment, and apply tags if you use them.
- On theSourcetab, identify the source zones, IP addresses, users, and devices of the traffic that you want the rule to forward to the security chain.
- On theDestinationtab, identify the destination zones, IP addresses, and devices of the traffic that you want the rule to forward to the security chain.
- On theApplication/Service/Traffictab, identify the applications and services you want the rule to forward to the security chain. Unless the rule control applications that you expect to use non-standard ports such as internal custom applications, the best practice is to set theServicetoApplication Defaultso that applications that exhibit evasive behavior by using non-standard ports are blocked.For theTraffic Type, select all of the types of traffic that you want the rule to forward to the security chain.Forward TLS(Decrypted) Trafficis the default selection. You can select any combination ofForward TLS(Decrypted) Traffic,Forward TLS(Non-Decrypted), andForward Non-TLS Trafficto forward to the security chain.
- If you want to create separate routed layer 3 security chains that use different dedicated pairs of firewall interfaces, then repeat Step 1 through Step 3 to create more Network Packet Broker security chains. The two layer 3 Ethernet interfaces used as Network Packet Broker forwarding interfaces must be dedicated to the security chain and cannot be used for any other purpose or carry any other traffic.
Recommended For You
Recommended videos not found.