Step 3 Use the url-filter good-sites-allow command to point to the goodurl.lst file. Step 2 Copy the goodurl.lst file to the /local1 sysfs directory of the Content Engine. The list of URLs in the goodurl.lst file must be written in the form and delimited with carriage returns. In this file, enter the URLs that you want to exclusively allow. Step 1 Create a plain text file named goodurl.lst. To permit specific URLs to the exclusion of all other URLs, do the following: Console(config)# url-filter enable bad-list Step 4 Use the url-filter bad-list enable command to actively deny the URLs. Console(config)# url-filter bad-sites-deny local/local1/badurl.lst Step 3 Use the url-filter bad-sites-deny command to point to the bad URL list. Note We recommend creating a separate directory under local1 to hold the bad and good lists, for Step 2 Copy the badurl.lst file to the /local1 system file system (sysfs) directory of the Content Engine. The list of URLs in the badurl.lst file must be written in the form and delimited with carriage returns. In this file, enter the URLs that you want to block. Step 1 Create a plain text file named badurl.lst. To deny requests for specific URLs, do the following: You can configure the Content Engine to deny client requests for URLs that are listed in a badurl.lst file, or configure it to fulfill only requests for URLs in a goodurl.lst file. The url-filter command takes precedence over the rule command to the extent that even the rule no-block command is executed only if the url-filter command has not blocked the request. List filenames and the customized blocking message directory name are now specified in theĬommand-line interface you can now use the url-filter local-list-reload EXEC command toĭynamically refresh a local URL list and bad-sites-block has been changed to bad-sites-deny.
#Configure content websense filter nsa 220 software
Note The URL filtering feature in ACNS 4.1 software differs from the URL feature in other releases asįollows: There is now an enable command option for the good-sites and bad-sites options the URL Only one form of URL filtering can be active at a time. Filter traffic with Secure Computing Corporation SmartFilter ™ Software, Release 3.0.2 for Cisco Content Engine ACNS Software, Release 4.1.x.
Direct traffic to a Websense enterprise server for filtering.Direct traffic to a N2H2 server for filtering.Permit access only to URLs specified in a list.Deny access to URLs specified in a list.The URL filtering features presented in this chapter allow the Content Engine to control client access to websites in any of the following ways: By having a URL filtering scheme on the Content Engines, organizations realize an immediate return on investment as a result of increased productivity and recaptured network bandwidth, while reducing legal liability. Employees or students can be allowed or denied access to websites, or can be coached with information about acceptable use of the Internet. Some enterprises have a requirement to monitor, manage, and restrict employee access to nonbusiness and objectionable content on the Internet.
URL Filtering with the Websense Enterprise Server N2H2 Configuration Through the Content Engine GUI Table of Contents Configuring URL Filtering
0 kommentar(er)
