Hello all. I am deploying Virtual SWG in my envoirement and I need to implement the following functionality.

I need to filter some HTTPS URLs not the whole domain via SSL deep inspection through inline + proxy mode in the virtual envoirement. for example if I want to filter some specific URLs within youtube ( not the whole website)  which is using HTTPS how can this be achieved in this mode ? How to display blocked pages for HTTPS website sfor users ?

what policies do I need to configure ? Secondly in inline + proxy mode do i need to configure my inline IP address within User's browsers ? or will it be transparent for the users ?

What mechanism does SWG use for decrypting the SSL traffic from the users ? does it download certificates of the webistes from internet which users are accessing ?

Regards,

Any 1 help ?

would anyone like to comment on this ?

Hello Outrageous,

I am not SWG expert but provide some of articles if help you.

Can SWG Block an HTTPS address?

Symantec Web Gateway (SWG) considerations and behavior when an external proxy is used

How SSL Deep Inspection differs from SSL Domain Level Inspection

Please see this thread

https://www-secure.symantec.com/connect/forums/webgateway-inline-mode-https

Thanks James, I have already read those articales but I am looking for some specific solution what are not addressed them. Regards,

Sooooo, in order to block specific parts of a SSL encrypted site, you must be using SSL Deep Insepction.  More info on SSL Deep Inspection can be found below (with further useful links inside this article):

http://www.symantec.com/docs/HOWTO54180

Essentially though (in bullet points):

• SWG must in proxy mode
• Enable SSL Deep Inspection
• Download SWG's cert and distribute to clients
• Configure clients to use SWG's LAN/WAN IP address and ports (for https and http respectively) as proxy via GPO/PAC/WPAD/whatever
• Configure SWG Policy for SSL Deep Inspection Inteception
• Configure SWG Policy for filtering (with a lower priority)

As far as blocking pages go, the below articles are quite handy:
http://www.symantec.com/docs/TECH175244
http://www.symantec.com/docs/TECH206412

And to answer your final question, the whole SSL Deep Inspection process works in a man-in-the-middle scenario.  Clients create a SSL connection to the SWG, the SWG creates a SSL connection to the external website.

Any Symantec Employee would please like to comment on this ? Regards

Thanks for your help SM , issue is resloved now :) Regards