Last Modified: Apr 10, 2019
Opened: Sep 24, 2015
One example is that Response Analytics classifies 'http://testdatabasewebsense.com/violence/' as /Common/Information_Technology. This is because since this is a test page, there is nothing actually violent in the payload, so when it is examined by Response Analytics it gets classified not as "Violence" but as "IT". Category Lookup suggested violence because of the URL, but Response Analytics overwrites this suggestion with what is technically correct: information technology.
Wrongly categorized websites may be allowed through.
This is a fairly unlikely event; the Category Lookup would have to suggest something completely different from what the Response Analytics suggests. In the off chance that Category Lookup is more accurate than Response Analytics, this issue would occur.
A URL Filter agent can be placed after the Category Lookup agent and before the Response Analytics agent. This makes sure that if Category Lookup thinks something should be blocked, it is blocked, and never even goes to the Response Analytics to be further classified.