Decryption policies are used to create groups of rules defining which traffic should be decrypted. This decision is based on match criteria such as source IPs and destination IPs. Each decryption policy can have its own match criteria, along with an associated action. Once the match is done, we can decide whether we need to decrypt or bypass.
In SonicOSX 7.0, the HTTPS content filtering is no longer present. So, if we want to allow HTTPS websites, we need Client DPI SSL and a corresponding decryption policy to inspect them.
Decryption policy rules define what type of traffic needs to be decrypted. There are three types of rules that can be added, each with its own parameters that can be used for the match.
The match criteria for these rules can contain the following traffic parameters:
Client-side SSL Rules:
Server-side SSL Rules:
SSH Rules:
Before we can create a decryption policy, these features should be enabled globally.
To Enable Client DPI-SSL:


To enable Server DPI-SSL:



To enable DPI-SSH

To create a Client SSL Decryption Policy




To Create a Server SSL/SSH Decryption Policy
