13.07.2015 Views

Web Security Deployment Guide (PDF) - Websense

Web Security Deployment Guide (PDF) - Websense

Web Security Deployment Guide (PDF) - Websense

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

General <strong>Deployment</strong> RecommendationsFor more information, see Chapter 3: Deploying Network Agent.As a network grows and the number of Internet requests increases, componentscan be deployed to additional, non-dedicated machines to improve processingperformance on the dedicated machines.• You can deploy multiple Filtering Service instances, connected to one PolicyServer. This is useful for remote or isolated sub-networks. For moreinformation, see Number of Filtering Services allowed per Policy Server.• Since a maximum of 5000 connections per Policy Server is recommended,multiple Policy Servers may be needed.IMPORTANT: To ensure the integrity of the firewall, do not install <strong>Web</strong>sensecomponents on the firewall machine.NoteNetwork Agent can be deployed with the filteringcomponents or on a separate machine. Network Agentshould not be deployed on the same machine as responsecriticalcomponents. For more information, see Chapter 3:Deploying Network Agent.Network Agent suggestionsUp to four Network Agents per Filtering ServiceOne Filtering Service may be able to handle more than four Network Agents.Network Agent can typically monitor 50 Mbits of traffic per second, or about 800requests per second. The number of users that Network Agent can monitor depends onthe volume of Internet requests from each user, the configuration of the network, andthe location of Network Agent in relation to the computers it is assigned to monitor.Network Agent functions best when it is close to those computers.If a component’s capacity is exceeded, filtering and logging inconsistencies mayoccur.Contact your <strong>Web</strong>sense software provider for technical assistance with specificNetwork Agent sizing guidelines.Number of Filtering Services allowed per Policy ServerUp to 10 Filtering Services per Policy Server is recommended. A Policy Servermay be able to handle more, depending on the load.Multiple Filtering Service instances are useful to manage remote or isolated subnetworks.The appropriate number of Filtering Service instances for a Policy Server depends on:The number of users per Filtering Service28 <strong>Web</strong>sense <strong>Web</strong> <strong>Security</strong> and <strong>Web</strong>sense <strong>Web</strong> Filter

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!