Cisco Cisco Web Security Appliance S160 Guía Del Usuario
8-16
AsyncOS 8.5 for Cisco Web Security Appliances User Guide
Chapter 8 Classify URLs for Policy Application
Filtering Adult Content
Step 8
Submit and Commit Changes.
Related Topics
•
.
•
Controlling Access to Web Applications, page 17-18
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:
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
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:
ACL decision tags in the access logs:
•
BLOCK_SEARCH_UNSAFE
•
BLOCK_CONTENT_UNSAFE
•
BLOCK_UNSUPPORTED_SEARCH_APP
•
BLOCK_CONTINUE_CONTENT_UNSAFE
Related Topics
•
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.
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.
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.