Deep Packet Inspection
Deep Packet Inspection
Deep Packet Inspection
Page 1 of 4
How do I inspect HTTPS traffic? [Fireware XTM v11.4.x] Many web sites use both the HTTP and HTTPS protocols to send information to users. While HTTP traffic can be examined easily, HTTPS traffic is encrypted. To examine HTTPS traffic requested by a user on your network, you must configure your XTM device to decrypt the information and then encrypt it with a certificate the user trusts. By default, the XTM device re-signs the content it has inspected with a self-signed certificate. Users without a copy of this certificate see a certificate warning when they connect to a secure web site with HTTPS. If the remote web site uses a certificate that is expired, or if the certificate is signed by a CA (Certificate Authority) the XTM device does not recognize, the XTM device re-signs the content as Fireware HTTPS Proxy: Unrecognized Certificate. If your organization already has a PKI (Public Key Infrastructure) set up with a trusted CA, then you can import a certificate on the XTM device that is signed by your organization. If your organization does not have a PKI, we recommend that you copy the default, self-signed certificate from the XTM device to each client device. This document includes information about how to export a certificate from the XTM device and import it on a Microsoft Windows or Mac OS X system. To import the certificate on other devices, operating systems, or applications, see the documentation from their manufacturers. For more information about how to use certificates with Policy Manager, see About Certificates. For more information about how to use certificates with the Fireware XTM Web UI, see About Certificates.
Answer
The New Policy Properties dialog box appears, with the Policy tab selected.
3. Adjacent to the Proxy Action drop-down list, click the View/Edit Proxy button.
The HTTPS Proxy Action configuration dialog box appears, with the Content Inspection category selected.
4. On the Content Inspection page, select the Enable deep inspection of HTTPS content check box. 5. From the Proxy Action drop-down list, select an HTTP-proxy action to use to inspect HTTPS content, or create a new HTTP-proxy action to use for this policy. 6. In the Certificate Validation section, select the options for OCSP certificate validation. 7. In the Bypass List text box, type the IP address a of web site for which you do not want to inspect traffic. Click Add.
http://customers.watchguard.com/articles/Article/3209/p?pubstatus=o
9/30/2011
Page 2 of 4
9. Click OK to close the HTTPS Proxy Action Configuration dialog box. 10. Click OK to close the New Policy Properties dialog box. 11. Click Closeto close the Add Policies dialog box. From Fireware XTM Web UI First, edit an HTTPS-proxy action to enable deep content inspection of HTTPS content. 1. Select Firewall > Proxy Actions.
The Edit Proxy Action page appears for the proxy action you selected.
3. Expand the Content Inspection section. 4. Select the Enable deep inspection of HTTPS content check box. 5. From the Proxy Action drop-down list, select the HTTP-proxy action to use to inspect HTTPS content. For example, HTTP-Client. 6. Clear the Use OCSP to confirm the validity of certificates check box. 7. In the Bypass List text box, type the IP address of a web site for which you do not want to inspect traffic. Click Add. 8. (Optional) Repeat Step 7 to add more IP addresses to the Bypass List. 9. Click Save.
If you edited a predefined proxy action, you must clone your changes to a new proxy action before you can save them and apply them to a proxy policy. The Clone Proxy Action dialog box appears.
10. In the Name text box, type a new name for the proxy action. For example, type HTTPS-Client DCI. 11. Click OK.
If you have previously imported the certificate on a client, you can export that certificate directly from operating system or browser certificate store. In most cases, this exports the certificate in the x.509 format. Windows and Mac OS X users can double-click an x.509 format certificate to import it.
http://customers.watchguard.com/articles/Article/3209/p?pubstatus=o
9/30/2011
Page 3 of 4
Select File > Add/Remove Snap-In. Click Add. Select Certificatesand click Add. Select Computer account and click Next. Click Finish, Close, and OK to add the certificates module. In the Console Root window, click the plus icon [+] to expand the Certificates tree. Expand the Trusted Root Certification Authorities object. 8. Under the Trusted Root Certification Authorities object, right-click Certificates and select All Tasks > Import. 9. Click Next. Click Browse to find and select the HTTPS Proxy Authority CA certificate you previously exported. Click OK. 10. Click Next, then clickFinish to complete the wizard.
2. 3. 4. 5. 6. 7.
If you are prompted to authenticate as an administrator, type your password or confirm your access.
2. Select the Trusted Root Certification Authorities object. 3. From the Action menu, select All Tasks > Import. 4. Click Next. Click Browse to find and select the HTTPS Proxy Authority CA certificate you previously exported. Click OK. 5. Click Next, then click Finish to complete the wizard.
http://customers.watchguard.com/articles/Article/3209/p?pubstatus=o
9/30/2011
Page 4 of 4
Attachments
http://customers.watchguard.com/articles/Article/3209/p?pubstatus=o
9/30/2011