Technical Library | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Refine Web Security Policies > Using Bandwidth Optimizer to manage bandwidth
Using Bandwidth Optimizer to manage bandwidth
Web Security Help | Web Security Solutions | Version 7.8.x
Related topics:
*
Working with categories
*
Working with protocols
*
Configuring the default Bandwidth Optimizer limits
When you create a category or protocol filter, you can elect to limit access to a category or protocol based on bandwidth usage.
*
Block access to categories or protocols based on total network bandwidth usage.
*
Block access to categories based on total bandwidth usage by HTTP traffic.
*
Block access to a specific protocol based on bandwidth usage by that protocol.
 
* 
Note 
If you have Websense Web Security Gateway Anywhere, be aware that the hybrid service does not enforce bandwidth-based restrictions.
For example:
*
Block the AOL Instant Messaging protocol if total network bandwidth usage exceeds 50% of available bandwidth, or if current bandwidth usage for AIM exceeds 10% of the total network bandwidth.
*
Block the Sports category when total network bandwidth usage reaches 75%, or when bandwidth usage by all HTTP traffic reaches 60% of available network bandwidth.
Protocol bandwidth usage includes traffic over all ports, IP addresses, or signatures defined for the protocol. This means that if a protocol or Internet application uses multiple ports for data transfer, traffic across all of the ports included in the protocol definition are counted toward that protocol's bandwidth usage total. If an Internet application uses a port not included in the protocol definition, however, traffic over that port is not included in bandwidth usage measurements.
Websense software records bandwidth used by filtered TCP- and UDP-based protocols.
Websense, Inc., updates Websense protocol definitions regularly to ensure bandwidth measurement accuracy.
Network Agent sends network bandwidth data to Filtering Service at a predetermined interval. This ensures that Websense software accurately monitors bandwidth usage, and receives measurements that are closest to an average.
In a Websense Web Security Gateway deployment, Content Gateway collects bandwidth data for FTP, HTTP, and, when enabled, the individual protocols that tunnel over HTTP (see Tunneled protocol detection). Measurement and reporting parallel that used by Network Agent. You can specify that this data be used to determine bandwidth-based policy enforcement for protocols in the Bandwidth Optimizer settings.
1.
In the Web Security manager, go to Settings > General > Filtering.
2.
Select the Bandwidth Monitoring check box.
3.
When you are finished, click OK to cache your change. Changes are not implemented until you click Save and Deploy.
When bandwidth options are active, enforcement starts 10 minutes after initial configuration, and 10 minutes after each Websense Policy Server restart. This delay ensures accurate measurement of bandwidth data.
When a request is blocked based on bandwidth limitations, the Websense block page displays this information in the Reason field. For more information, see Block Pages.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Refine Web Security Policies > Using Bandwidth Optimizer to manage bandwidth
Copyright 2016 Forcepoint LLC. All rights reserved.