Cisco Cisco Web Security Appliance S380 User Guide
3-11
AsyncOS 8.1 for Cisco Web Security User Guide
Chapter 3 Connect the Appliance to a Cloud Web Security Tower
Bypassing the Cloud Proxy Server
Step 3
Select the groups for which you have created Cloud Policies within Cisco Cloud Web Security.
Step 4
Click Add.
Step 5
Click Done and Commit your changes.
Related information
•
Bypassing the Cloud Proxy Server
Cloud routing policies allow you to route web traffic to either Cisco Cloud Web Security towers or
directly to the Internet based on these characteristics:
directly to the Internet based on these characteristics:
•
Identity
•
Proxy Port
•
Subnet
•
URL Category
•
User Agent
The process of creating cloud routing policies in Cloud Connector mode is identical to the process of
creating routing policies using the standard mode.
creating routing policies using the standard mode.
Related topics
•
FTP and HTTPS
The Web Security appliance in Cloud Connector mode does not fully support FTP or HTTPS.
•
•
FTP
FTP is not supported by the Cloud Connector. AsyncOS drops native FTP traffic when the appliance is
configured for Cloud Connector.
configured for Cloud Connector.
FTP over HTTP is supported in Cloud Connector mode.
HTTPS
The Cloud Connector does not support decryption. It passes through HTTPS traffic without decrypting.
Because the Cloud Connector does not support decryption, AsyncOS generally does not have access to
information in the client headers of HTTPS traffic. Therefore, AsyncOS generally cannot enforce
routing policies that rely on information in encrypted headers. This is always the case for transparent
information in the client headers of HTTPS traffic. Therefore, AsyncOS generally cannot enforce
routing policies that rely on information in encrypted headers. This is always the case for transparent