
S W G U s e r G u i d e
Chapter 21: Implementing Cloud Security
128
4. Configure Cloud Proxies in the
Proxies
(Cloud)
tab, as follows:
a. In the
Server
Side
area, define the following details:
i. In the
Cloud
Proxy
HTTP
Port
field, specify the server‐side HTTP port number on which
all cloud proxies and cloud‐based load balancers will listen, and to which all clients will
connect.
ii. In the
Cloud
Proxy
HTTPS
Port
field, specify the server‐side HTTPS port number on
which all cloud proxies and cloud‐based load balancers will listen, and to which all clients
will connect.
b. In the
Client
Side
area, do the following:
i. In the
Local
Control
Port
field, specify the port to which the client uses to perform
“control” activities, such as configuration updates.
Note
: It is recommended that you not
change the port value from the default unless you use the default for a different
application.
ii. In the
Client
Side
table under the Local Control Port field, for each Cloud Scanner or Load
Balancer that the client can use, define the identifying details, as follows:
a) Click the
icon.
b) In the
Comment
field, specify an internal label for this scanner/load balancer, for
example a suggested name could include the scanner type, and/or the scanner’s
location.
c) In the
Address
field, specify the IP Address or Hostname of the scanner/load
balancer.
d) In the
Local
Client
HTTP
Port
field, specify the client‐side port number used to
uniquely identify a specific cloud proxy or cloud‐based load balancer for HTTP.
e) In the
Local
Client
HTTPS
Port
field, specify the client‐side port number used to
uniquely identify a specific cloud proxy or cloud‐based load balancer for HTTPS.
5. Configure On‐premise Proxies and On‐premise/Off‐premise indicators in the
Proxies
(On
premise)
tab, as follows:
a. In the
On
premise
Proxy
Details
area, for each explicit proxy server to which roaming users
can connect while on premise, configure the details as follows:
i. Click the
icon.
ii. In the
Address
field, specify the IP or Hostname of the on‐premise proxy server.
iii. In the
Cloud
Proxy
HTTP
Port
field, HTTP port to which roaming users will connect
when on‐premise.
iv. In the
Cloud
Proxy
HTTPS
Port
field, HTTPS port to which roaming users will connect
when on‐premise.
b. In the
On
Premise.Off
Premise
Indicator
area, do the following:
i. In the
Corporate
Hostname
field specify the corporate address (for example,
www.M86security.com). When the user is within the corporate network, this name must
be resolvable to the Internal Hostname IP which is specified in the next sub‐step. When
the user is outside the corporate network, this name should not be resolvable to the
Internal Hostname IP.
ii. In the
Internal
Hostname
IP
field specify the IP of the corporate hostname, using either
of the following methods:
• Click the
Resolve
IP
button. The application will look up the IP address of the internal
NOTE:
Be
sure
not
to
confuse
the
Local
Client
ports
and
Listening
Server
ports.