The site from which the response was received is checked against the Pass Sites list.When evaluating HTTP responses, Web Monitor applies the configured rules and lists in the following order: If the category could not be determined, the traffic is allowed. The category determined in step #1 is compared to the Categories list, and the traffic is allowed and possibly flagged based on the corresponding match.If a match is found, the traffic is allowed and possibly flagged based on the options configured in the rule that was matched. The traffic details are passed to the Rules list.If a match is found, the traffic is flagged. The destination site of the request is checked against the Flag Sites list.If a match is found, the traffic is allowed. The destination site of the request is checked against the Pass Sites list.The source IP of the request is checked against the Pass Clients list.The category is attached to the session for use by Web Monitor as well as other applications. A lookup is performed to determine the category for the requested site.When evaluating HTTP requests, Web Monitor applies the configured rules and lists in the following order: This allows a high degree of monitoring over both resources that are requested, and content that is returned in response. The second is after the response is received from the server and before it is passed back to the client. The first evaluation happens after the request is received from the client and before it is forwarded to the server. When scanning traffic, Web Monitor evaluates the pass lists, flag lists, categories, and rules at two distinct points of the HTTP transaction. The abundance of categories means that you can narrow your scope - maybe you want to flag websites related to nudity, but allow sites dealing with Sexual Education. The Web Monitor database is over 100 times larger and more accurate. Detailed categorization: Web Monitor offers 79 categories and tens of billions of URLs. More information on how this is down below. HTTPS traffic is encrypted so only some information is visible and this information is used to categorize the session. HTTPS Filtering: Web Monitor has multiple techniques to deal with HTTPS, SSL-encrypted HTTP. Because this is done dynamically, new sites and updated URLs are allowed or flagged according to your settings without additional intervention, plus you have the option of requesting recategorization of sites. If a site is not categorized upon request, it is autocategorized by our partners at Webroot and put into a queue to be verified by a human. This data is then used to flag or allow users access to the site they have requested, all without any appreciable increase in load time. When the data is returned, NG Firewall keeps a temporary local cache of the site and category to speed up the process the next time the URL is requested. Real-time classification and updates: When your users visit a site, NG Firewall sends the URL to the Webroot BrightCloud® to be categorized.Web Monitor monitors HTTP and HTTPS traffic on your network to log web activities and flag inappropriate content. 5.2 Can I block sites with Web Monitor?.5.1 Why is there a pass list if Web Monitor can't block sites?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |