System settings include settings that are configured when initially setting up a Secure Web Gateway appliance and others that are configured after this setup. For reference information about these settings, see Secure Web Gateway System Settings.
Initial system settings
System settings configured at the initial setup of a Secure Web Gateway appliance include the primary network interface, host name, root password, and others. For more information about this setup, see Secure Web Gateway Installation.
After the initial setup you can configure more system settings and also modify the initial settings.
System settings are configured to control the behavior of the appliance system. They include the settings that were configured at the initial setup and others, for example, settings for domain name services or port forwarding.
Among these settings, the following play an important part:
- Network interfaces — Network interfaces are configured to enable processing of web traffic on a Web Gateway appliance. When completing this configuration, you specify the host name, gateways, use of the IPv4 or IPv6 protocol, and other parameters. Some of these settings are already configured during the initial setup.
- Proxies — Web Gateway can be configured to run as a proxy that intercepts web traffic and transmits it if this is allowed by the rules of your web security policy.
Proxies can be configured in different ways regarding;
- Network mode — The network mode can be an explicit (also known as direct) proxy mode or a transparent mode.
- Network protocol — The network protocol can be, for example, HTTP, HTTPS, FTP, ICAP, or IFP, to enable the filtering of web traffic that is going on under any of these protocols.
For more information, see Secure Web Gateway Proxy Configuration.
- Cluster nodes — Instead of running a Web Gateway appliance in a standalone mode, you can run multiple appliances as nodes in a cluster.
To configure a cluster with several appliances as nodes, use the Central Management system settings. For more information, see Secure Web Gateway Cluster Configuration.