Cisco Cisco Web Security Appliance S360 Guía Del Usuario

Descargar
Página de 486
 
3-3
AsyncOS 10.0 for Cisco Web Security Appliances User Guide
 
Chapter 3      Connect the Appliance to a Cisco Cloud Web Security Proxy
  Configuring the Cloud Connector
Step 6
Select Cloud Web Security Connector for the appliance mode. 
Step 7
Configure Cloud Connector settings: 
Step 8
Configure network interfaces and wiring: 
Step 9
Configure routes for Management and Data traffic: 
Step 10
Configure transparent connection settings: 
Note
By default, the Cloud Connector is deployed in transparent mode. which requires a connection 
to a Layer-4 switch or a version 2 WCCP router
Setting
Description
Cloud Web Security Proxy Servers
The address of the Cloud Proxy Server (CPS), for example, 
proxy1743.scansafe.net.
Failure Handling
If AsyncOS fails to connect to a Cloud Web Security proxy, 
either Connect directly to the Internet or Drop requests.
Cloud Web Security Authorization 
Scheme
Method for authorizing transactions: 
Web Security Appliance public facing IPv4 address
Authorization key included with each transaction. You can 
generate an authorization key within the Cisco Cloud Web 
Security Portal.
Setting
Description
Ethernet Port
If you configure the M1 interface for management traffic only, you must configure 
the P1 interface for data traffic. However, you can configure the P1 interface even 
when the M1 interface is used for both management and data traffic.
IP Address
The IPv4 address to use to manage the Web Security appliance.
Network Mask
The network mask to use when managing the Web Security appliance on this 
network interface.
Hostname
The hostname to use when managing the Web Security appliance on this 
network interface.
Setting
Description
Default Gateway
The default gateway IPv4 address to use for the traffic through the Management 
and/or Data interface.
Name
A name used to identify the static route.
Internal Network
The IPv4 address for this route’s destination on the network.
Internal  Gateway
The gateway IPv4 address for this route. A route gateway must reside on the same 
subnet as the Management or Data interface on which it is configured.