Applying YouTube Header Restrictions in Netskope

Netskope Global Technical Success (GTS)

Applying YouTube Header Restrictions in Netskope

Netskope Cloud Version - 120

Objective

Apply the content restrictions currently available on YouTube through Header insertion.

Prerequisite

Ensure that YouTube, or alternatively, the “Streaming & Downloadable Video” category, is not in bypass or part of a steering exception so that Netskope can apply Header Insertion.

Context

The client wants to use the Header Insertion functionality to control the available restrictions on YouTube.

Configuration

Currently, YouTube offers three methods for content restriction, which can be reviewed here: YouTube Content Restriction Methods. These methods include DNS, HTTP Headers, and Chromebooks. In this case, we’ll focus on using HTTP Headers (HTTP Headers Option) to meet this use case through Netskope.

The configuration process is straightforward:

1. Go to Settings > Manage > Header Insertion in Netskope.
2. Click on New Header Insertion Profile and add the key according to the options currently available on YouTube. 
   1. YouTube-Restrict: Strict.
   2. YouTube-Restrict: Moderate.

Once configured, ensure the changes are applied to your clients. There are two ways to validate this setup:

1. Visit YouTube Content Restriction Check from the test endpoint to confirm that "HTTP header restrictions are on" is checked.

2. Browse YouTube and observe that restrictions are enforced according to the policies set by YouTube.

This setup should ensure that YouTube content restrictions are correctly applied through Netskope. Please take a look at the Google’s documentation on this topic for more details:

• https://support.google.com/a/answer/6212415

Additional information can be found at this Netskope Document:

• https://docs.netskope.com/en/header-insertion/

Terms and Conditions

• All documented information undergoes testing and verification to ensure accuracy.
• In the future, it is possible that the application's functionality may be altered by the vendor. If any such changes are brought to our attention, we will promptly update the documentation to reflect them.

Notes

• This article is authored by Netskope Global Technical Success (GTS).
• For any further inquiries related to this article, please contact Netskope GTS by submitting a support case with 'Case Type – How To Questions'.