SSL certificate categorization does not work for sub-domains when the OCS presents a wildcard certificate.
Last Updated May 13, 2017
You have a transparent proxy deployment using SSL access rule to block SSL sites based on the BCWF categorization of the CN in the SSL certificate.
Websites which return an wildcard SSL certificate is categorized as 'none' by the ProxySG.
When the OCS presents a wildcard certificate (e.g *.domain.com), the ProxySG also requires a response from DRTR as it cannot purely rely on the wildcard certificate to know what the true requested URL was.
The reason the ProxySG cannot rely on the SSL wildcard certificates alone is because in an unintercepted transparent deployment, the ProxySG only knows the IP address of the site that was requested and the domain portion in the wildcard CN.
The ProxySG will therefore not know if the user requested the 'domain URL' or a 'sub-domain URL'.
The category 'none' is returned if the IP address does not exist in DRTR and a wildcard SSL certificate is returned by the OCS.
Since SGOS 220.127.116.11 the behavior has changed. The proxy will now categorize the request based on the host of the wildcard certificate.
Imported Document ID: 000013646
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe