<p>You wish to understand the correct policy order to use when utilizing the Web Gateway SSL&nbsp;decryption proxy.</p>

<p>The correct way to configure the policies when using SSL decryption is to arrange them in the following order:</p> <ol> <li>Authentication policy (If using. Only required if using NTLM authentication).</li> <li>SSL Decryption Policies (Required if SSL Interception to DLP or for AV scanning is required).</li> <li>Blocking policies.</li> </ol> <p><strong>SSL Decryption Policy Configuration:</strong><br /> The SSL Decryption policy is essentially a filter to intercept and redirect all SSL traffic that needs to be decrypted, generally in order to send it to DLP. In general, it would be assumed that this traffic will not be blocked (unless a negative DLP response is returned).</p> <p>Configuration options:</p> <ol> <li>Configure the SSL&nbsp;policy to &ldquo;Intercept&rdquo; all categories: This will have the advantage of correctly display a blocking page on those SSL&nbsp;sites that are blocked, but it will place additional resource overhead on the SSL proxy. A single SSL&nbsp;decryption policy intercepting all SSL&nbsp;traffic is required.</li> <li>Configure the SSL&nbsp;decryption policy to intercept only those categories that you do not wish to explicitly block. Note that this may require more than one SSL decryption policy in order to tune individual policies that apply to specific groups. This has the advantage of minimizing the overhead on the SSL&nbsp;proxy, but blocked sites will display a blank page because the SSL&nbsp;traffic is tunnelled.</li> </ol> <p>In the second scenario, if for example you want to run DLP on everyone&rsquo;s Blog posts, but also on the Web mail of Sales, you would need two separate SSL decryption policies; one for Sales above a general policy for all. The Sales SSL policy would apply to Sales LDAP group only, and would ignore everything but Web Mail and Blogs, while the general SSL decryption policy would ignore everything but blogs. You could then apply whatever blocking policies you wish below the SSL policies to apply to the ignored traffic.</p> <p>Remember that if you wish to intercept SSL traffic, you need to import the SWG&nbsp;root certificate on all machines that will be using the SSL&nbsp;proxy (see HOWTO54180 and HOWTO54181).</p> <p><strong>DLP&nbsp;Network Prevent configuration</strong></p> <p>Consult your DLP documentation for direction on implmenting DLP&nbsp;Network Prevent configuration. Symantec does recommend however that you choose to remove/replace the POST/PUT content RATHER THAN block the connection. This will prevent the user from seeing an inexplicable browser error or connection time out, and reduce the impact on the user experience while posting or uploading files.<br /> &nbsp;</p><br/><p><b>Applies To</b><br/><p>The Web Gateway is running in inline-proxy or proxy-only mode. The SSL decryption proxy has been configured.</p>