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

In the case of transparent HTTPS, AsyncOS does not have access to information in the client headers. 
Therefore, AsyncOS cannot enforce routing policies that rely on information in client headers. For 
example, for transparent HTTPS transactions, AsyncOS does not have access to the username in the 
HTTPS client header and therefore it cannot match a routing policy based on username. In this case, 
AsyncOS uses the default routing policy.

In the case of explicit HTTPS, AsyncOS has access to the following information in client headers:

URL

Destination port number

Therefore, for explicit HTTPS transactions, it is possible to match a routing policy based on URL or port 
number. 

You can integrate the Cloud Connector with external Data Loss Prevention servers through 
Network>External DLP Servers. 

The Cloud Connector Logs provides useful information for troubleshooting problems with the Cloud 
Connector, for example, authenticated users and groups, the Cloud header, and the authorization key. 

Navigate to System Administration>Log Subscriptions.

Select Cloud Connector Logs from the Log Type menu.

Type a name in the Log Name field.

Set the log level.

Submit and Commit your changes.

Go to whoami.scansafe.net to view the configured group names, user names, and IP addresses.