|
In this topic: |
Web Filter Server
The Web Filter Server enforces Acceptable Use Policy by preventing users from accessing portions of the Internet. Installed as a Windows service, the Web Filter Server listens for Clients requesting to go online. Any Clients using Server Web Filtering (as opposed to Local Web Site blocking) are subjected to the rules the Web Filter Server delivers from the database.
Like the Primary Server and Data Vault services, the Web Filter Server service appears as an icon in the Windows notification area. Control the Web Filter Server from the Control Center's Properties.
To use Server Web Filtering:
Install the Web Filter Server on a computer (static IP) with network access to the Spector 360 Database and to all Clients. See the Spector 360 Deployment Guide
When you configure the Client, make sure Server Web Filtering is enabled in the Client's Block Web Sites settings.
At the Dashboard, define Website Filtering Rules, specifying the categories of domains you wish to filter, the Time Profile for applying filtering, and the users to receive the filtering. The Spector 360 Database provides pre-defined System Categories for your convenience. See the Spector 360 Dashboard Guide
As soon as the Client is installed and running, each time the Client computer requests to go online to a web site, it first checks with the Web Filter Server.
The Web Filter Server tells the Client what is allowed or not allowed, based on filtering rules currently in the database (as set in the Dashboard). The first rule is applied first, then the second, and so on.
If a domain ends up being blocked by the rules, a customized message with a hyperlink can be displayed. The link might lead to an explanation of Acceptable Use Policy or to a request for Internet access. If a domain is not blocked by the rules, the web site is displayed.
This type of filtering is dynamic and based on the user login, rather than a specific Client computer. The Dashboard provides ways of testing the Filtering Rules to see if blocking is occurring as you wish. See the Spector 360 Dashboard Guide for complete information about Website Filtering.
When Server Web Filtering is active:
The server enforces both block and allow rules by priority, as instructed.
The server applies different Time Profiles and different sets of users to each rule, as instructed.
The System Categories provided with the Spector 360 Database cover well-known web sites. You can combine these with your own Custom Categories for a complete filtering policy.
You can change the rules or the domains WITHOUT reconfiguring the Client computer.
Client blocking of Internet ports and Chat/IM contacts still applies (see "Combination Filtering" below).
|
|
When Server Web Filtering is active, the Client's When to Block and Who to Block settings will NOT apply to web sites. They will ONLY apply to Internet Blocking of ports. |
If Server Web Filtering is NOT enabled, you can use the Client settings to provide the a list of web sites (domains) to block or allow at each local Client. This type of filtering is static and affects only users logging into the specific computer where the settings are applied. Local Client Filtering is described in this guide.
When Local Web Filtering is active:
The Client ignores instructions from the Web Filter Server.
Even if the computer is removed from the network or connected to any other network the filtering will be applied.
The Client's When to Block and Who to Block settings apply to the specified web sites in addition to specified ports.
You would change the filtering on any computer by applying new Client Settings.
|
|
It is possible to revert to Local Web Filtering as a backup when the Web Filter Server is not available (when the Client computer is removed from the network). See Block Web Sites. |
You can use Server Web Filtering in combination with Local Client Filtering for the most effective blocking policy. Although Server Web Filtering overrides Local Filtering as far as web sites (domains) are concerned, if you are also blocking ports or Chat/IM, the most restrictive policy always applies.
Examples
If you block All Internet Access at the Client, no Server Web Filtering rules will apply, because no Internet access is allowed.
If you block HTTP/HTTPS ports during work hours at the Client, the Server Web Filtering rules will apply ONLY during "off" hours, when the Internet port access is allowed.
If you block HTTP/HTTPS ports for specific users at the Client, the Server Web Filtering rules will apply to OTHER users. These users are simply blocked from accessing web sites altogether.
If you allow ONLY Chat/IM from specific teachers or business associates at the Client, there will be no incoming messages from unauthorized contacts, even though filtering rules may allow access to a chat room domain.
If you block ports used by Kazaa at the Client, the user will NOT be able to download media at those ports, even if the domain is permitted.
If you block File Transfer via FTP, a user might be able to visit a site, but the Client will NOT allow an FTP download from the site.
