Configure SSL Inbound Inspection

SSL Inbound Inspection decryption enables the firewall to see potential threats in inbound encrypted traffic destined for your servers and apply security protections against those threats.
Use SSL Inbound Inspection to decrypt and inspect inbound SSL traffic destined for a network server (you can perform SSL Inbound Inspection for any server if you load the server certificate onto the firewall). With an SSL Inbound Inspection Decryption policy enabled, the firewall decrypts all SSL traffic identified by the policy to clear text traffic and inspects it. The firewall blocks, restricts, or allows the traffic based on the Decryption profile attached to the policy and the Security policy that applies to the traffic, including and any configured Antivirus, Vulnerability Protection, Anti-Spyware, URL-Filtering, and File Blocking profiles. As a best practice, enable the firewall to forward decrypted SSL traffic for WildFire analysis and signature generation.
Configuring SSL Inbound Inspection includes installing the targeted server certificate on the firewall, creating an SSL Inbound Inspection Decryption policy, and applying a Decryption profile to the policy.
  1. Ensure that the appropriate interfaces are configured as either Tap, Virtual Wire, Layer 2, or Layer 3 interfaces.
    You cannot use a Tap mode interface for SSL Inbound Inspection if the negotiated cyphers include PFS key-exchange algorithms (DHE and ECDHE).
    View configured interfaces on the
    Network
    Interfaces
    Ethernet
    tab. The
    Interface Type
    column displays if an interface is configured to be a
    Virtual Wire
    or
    Layer 2
    , or
    Layer 3
    interface. You can select an interface to modify its configuration, including the interface type.
  2. Ensure that the targeted server certificate is installed on the firewall.
    On the web interface, select
    Device
    Certificate Management
    Certificates
    Device Certificates
    to view device certificates installed on the firewall.
    To import the targeted server certificate onto the firewall:
    1. On the
      Device Certificates
      tab, select
      Import
      .
    2. Enter a descriptive
      Certificate Name
      .
    3. Browse for and select the targeted server
      Certificate File
      .
    4. Click
      OK
      .
  3. Create a Decryption Policy Rule to define traffic for the firewall to decrypt and Create a Decryption Profile to apply SSL controls to the traffic.
    Although Decryption profiles are optional, it is a best practice to include a Decryption profile with each Decryption policy rule to prevent weak, vulnerable protocols and algorithms from allowing questionable traffic on your network.
    1. Select
      Policies
      Decryption
      ,
      Add
      or modify an existing rule, and define traffic to be decrypted.
    2. Select
      Options
      and:
      • Set the rule
        Action
        to
        Decrypt
        matching traffic.
      • Set the rule
        Type
        to
        SSL Inbound Inspection
        .
      • Select the
        Certificate
        for the internal server that is the destination of the inbound SSL traffic.
      • (
        Optional but a best practice
        ) Configure or select an existing
        Decryption Profile
        to block and control various aspects of the decrypted traffic (for example, create a Decryption profile to terminate sessions with unsupported algorithms and unsupported cipher suites).
        When you configure the SSL Protocol Settings Decryption Profile for SSL Inbound Inspection traffic, create separate profiles for servers with different security capabilities. For example, if one set of servers supports only RSA, the SSL Protocol Settings only need to support RSA. However, the SSL Protocol Settings for servers that support PFS should support PFS. Configure SSL Protocol Settings for the highest level of security that the server supports, but check performance to ensure that the firewall resources can handle the higher processing load that higher security protocols and algorithms require.
    3. Click
      OK
      to save.
  4. This option requires an active WildFire license and is a WildFire best practice.
  5. Commit
    the configuration.
  6. Choose your next step:

Related Documentation