Choose from several options for complete web, email and data security.
Learn more
Evaluate Websense products by watching demos and installing evaluation software.
Learn how Websense solutions help keep our customer safe, secure and productive
Get information on product updates, support resources and more.
Get the most out of support in five simple steps.
Find tools and assets to help sell Websense solutions.
Stay informed on the latest security exploits, industry news, research, solutions, and more.
Recommend adding a configuration option to append an organization-specified URL parameter to all YouTube requests (both local and Remote Filter clients) to support YouTube in Schools:
http://support.google.com/youtube/bin/answer.py?hl=en&answer=1686318
Thank you for inquiring about a new feature in Websense Web Security. Your request has been entered into our Feature Request tracking system, and our Product Management team will review it within the next 30 days. If you need a response sooner, we recommend that you open a case with Technical Support. When the request is reviewed, the product manager will decide whether to accept this for future consideration or ask for more information. Please note that Websense receives a high volume of feature requests, and as such Websense cannot include all of these requests in the next product release. That said, the product team is constantly revisiting the list of requests to determine the features that have been most frequently requested, so that the highest priority features are addressed.
We look forward to your continued participation in the Websense community and welcome your active involvement in our product direction.
Thank you.
Hi,
Got a response from the development team :
Please explain exactly what is being requested. Are you asking to block all of YouTube but allow specific YouTube channels?
Would you please provide more information regarding your request?
Phil
Thanks for the follow-up. Please direct the development team to the documentation provided in the URL I included in the initial posting. I am asking that Websense add a feature that supports the rewriting of HTTP requests to YouTube.com to support YouTube in Schools per the referenced documentation, just as Websense now supports the rewriting of HTTP requests to enforce safe search in queries to search engines.
phylliszh: Please explain exactly what is being requested. Are you asking to block all of YouTube but allow specific YouTube channels?
What is needed is that the Websense Content Gateway needs to have the ability to do custom headers when being sent to specific urls (OR) the Web Filter product needs to rewrite the urls (similar to Safe Searching) to change the url for the user to enable this. However, this also requires a new field that the customer will need to fill in for the "school ID" that is required.
See below:
Modify your hardware filter or proxy server settings so that all outgoing traffic to youtube.com contains the following custom HTTP header. The ID to use in the HTTP header configuration, written below, is an example of a unique ID for your school’s network only. If your school is blocked at the district level, this HTTP header is then unique to the district network.
Example:X-YouTube-Edu-Filter:ABCD1234567890abcdef Field Name: X-YouTube-Edu-FilterDescription: When YouTube sees this header and an accompanying valid school ID in the incoming traffic, YouTube will serve a limited EDU-only site to all computers behind the school hardware filter.Field Value Format: alphanumeric [a-z][A-Z][0-9]Field Value Length: up to 44 characters
Example:X-YouTube-Edu-Filter:ABCD1234567890abcdef
If your hardware filter does not support HTTP header modification, please rewrite all outgoing URLs to youtube.com by appending the parameter “edufilter” at the end. Exclude the &edufilter parameter from these file types: .css, .gif, .png, .js, .xml
Example:http://youtube.com/?edufilter=ABCD1234567890abcdef http://youtube.com/watch?v=gM95HHI4gLk&edufilter=ABCD1234567890afbcdef
JACOB SLOAN, CCNA, WCSE
I would like to second this request.
Since we use Websense Remote Filtering, merely implementing header rewriting at the proxy or router level will not work for us, which is why we are requesting that the functionality be integrated into Websense itself.
Forgive my denseness, please, but am I to understand from this thread that neither of the two options offered by YouTube for allowing "YouTube for Schools" traffic is currently supported by Websense?
Thanks.
They are not supported (as in features of Websense), but that does not mean one cannot deploy one of them in an environment that includes Websense, as the two methods of YouTube for Schools involve router, firewall, and/or proxy server changes, which can be made independently of Websense.
Thanks LFCDS.
From a recent article in THE Journal, I learned today that Barracuda Web Filter and Web Security Flex offer YouTube for Schools integration.
Has anyone found a work around or has this received any traction from Websense?
Hi All,
I am glad to let you know that this feature will be implemented in next version 7.7.
Thanks all for your input and patience to get his feature added.
7.7 is scheduled for release late second quarter or early third quarter.
7.6.5 now has this.
http://www.websense.com/content/support/library/web/v765/wsga_release_notes/rnwsga765_new.aspx#664851
Support in Web Security Gateway for "Google Apps for Business," "YouTube for Schools," and other sites with a custom header Web Security Gateway (Anywhere) now supports YouTube for Schools and Google Apps for Business. Special configuration of Content Gateway filtering rules makes this possible. For example, you can now allow Google Business Gmail while simultaneously blocking Google personal gmail.In Content Gateway, to allow YouTube for Schools or Google Apps for Business (or any host that supports filtering via custom headers), define the filtering rule type add_hdr. This causes a custom header-value pair to be inserted, providing support for destination hosts (such as YouTube for Schools) that require a specific header-value pair. You can create an add_hdr rule for any host that supports filtering via custom headers. Following are two setup examples.Example One: Google Apps for BusinessGoogle supports a custom header in the request, containing a comma-separated list of domains that the administrator wants to allow. For example, with the custom header "X-GoogApps-Allowed-Domains", if the header has the value "domain1.com, domain2.com", then "user@domain1.com" and "user@domain2.com" are allowed, but "user@xyz.com" is blocked by Google. When a user attempts to access Google services from an unauthorized account, Google displays a block page similar to this:Content Gateway, as an SSL intercepting proxy, provides a facility for creating and adding the custom header.To implement the solution for Google Apps for Business:In the TRITON – Web Security console, allow the Web Security category Internet Communication > General Email. In Content Gateway Manager, enable HTTPS (SSL decryption). In Content Gateway Manager, on the Configure > Security > Access Control page, open filter.config and create an add_hdr rule (see below). Creating an add_hdr rule:1. Go to the Configure > Security > Access Control > Filtering tab and click Edit File to open filter.config. 2. For Rule Type select add_hdr. 3. For Primary Destination Type select dest_domain. 4. In Primary Destination Value specify "mail.google.com". 5. In the Custom Header field specify "X-GoogApps-Allowed-Domains". 6. In the Header Value field specify your domain. For example: www.example.com. 7. Click Add to add the rule. 8. Click Apply to save all the changes, and then click Close to close the edit window. 9. To put the new rules into effect, select the Content Gateway Manager window and restart Content Gateway. For Google's description of this filtering solution, see the article Block access to consumer accounts and services while allowing access to Google Apps for your organization. Example Two: YouTube for SchoolsTo create an add_hdr rule to allow YouTube for Schools, do the following:1. In Content Gateway Manager, go to the Configure > Security > Access Control > Filtering tab and click Edit File to open filter.config in the file editor. 2. For Rule Type select add_hdr. 3. For Primary Destination Type select dest_domain. 4. In Primary Destination Value specify "youtube.com". 5. In the Custom Header field, specify "X-YouTube-Edu-Filter". 6. In the Header Value field, specify your unique edufilter value. For example: 1234abcd 7. Click Add to add the rule. 8. Click Apply to save all the changes, and then click Close to close the edit window. 9. To put the new rule into effect, select the Content Gateway Manager window and restart Content Gateway. You can create an add_hdr rule for any host that supports filtering via a custom header.
