Senso.cloud filters SSL traffic and in some instances where a website or application needs their own SSL Certificate installed, the site may no longer work when senso is installed.


There are 2 sure ways to avoid this and get the website or application working again.


1. Add the application .exe name to the SSL Exclusions list

2. Add the website IP Address to the SSL URL exclusions list


Both options are set in the Logging and Blocking Policy.

Finding the Logging And Blocking Policy

Logging and blocking policies can be set at any level. Typically the policy would either be at the top level or at the site level. Alternatively you may find it set on a group within the sites.

If you don't know where you logging and blocking policy is set. You can tick the device you are seeing this issue on and then click the passport



That should open up a window for you that will show which policies are effecting the device and where they are.


Application Exclusions


The Logging and Blocking Policy has an option to exclude processes from SSL Filtering.  Simply add the process name or part of the path to the SSL Application Exclusions box.



An example would be:


app1.exe|system32|folder\app2.exe|


The above example will allow app1.exe, wherever the app exists on hard disk to be excluded.  It also allows any application in the System32 folder to go unfiltered and finally, any app2.exe residing in Folder to be excluded.

This will of course not work if its a website that has the issue because you cannot exclude browsers (chrome, ie, firefox etc) otherwise all logging and blocking for those browsers will no longer work.



URL/IP Exclusions


The Logging and Blocking Policy has an option to exclude IP Addresses and URL's from SSL Filtering.  Simply add the URL or IP to the SSL URL Exclusions box.



An example would be:


192.168|10.0|website.com


The above example will allow an IP address containing '192.168' and '10.0' to completely bypass the Senso SSL Filter, and any URL containing website.com will go unfiltered.