Web Security Deployment Guide (PDF) - Websense

General Deployment RecommendationsNetwork AgentNetwork AgentLogging of bytes transferred Database engine (Microsoft SQL Server 2005/2000, MSDE 2000, MySQL 5.0).SQL Server 2005 is recommended.For enterprise networks, see Deploying in a Distributed Enterprise supplement to thisguide for more information.Network Agent can be installed on the same machine as other Websense components,or on a separate machine.When a small or medium network, for example, exceeds 1000 users, or when NetworkAgent misses Internet requests, place Network Agent on a different machine thanFiltering Service and Policy Server.If Websense software is running in a high load environment, or with a high capacity(T3) Internet connection, you can increase throughput and implement load sharing byinstalling multiple Network Agent instances. Install each agent on a different machine,and configure each agent to monitor a different portion of the network.ImportantNetwork Agent must have bidirectional visibility into thenetwork or network segment that it monitors.If multiple Network Agents are installed, each agent mustmonitor a different network segment (IP address range).If a Network Agent machine connects to a switch, themonitor NIC must plug into a port that mirrors, monitors,or spans the traffic of all other ports. Multiple segmentnetwork, page 51, and Network Agent location, page 49,discuss locating Network Agent in more detail.HTTP reportingYou can use Network Agent or an integration product to track HTTP requests and passthe information to Websense software, which uses the data to filter and log requests.Network Agent and some integration products also track bandwidth activity (bytessent and received), and the duration of each permitted Internet request. This data isalso passed to Websense software for logging.When both Network Agent and the integration partner provide logging data, theamount of processor time required by Filtering Service doubles.34 Websense Web Security and Websense Web Filter