Comment Quite misleading (Score 1) 119
There are a number of assumptions being made about all of this.
First, it's assuming one is using BlueCoat to begin with.
Second, it's assuming that the users of BlueCoat products are using some of BlueCoat's subscription services to ease management of those devices.
Third, it's assuming that the users of BlueCoat products are not modifying the filters by hand.
I've had some hands-on experience with BlueCoat products in the past, particularly the web-filtering/proxy devices described here, and our organization was large enough to have some of our staff (including myself) manage it part-time as part of their full-time IT responsibilities. We set it up in full white-list mode so that everything not explicitly allowed was blocked by default. We could have set it up in black-list mode or even a hybrid black- and white-list mode. We did not, however, subscribe to the filtering list that BlueCoat offers. That's just one option a customer can choose.
It is unacceptable to me that such filter subscriptions should block well-meaning websites under the guise of preventing porn. But it's entirely possible to remove or even white-list those same sites, on an individual basis, by the customer even if they're included as part of the filter subscription configuration. It's lazy on the part of the staff at BlueCoat for maintaining an inaccurate list and it's lazy on the part of IT managers and staff for keeping those sites blocked if their policies didn't specifically prohibit users from accessing them. The blame can't be solely pinned on BlueCoat, but they certainly share a significant portion of it with IT staff.