Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 1224
 
16-3
Cisco AsyncOS 9.5 for Email User Guide
 
Chapter 16      Protecting Against Malicious or Undesirable URLs
  Setting Up URL Filtering
Before You Begin 
Ensure that the requirements for the individual URL filtering features that you want to use have been 
met. See 
(Optional) Create a list of URLs that you want all URL filtering functionalities to ignore. See 
Procedure 
Step 1
Select Security Services > URL Filtering
Step 2
Click Enable
Step 3
Select the Enable URL Category and Reputation Filters check box. 
Step 4
(Optional) If you have created a list of URLs to exempt from URL filtering when evaluating messages 
for spam and malware, and from all content and message filtering, select that list. 
This setting does not cause the message to bypass anti-spam or Outbreak Filters processing generally. 
Step 5
(Optional) Enable Web Interaction Tracking. See 
.
Step 6
Submit and commit your changes. 
If you have met the applicable prerequisites, and you have already configured Outbreak Filters and 
Anti-Spam protection, then you do not need to make additional configurations to benefit from enhanced 
automatic detection of spam and malicious URLs. 
What To Do Next 
To take action based on the reputation of URLs in messages, see 
To use URL categories in content and message filters, for example to enforce acceptable use 
policies, see 
To redirect all URLs in suspected spam messages to the Cisco Web Security proxy service, see 
(Optional) To customize the appearance of end user notification page, see 
.
Ensure that you receive alerts about issues related to this feature. See 
, the release notes for your AsyncOS release, and 
About the Connection to Cisco Web Security Services 
URL reputation and category are provided by cloud-based Cisco Web Security Services.
The Email Security appliance connects to the Cisco Web Security Services either directly or through a 
web proxy, using the port specified for URL filtering services in 
Communication is over HTTPS with mutual certificate authentication. Certificates are updated 
automatically (see 
.) For additional information about required certificates, 
see the Release Notes available from the location specified in