YouTube recently implemented bot detection similar to what has been running on www.google.com for a few years. As far as we can tell, this was released in the summer of 2019. Google/YouTube are very tight-lipped regarding the specifics around these protections to ensure bot developers can't easily code their way around them.
After careful traffic observation, we have a few ideas on how to mitigate impact to schools using YouTube as an educational resource.
Steps we've taken
2. YouTube ban- Since we are still seeing CAPTCHAs coming from YouTube, we developed a YouTube Ban. This sounds scary, but we've developed it to be very passive. We have also coded a lot of intelligence into it so we can easily modify actions based on what we see happening in the field. YouTube ban will look for x number of CAPTCHA events within y minutes and block the USER for z minutes. All of the variables are real-time configurable so we can ensure we are stopping the bots and not causing unnecessary blocks.
What to do if users are seeing YouTube ban block pages
From conversations with Google developers, they claim only users with malware, spyware, malicious toolbars, and the like will receive CAPTCHAs. Similarly, users will only see the YouTube ban block page if they receive multiple CAPTCHAs from YouTube within a short period of time. It would be safe to say, there is something on the device that is causing enough suspicious YouTube traffic to generate our block page.
1. Re-image the device. This is a drastic step, but it would ensure the user stops seeing CAPTCHAs from YouTube and thus would stop seeing the YouTube ban block page from Securly.
2. Run an AV scan on the device. This should pick up and remediation any malicious code.
3. Have the user remove any non-essential toolbars from their browser. Toolbars have been known to cause suspicious traffic.
In closing, we want our customers to know we are working tirelessly to help schools overcome these recent YouTube issues.