Cisco Cisco Web Security Appliance S360 User Guide

Page of 430
 
16-9
Cisco AsyncOS 8.0.6 for Web User Guide
 
Chapter 16      Notify End-Users of Proxy Actions
  Off-Box End-User Notification Pages
The table describes the parameters AsyncOS includes in the query string. 
Note
AsyncOS always includes all parameters in each redirected URL. If no value exists for a particular 
parameter, AsyncOS passes a hyphen (-).
Redirecting End-User Notification Pages to a Custom URL
Step 1
Security Services > End-User Notification
Step 2
Click Edit Settings.
Step 3
Choose Redirect to Custom URL.
Parameter Name
Description
Time
Date and time of the transaction.
ID
Transaction ID.
Client_IP
IP address of the client.
User
Username of the client making the request, if available. 
Site
Hostname of the destination in the HTTP request.
URI
URL path specified in the HTTP request.
Status_Code
HTTP status code for the request.
Decision_Tag
ACL decision tag as defined in the Access log entry that indicates how the DVS 
engine handled the transaction. 
URL_Cat
URL category that the URL filtering engine assigned to the transaction request. 
Note: AsyncOS for Web sends the entire URL category name for both 
predefined and user defined URL categories. It performs URL encoding on the 
category name, so spaces are written as “%20”. 
WBRS
WBRS score that the Web Reputation Filters assigned to the URL in the request.
DVS_Verdict
Malware category that the DVS engine assigns to the transaction. 
DVS_ThreatName
The name of the malware found by the DVS engine.
Reauth_URL
A URL that users can click to authenticate again if the user is blocked from a 
website due to a restrictive URL filtering policy. Use this parameter when the 
“Enable Re-Authentication Prompt If End User Blocked by URL Category or 
User Session Restriction” global authentication setting is enabled and the user is 
blocked from a website due to a blocked URL category.
To use this parameter, make sure the CGI script performs the following steps:
1. Get the value of 
Reauth_Url
 parameter.
2. URL-decode the value.
3. Base64 decode the value and get the actual re-authentication URL.
4. Include the decoded URL on the end-user notification page in some way, 
either as a link or button, along with instructions for users informing them they 
can click the link and enter new authentication credentials that allow greater 
access.