Does using translation sites bypass Web Filter on the ProxySG?
search cancel

Does using translation sites bypass Web Filter on the ProxySG?

book

Article ID: 165984

calendar_today

Updated On:

Products

ProxySG Software - SGOS

Issue/Introduction

Does using translation sites bypass Web Filter on the ProxySG?  For example, is there any way we can make sure that a user can't avoid the ProxySG policy by using http://translate.google.com as a "proxy"?

Resolution

As a general rule, the same internet policy applies to translated sites as it does to directly accessed sites, because the site being translated is the site being categorized. For example, if your policy denies social networking categories, http://www.facebook.com will be denied.

The same rule will apply to these example sites:

http://translate.google.dk/translate?u=http%3A%2F%2Fwww.facebook.com&hl=da&ie=UTF-8&sl=en&tl=da.
 

http://translate.google.com/translate?u=facebook.com&hl=en&ie=UTF-8&sl=en&tl=fi

Note: The last site translates Facebook from English to Finnish, and WebFilter should block it as expected.

Some sites use  a POST method for their translation,  and are thus difficult to handle, but in general , the translation sites are handled properly. Webpulse  categorizes what you translate, not the translation site itself, so the same internet use policy applies to translated sites as does to directly accessed sites. This can also be said of  links through http://tinyurl.com/. This site is categorized as computers and internet. Tinyurl.com links work by sending a HTTP 301 redirect to the actual
site. The redirrected URL will still come through the ProxySG, so the actual site should be categorized according to the policy. 
 

Note: If you ever see translation sites that are not handled properly, please let Blue Coat know and they will be added. The most efficient method is to use this site: http://sitereview.bluecoat.com/sitereview.jsp

 

Additional Information

While most sites will still be blocked even if Google Translate is used to hide the URL, there have been cases where the website evaded detection via Google Translate.  If it is not necessary for business operations / if the environment allows, block Google Translate as a proactive feature.