Руководство Пользователя для Cisco Cisco Email Security Appliance C170

Скачать
Страница из 1197
 
16-14
User Guide for AsyncOS 9.7 for Cisco Email Security Appliances
 
Chapter 16      Protecting Against Malicious or Undesirable URLs
  Troubleshooting URL Filtering
Using the websecurityadvancedconfig Command 
Except for changes explicitly described in this document, make no other changes using the 
websecurityadvancedconfig
 command without guidance from TAC. 
Message Tracking Search Does Not Find Messages with Specified Category 
Problem
Messages that contain URLs in a particular category are not found when searching by that 
category. 
Solution
See 
Malicious URLs and Marketing Messages Are Not Caught by Anti-Spam or 
Outbreak Filters 
Problem
Malicious URLs and messages containing marketing links are not caught by the anti-spam or 
outbreak filters. 
Solution
This can occur because web site reputation and category are only two among many criteria that 
anti-spam and outbreak filters use to determine their verdicts. You can increase the sensitivity of 
these filters by lowering the thresholds required to take action such as rewriting or replacing URLs 
with text, or quarantining or dropping messages. For details, see 
 and 
. Alternatively, create content 
or message filters based on URL reputation score. 
This can also occur if the Email Security appliance is unable to connect to the Cisco Web Security 
Services. See 
URLs in a Filtered Category Are Not Handled Correctly 
Problem
The defined action in a content or message filter based on URL category is not applied. 
Solution
Use the Trace feature (described in the Troubleshooting chapter) to follow the message processing 
path. 
This can occur if the Email Security appliance is unable to connect to the Cisco Web Security 
Services. See 
If there are no connection issues, the URLs may not yet be categorized, or may be miscategorized. 
See 
. You can use this site to 
determine the category of a URL. 
End User Reaches Malicious Site via Rewritten URL 
Problem
A malicious URL was redirected to the Cisco Web Security Proxy, but the end user was able to 
access the site anyway. 
Solution
This can occur if: