Configure Decryption Broker with One or More Layer 3 Security Chain

1. Follow the Layer 3 Security Chain Guidelines to make sure that you’ve set up your security chain to support decryption broker.
2. Activate the free Decryption Broker license (see Decryption Licenses).
3. Confirm that the firewall is enabled to perform SSL Forward Proxy decryption.
   Select PoliciesDecryption to Add or modify a decryption policy rule. You can also attach a decryption profile to a decryption policy rule, to perform certificate checks and to validate SSL protocols. For example, a decryption profile allows you to block sessions based on certificate status, using unsupported protocols or cipher suits, or if the resources to perform decryption are not available.
4. Enable a pair of Layer 3 interfaces to forward decrypted traffic.
   1. View configured interfaces on the NetworkInterfacesEthernet tab. The Interface Type column displays if an interface is configured as a Layer 3 interface. Select a Layer 3 interface and complete the following steps for both Layer 3 interfaces that you want to enable as a Decrypt Forward pair.
   2. Select the Config tab and assign the interface to a Virtual Router that has no configured routes or interfaces used to pass dataplane traffic. The virtual router must be dedicated to the decryption forwarding interfaces to ensure the clear text sessions that the firewall forwards for additional analysis are totally segmented from dataplane traffic.
   3. Continue to assign the interface to a Security Zone. (Assign both interfaces to the same security zone).
   4. On the Advanced tab, select Decrypt Forward.
   5. Click OK to save the interface settings.
   6. Repeat these steps for an even number of interfaces, pairing two as you go.
   7. Make sure that the interfaces enabled to forward decrypted traffic are not being used to pass any other type of traffic.
5. Create a Decryption Forwarding profile to define settings for the firewall to forward decrypted traffic to a Layer 3 security chain.
   1. Select ObjectsDecryptionForwarding Profile, Add a new Decryption Forwarding Profile, and give the profile a descriptive Name.
   2. On the General tab, set the Security Chain Type to Routed (layer 3) to configure the firewall to forward decrypted traffic to a security chain with Layer 3 devices.
   3. Set the Flow Direction for decrypted traffic the firewall forwards: Unidirectional or Bidirectional.
   4. Select the Primary Interface and Secondary Interface the firewall uses to communicate with the security chain.
      Together, the primary and secondary interfaces form a pair of decryption forwarding interfaces. Only interfaces that you have enabled to be Decrypt Forward interfaces are displayed here. Your security chain type (Layer 3 or Transparent Bridge) and the traffic flow direction (unidirectional or bidirectional) determine which of the two interfaces forwards allowed, clear text traffic to the security chain, and which interface receives the traffic back from the security chain after it has undergone additional enforcement.
   5. Click OK to save the decryption profile.
6. Connect the firewall to a security chain.
   1. Select the Security Chains tab and Add a security chain.
   2. Name and Enable the security chain.
   3. Enter details for the First Device and Last Device in the security chain.
      Give the device a descriptive Name, and select the IPv4 address of the first device in the security chain. Or, you can define a new Address Object to easily reference the device.
   4. Click OK to save the security chain, and continue to repeat these steps to add another security chain. Or, continue on if you’re only adding a single chain.
7. (Multiple Security Chains Only) Continue on the Security Chains tab and choose the Session Distribution Method for the firewall to use to distribute decrypted sessions amongst security chains.
   Choose for session distribution to be based on IP Modulo, IP Hash, Round Robin, or Lowest Latency. The Lowest Latency distribution method requires you to also enable the firewall to perform HTTP Latency Monitoring and HTTP Monitoring on the security chain.
8. Select the Health Monitor tab to enable the firewall to perform Security Chain Health Checks on security chains.
   If a security chain fails a health check, the firewall can then either block traffic until the security chain passes a subsequent health check and is able to process it, or the firewall can allow traffic to bypass a failed security chain.
   1. On Health Check Failure, choose for the firewall to either Bypass Security Chain or Block Session.
   2. Define a Health Check Failed Condition as an event where any of the health monitor conditions are met (an OR Condition), or when all of the conditions are met (an AND Condition).
   3. Enable Path Monitoring, HTTP Latency Monitoring, and/or HTTP Monitoring. For each type of monitoring you want to enable, define the periods of time and/or counts that you want to trigger a health check failure.
      Latency and HTTP monitoring are required to effectively support Lowest Latency session distribution (ObjectsDecryptionForwarding ProfileSecurity Chains Session Distribution Method).
9. Save the Forwarding profile.
10. Attach the Forwarding Profile to a decryption policy rule.
    The firewall decrypts and inspects traffic the rule matches, and then forwards the clear text traffic to the security chain for further inspection and enforcement.
    1. Select PoliciesDecryption and select a decryption policy rule.
    2. Select Options.
    3. Set the Action to Decrypt and Forward.
    4. Select the Forwarding Profile you created.
    5. Click OK to save the policy rule and Commit your changes.
11. Monitor the decrypted traffic that the firewalls forwards for additional inspection.
    1. Select MonitorLogsTraffic and use the following filter: (flags has decrypt-forwarded).
    2. Check the details for a traffic log entry and look for the Decrypt Forwarded flag.