09/06/2022 1,568 People found this article helpful 470,389 Views
This article explains how we can use Deep Packet Inspection to perform Content Filtering on HTTPS websites.
Deep Packet Inspection of Secure Socket Layer (DPI-SSL) extends SonicWall's Deep Packet Inspection technology to allow for the inspection of encrypted HTTPS traffic and other SSL-based traffic.Normally, without DPI-SSL, HTTPS traffic cannot be blocked by SonicWall Security Services. However, with SonicWall DPI-SSL feature, the SSL traffic is decrypted by the SonicWall for inspection, thus enabling SonicWall to inspect traffic and enforce any Security Services prevention on it. This article describes how to block https://www.bing.com using SonicWall Content Filtering (CFS4.0) when DPI-SSL is enabled.
This release includes significant user interface changes and many new features that are different from the SonicOS 6.5 and earlier firmware. The below resolution is for customers using SonicOS 7.X firmware.
In this section we will enable DPI-SSL Client Inspection. The Client DPI-SSL deployment scenario typically is used to inspect HTTPS traffic when clients on the LAN browse content located on the WAN.
For the purpose of this article we will be using Default SonicWall DPI-SSL Certificate Authority (CA) Certificate as the re-signing authority. Users should be instructed to add the certificate to their browser's trusted list to avoid certificate trust errors.
Adding Certificates to Browsers
NOTE: To avoid certificate trust errors and to enable the re-signing certificate authority to successfully re-sign certificates, browsers would have to trust this certificate authority. Such trust can be established by having re-signing certificate imported into the browser's trusted CA list.
Configuring SonicWall Content Filter
How to Test
This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.
In this section we will enable DPI-SSL Client Inspection. The Client DPI-SSL deployment scenario typically is used to inspect HTTPS traffic when clients on the LAN browse content located on the WAN.
For the purpose of this article we will be using Default SonicWall DPI-SSL Certificate Authority (CA) Certificate as the re-signing authority. Users should be instructed to add the certificate to their browser's trusted list to avoid certificate trust errors.
Adding Certificates to Browsers
NOTE: To avoid certificate trust errors and to enable the re-signing certificate authority to successfully re-sign certificates, browsers would have to trust this certificate authority. Such trust can be established by having re-signing certificate imported into the browser's trusted CA list.
Configuring SonicWall Content Filter
How to Test
NOTE: If this is being done from the same computer as the one which is logged into the SonicWall Management GUI, make sure you are logged out before testing. Otherwise, you need go to Security | Content Filter, check the box next to Exclude Administrator under CFS Exclusion section.
The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.
In this section we will enable DPI-SSL Client Inspection. The Client DPI-SSL deployment scenario typically is used to inspect HTTPS traffic when clients on the LAN browse content located on the WAN.
For the purpose of this article we will be using Default SonicWall DPI-SSL Certificate Authority (CA) Certificate as the re-signing authority. Users should be instructed to add the certificate to their browser's trusted list to avoid certificate trust errors.
Adding Certificates to Browsers
NOTE: To avoid certificate trust errors and to enable the re-signing certificate authority to successfully re-sign certificates, browsers would have to trust this certificate authority. Such trust can be established by having re-signing certificate imported into the browser's trusted CA list.
Configuring SonicWall Content Filter
How to Test:
NOTE: If this is being done from the same computer as the one which is logged into the SonicWall Management GUI, make sure you are logged out before testing. Otherwise, navigate to Security | Content Filter, check the box next to Exclude Administrator under CFS Exclusion section.