Filtering Web 2.0
Published on Wednesday, 20 July 2011 15:32
Written by Scott O'Neill
With these types of sites, it is no longer acceptable to just out-and-out block them at the whole site level. Portions of the site should be blocked or have safesearch applied, while other parts of the sites need unrestricted access.
To deal with Web 2.0 filtering, Netsweeper uses the dynamic categorization at the URI level to fulfil policy requests. This means that the full categorization process applies for every URI requested by a client. It must be remembered that this process, when viewed in the structure of a Web 2.0 page, or ‘mash-up’ of content will see each individual request generated by the single URI requested by the end user, and then each URI requested by the page also. This allows the Netsweeper solution to monitor and categorize every aspect of the content delivered to the end user (instead of relying upon the categorization of the Top Level Domain of that URI).
Whenever one of the 50 million current users of Netsweeper first accesses these URIs , they go through this categorization process (and are subsequently available as categorized to the rest of our users). In addition, users and administrators are able to request a human review of URIs—either to add a URI to a category, remove a URI from a category, or add a URI to multiple categories. All sites reviewed manually are immediately updated in the Categorization Database and are available to the Master Category Name Server. These sites/updates are also downloaded nightly to the Category Name Server and Policy Server caches. The mastered database is a database of humanly reviewed and re-classified sites that is checked every 5 minutes for any changes, and the changes are downloaded automatically.
Dynamic, not hard-coded
Using the dynamic categorization of the Netsweeper solution, all sites and services can be controlled via policy at the granular level of the URI itself. This enables the Administrator to make decisions and block aspects of the full page delivered by the Web 2.0 URI. Utilizing this function, for example, will allow components of a FaceBook webpage, embedded advertising, uploads and other content to be blocked without blocking overall access to FaceBook.
Full granular control for filtering Web 2.0
The Netsweeper solution allows administrators to configure all policy setting to the URI level allowing full granularity for the policies as applied to filtering Web 2.0. For instance, this could allow blocking Twitter but allowing posts to approved “Twitter-like” sites.