|
|
|
|
Network Agent Quick Start : Configuring Network Agent
|
|
1.
|
In the Web module of the TRITON Manager, go to the Settings > Network Agent > Global page.
|
|
2.
|
Make sure that the Ignore Internal Traffic list includes all IP addresses in your network.
|
|
This information is not used to determine which machines are monitored for policy enforcement. Instead, it allows Network Agent to ignore internal communications while monitoring Internet traffic.
|
|
Click Add to add an IP address or IP address range to the list.
|
|
|
Mark the check box next to an entry, and then click Delete to remove it from the list.
|
|
3.
|
Use the Internal Traffic to Monitor list to specify internal IP addresses (included in the network definition list) for which you do want Network Agent to monitor connections from other internal IP addresses. You might include internal web servers, for example, to help track access to internal resources.
|
|
4.
|
Use the Additional Settings options allow you to determine how often Network Agent calculates bandwidth usage, and whether and how often protocol traffic is logged:
|
|
5.
|
When you are finished making changes, click OK to cache the changes. Changes are not implemented until you click Save and Deploy.
|
|
1.
|
Under Settings > Network Agent, highlight or mouse over Global, then select the IP address of the Network Agent instance that you want to configure.
|
|
2.
|
Select the Filtering Service IPv4 address that identifies the Filtering Service instance with which this Network Agent will communicate (Planning Worksheet 2). If Network Agent and Filtering Service are installed on the same machine, the local IP address is selected by default.
|
|
3.
|
Indicate whether Network Agent should block or permit all requests If Filtering Service is not available.
|
|
4.
|
Under the Network Interface Cards list, use the Proxies and Caches list to specify any proxy or cache machines that monitored machines use to access the Internet. This keeps Network Agent from identifying requests from both the client machine and the proxy or cache machine, which could result in duplicate log records or incorrect filtering.
|
|
5.
|
Expand Advanced Network Agent Settings.
|
|
a.
|
With TRITON AP-WEB, or when Web Filter & Security is integrated with a third-party product, verify that the Integration manages HTTP traffic on ports value is correct. (The default is 80, 8080.)
|
|
b.
|
If you want Network Agent to ignore traffic on specific ports, mark Configure this Network Agent instance to ignore traffic on the following ports, and then enter one or more ports in a comma-separated list.
|
|
6.
|
|
1.
|
Click an entry in the Network Interface Cards list on the Local Settings page for the Network Agent instance that you are configuring.
|
|
2.
|
Indicate whether or not to Use this NIC to monitor traffic.
|
|
|
If this NIC will be used for monitoring, click Configure, and continue with step 3.
|
|
3.
|
Use the Local Settings > NIC Configuration > Monitor List page to configure monitoring behavior:
|
|
|
Use the Monitor List to identify which IP addresses (All, None, or Specific) this Network Agent instance monitors.
|
|
|
Under Monitor List Exceptions, add any IP addresses within the monitored ranges that Network Agent should not monitor.
|
|
|
When you are finished making changes, click OK to return to the NIC Configuration page.
|
|
4.
|
Indicate which NIC Network Agent should use as a Blocking NIC. This NIC is also used for communication with other Websense software components, and must have an IP address.
|
|
|
Select Log HTTP requests to improve accuracy in Websense reports.
|
|
|
Select Filter all requests not sent over HTTP ports to use Network Agent to filter only those HTTP requests not sent through the integration product.
|
|
6.
|
Under Protocol Management, indicate whether Network Agent should be used to Filter non-HTTP protocol requests and Measure bandwidth by protocol.
|
|
|
|
|
|
Network Agent Quick Start : Configuring Network Agent
|
