Web Security Deployment Guide (PDF) - Websense

Deploying Network Agentinstances may be needed, depending on the size, volume of Internet requests and thenetwork configuration.The Network Agent machine can connect to the network via a switch or a hub. SeeHub configuration, page 54, and Switched networks with a single Network Agent, page55.Network Agent can be installed on the same machine as an integration product. SeeGateway configuration, page 59.WarningDo not install Network Agent on a machine running afirewall or Remote Filtering Server. On a firewall,Network Agent’s packet-capturing that may conflict withthe firewall software. On a Remote Filtering Server,machine resources may be too heavily taxed.There is one exception: A blade server or appliance withseparate processors or virtual processors may be able tosupport both Network Agent and firewall software orRemote Filtering Server.Network Agent settingsConfigure Network Agent global (applying to all agent instances) and local (specificto a single agent instance) settings in Websense Manager. These settings tell NetworkAgent which machines to monitor and which to ignore.Global settings:• Specify which machines are part of your network.• Identify any machines in your network that Network Agent should monitorfor incoming requests (for example, internal Web servers).• Specify bandwidth calculation and protocol logging behavior.Local settings:• Specify which Filtering Service is associated with each Network Agent.• Identify proxies and caches used by the machines that this Network Agentmonitors.• Determine which network card (NIC) the Network Agent instance uses tomonitor requests and which it uses to send block pages.Configuration settings for the NIC used to monitor requests determine whichsegment of the network the agent instance monitors.48 Websense Web Security and Websense Web Filter