Web Security initial configuration

Deployment and Installation Center | Web Security Solutions | Version 7.7.x

Applies to:

In this topic:

Web Filter, Web Security, and Web Security Gateway (Anywhere), v7.7.x

Getting started with Web Security solutions

Additional tips for working with Web Security solutions

Identifying Filtering Service by IP address

Getting started with Web Security solutions

After entering your Web Security subscription key (see Initial Configuration for All Websense Modules), perform the following initial steps in TRITON - Web Security (the management console).

For more complete instructions for any step, click Help in the TRITON toolbar, then select Explain This Page. Alternatively, use the New User Quick Start tutorial to run through the initial steps needed to start applying Web Security policies to user requests.

If Websense Filtering Service must go through a proxy server or firewall to connect to the Internet, navigate to the Settings > General > Database Download page and provide connection details.

Filtering Service must be able to connect to the download server to:

Verify your subscription.

Download the Master Database used to enable Web filtering.

On the Main tab, go to the Policy Management > Policies page and edit the Default policy.

This policy acts as a safety net. It applies to any requests not governed by another policy. Until you define clients and create custom policies, this is the policy that applies to all Internet requests that pass through your Web Security solution.

On the Settings tab, go to the Settings > General > Directory Services page and configure the directory service (if any) used in your network. This configuration must be performed before you can apply specific policies to users, groups, and OUs in your network.

On the Main tab, go to the Policy Management > Clients page and define the clients (IP addresses, IP address ranges, users, groups, and OUs) to which you want to apply policies.

If you have Web Security Gateway or Gateway Anywhere, also see Content Gateway initial configuration.

If you have Web Security Gateway Anywhere, also see Additional configuration for Web Security Gateway Anywhere.

Next, you can:

Create custom policies and filters on the Policy Management > Policies and Filters pages. (More information about what filters are, and how they work with policies, is available from the New User Quick Start tutorial or the TRITON - Web Security Help. Both are available from the Help menu in the TRITON console.

Configure transparent user identification on the Settings > General > User Identification page (see the "User Identification" topic in the TRITON - Web Security Help).

If you installed Logon Agent, you must create and deploy a client logon script in addition to configuring Logon Agent in TRITON - Web Security. See the Using Logon Agent for Transparent User Identification technical paper for instructions.

If you were unable to grant User Service, DC Agent, or Logon Agent administrator privileges during installation, see the "Troubleshooting" > "User Identification" topic on changing User Service, DC Agent, and Logon Agent service permissions in TRITON - Web Security Help.

Enable email or SNMP alerting on the Settings > Alerts > Enable Alerts page (see the "Alerting" topic in the TRITON - Web Security Help).

Customize reporting behavior (see the "Reporting Administration" topic in the TRITON - Web Security Help).

Configure optional Remote Filtering components to enable filtering of off-site users. For instructions, see the Remote Filtering Software technical paper.

Additional tips for working with Web Security solutions

All Websense tools and utilities installed on Windows Server 2008 (such as wsbackup.exe and websenseping.exe), as well as text editors used to modify Websense configuration files (such as websense.ini), must be run as the local administrator. Otherwise, you may be prevented from running the tool or the changes you make may not be implemented.

Navigate to the Websense bin directory (C:\Program Files or Program Files (x86)\Websense\Web Security).

Right-click the relevant executable file, and then click Properties. Following is a list of files for which this should be done.

In the Compatibility tab, under Privilege Level, select Run this program as an administrator. Then, click OK.

If you installed Network Agent on a machine with multiple NICs, you can configure the agent to use more than one NIC to monitor and block requests. See the "Network Configuration" topic in TRITON - Web Security Help for more information. To configure a stealth mode NIC for monitoring, see Network Agent and stealth mode NICs.

Identifying Filtering Service by IP address

When Websense software blocks an Internet request, the browser is redirected to a block page hosted by Filtering Service. The block page URL takes the form:

http://<FilteringServiceNameorIPAddress>:<MessagePort>/cgi-bin/blockpage.cgi?ws-session=#########

If Filtering Service is installed on a machine with multiple NICs, and Filtering Service is identified by machine hostname rather than IP address, users could receive a blank page rather than a block page.

If you have an internal domain name server (DNS), enter the Filtering Service machine's IP address as a resource record in your DNS. See your DNS documentation for instructions.

If you do not have an internal DNS:

On the Filtering Service machine, go to the Websense bin directory (by default, C:\Program Files\Websense\bin or opt/Websense/bin).

Make a backup copy of eimserver.ini in another directory.

Open the original eimserver.ini file in a text editor.

In the [WebsenseServer] section, enter the following command:

BlockMsgServerName=<IP address>

Here, <IP address> is the IP address of the Filtering Service machine.


	Important Do not use the loopback address (127.0.0.1).

Save the file.

Restart Websense Filtering Service. See Starting and stopping Web Security services.