Configure Transparent Bridge Security Chains
A layer 1 Transparent Bridge security chain forwards traffic from one firewall interface through a directly connected series of data inspection and processing security devices and then back through a different firewall interface without the need to route the traffic.
Before you configure a layer 1 Transparent Bridge 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.
To distribute sessions across multiple Transparent Bridge security chains, create one layer 1 Transparent Bridge security chain on the firewall for each of the security chains you want to use to load balance traffic. Each Transparent Bridge security chain on the firewall requires two dedicated layer 3 Ethernet interfaces. Check to ensure that you have enough free Ethernet interfaces for the topology you want to configure.
Layer 1 Transparent Bridge security chains cannot failover to another security chain because they are not routed.
- 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.
- (Optional) To use Health Monitoring on Transparent Bridge paths, you must configure a static IP address on each interface. SelectIPv4andAdda static Layer 4 IP address. You can also configure IPv6 addresses for Transparent Bridge interfaces (but not for Routed Layer 3 security chains).
- 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.If you inadvertently configured a DHCP or PPPoE address, theNetwork Packet Brokeroption is grayed out. Return to theIPv4tab and set theTypetoStatic.
- 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 layer 1 Transparent Bridge security chain.
- SelectandObjectsPacket Broker ProfileAdda new profile or modify an existing profile.
- Give the profile aNameandDescriptionso that you easily identify its purpose.
- On theGeneraltab:
- SelectTransparent Bridge (Layer 1)as theSecurity Chain Type.
- Enable IPv6if the traffic is IPv6 traffic.
- 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 Prepare to Deploy Network Packet Broker) 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.
- TheSecurity Chainstab is not used for Transparent Bridges.
- 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. 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 layer 1 Transparent Bridge 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.
- For each layer 1 Transparent Bridge security chain:
You can load balance traffic by creating Network Packet Broker policy rules that divide traffic relatively equally among the Transparent Bridge security chains. You can also use policy rules to direct specific traffic and types of traffic through specific security chains.Layer 1 Transparent Bridge security chains cannot failover to another security chain because they are not routed. Use theHealth Monitortab in the Packet Broker profile to configure how to handle traffic if a Transparent Bridge security chain fails.
- The two Ethernet interfaces used as Network Packet Broker forwarding interfaces must be dedicated to each security chain. Ethernet interfaces used for a Transparent Bridge security chain cannot be used for any other purpose or carry any other traffic.
- Each pair of Network Packet Broker forwarding interfaces connects to one layer 1 Transparent Bridge security chain.
Recommended For You
Recommended videos not found.