Cisco Cisco Web Security Appliance S170 사용자 가이드

다운로드
페이지 734
 
18-20
Cisco IronPort AsyncOS 7.5.7 for Web User Guide
Chapter 18      URL Filters
Filtering Adult Content
Step 4
Click the Enable Safe Search check box to enable the safe search feature.
Step 5
Choose whether to block users from search engines that are not currently supported by the Web Security 
appliance safe search feature.
Step 6
Click the Enable Site Content Rating check box to enable the site content ratings feature.
Step 7
Choose whether to block all adult content from the supported content ratings websites or to display the 
end-user URL filtering warning page.
Step 8
Submit and commit your changes.
Logging Adult Content Access
By default, the access logs include a safe browsing scanning verdict inside the angled brackets of each 
entry. The safe browsing scanning verdict indicates whether or not either the safe search or site content 
ratings feature was applied to the transaction. You can also add the safe browsing scanning verdict 
variable to the access logs or W3C access logs:
  •
Access logs: %XS
  •
W3C access logs: x-request-rewrite
 describes the safe browsing scanning verdict values. 
For more information on logging, see 
Requests blocked due to either the safe search or site content rating features, use one of the following 
ACL decision tags in the access logs:
  •
BLOCK_SEARCH_UNSAFE
  •
BLOCK_CONTENT_UNSAFE
  •
BLOCK_UNSUPPORTED_SEARCH_APP
Table 18-7
Safe Browsing Scanning Verdict Values 
Value
Description
ensrch
The original client request was unsafe and the safe search feature was applied.
encrt
The original client request was unsafe and the site content ratings feature was applied.
unsupp
The original client request was to an unsupported search engine.
err
The original client request was unsafe, but neither the safe search nor the site content 
ratings feature could be applied due to an error.
-
Neither the safe search nor the site content ratings feature was applied to the client request 
because the features were bypassed (for example, the transaction was allowed in a custom 
URL category) or the request was made from an unsupported application.