0 Replies Latest reply on Jul 12, 2017 4:44 PM by jebeling

    Blocking YouTube Sub-functions and Features without API

    jebeling

      SSL scanner must be enabled for any filtering of the YouTube application as it runs strictly on HTTPS. While you can block individual videos by category, uploader, subject, etc using the YouTube ruleset from the online library found on contentsecurity.mcafee.com, and referenced here Intel Security SNS ProTip for Web Gateway: Switch from using older YouTube Category/Uploader rules to using the newer YouTube API v3 rules this requires an API key and import of the ruleset. Even without this ruleset and key you can still control sub applications or sub functions of YouTube using a combination of basic criteria URL.Path and Application.Name. This capability allows administrators to quickly control new functions as they are added without having to wait for McAfee to add a new application definition or category.

       

      A few examples with SSL Scanning Enabled

       

      Block Uploads

      Application.Name equals YouTube

      AND

      URL.Path matches /upload*

       

      Block Live Chat

      Application.Name equals YouTube

      AND

      URL.Path matches /live_chat*

       

      Block Comments

      Application.Name equals YouTube

      AND

      URL.Path matches /comment*

       

      Block Sharing

      Application.Name equals YouTube

      AND

      URL.Path matches /shar*

       

      This should also be possible with WGCS (cloud web service) with policy managed from ePO cloud

       

      URL Blacklist entries (with all subdomains):

      Uploads: youtube.com/upload

      Live Chat: youtube.com/live_chat

      Comments: youtube.com/comment

      Sharing: youtube.com/shar