Configuration options for the Windows agent type
- Identification & Privacy
- Bypass Categories
- Network Detection
The Agent Configuration screen allows you to create or modify agent profiles for Windows agents. Selecting a Windows agent profile from the list will allow you to configure the profile.
To see the different Agent Configuration profiles attached to your account, visit your USS Dashboard and click Products ⟶ Web Security ⟶ Agent Configuration.
Profile name / Tray icon tooltip
A friendly name for the profile to make it easier to manage. The name is also displayed in the tooltip for the agent icon.
The tamper-proof password which secures the configuration and start/stop options on the agent. This password is automatically generated when the profile is created but can be changed.
Tag web requests with
The Tag to assign to this agent. Tags are used to identify the agent in Filter Rules. Select a tag to use, or choose
No Selection if a tag is not required.
Preferred outbound ports
The agent will connect to the Web Security cloud service on ports
443. Select the preferred ports here and they will be tried first. If a connection is not established, the agent will try the remaining ports.
Hot Spot mode (Fail Open)
If enabled, the agent will provide unfiltered access if for any reason the Web Security cloud service ports are inaccessible. If not enabled, web access will be blocked until the cloud service becomes available again.
Check for new updates automatically
If enabled, the agent will poll for new software updates.
Install new updates when they are available
If enabled, the agent will install new software updates as soon as they are available.
Identification & Privacy
The Identification & Privacy section allows you to control what information to log about your users and their devices.
Enables the capture of Active Directory or local user credentials. This captures the Active Directory domain and username if the user has logged into a Windows domain, or falls back to capturing the local username if this is not possible.
Use hostname as username
Use the device's hostname instead of the captured username. Useful for deployments where no user identification mechanism is provided, or for device-based policy control.
Log device MAC address
Enable capture of the device MAC address for the primary network interface.
Log device IP address
Enable capture of the device IP address for the primary network interface.
The Bypass Categories section contains a list of available categories, created in the Bypass section of the Web Security product. Bypass categories provide a way for the agents to trust particular network resources, so that matching traffic does not get filtered by the Web Security cloud service. A number of pre-defined categories are provided as a starting point for common services.
(System)appended to their name.
The Network Detection feature provides added flexibility when using a combination of the gateway and agent software on the same network. Using Network Detection, you can automatically disable Windows agents when the agent detects a new connection to a recognised network.
For example, you might have a gateway agent deployed at your Head Office, along with a number of remote workers each running a Windows agent. If a remote worker visits Head Office with their Windows device, you could instruct that their filtering is handled by the gateway rather than the local Windows agent.
If the agent detects a "known" network, the system tray icon will change to an orange icon, and an alert will be displayed.
Hostname(s) to detect
Use the [IMAGE add button] to add a hostname. The Windows agent will then monitor for that hostname. If the Expected IP is set to 0.0.0.0/0 then the agent state will change as long as the hostname can be resolved to an IP. If you want to only change state if a specific IP is resolved (recommended), specify the IP in CIDR format.
Choose what should happen to the Windows agent if a recognised network is detected (either disable or enable the agent).
Do not disable if agent gateway IP matches
In certain scenarios you may not want to automatically disable the agent if the device default gateway matches a certain IP (for example, the IP of a VPN router). Check this box, and add the IP address exceptions to the list underneath.
Use strict SSL/TLS ciphers
If enabled, the agent will reject connections to Web servers that are configured to use old, deprecated or insecure ciphers (such as rc4 and rc4-md5). This may cause third-party services to stop working. Generally, a web browser will always try and negotiate at the highest possible cipher level supported by the web server.
Block QUIC protocol
The QUIC protocol is developed by Google, and is used by many of their services, such as Google Search and GSuite (when accessed via the Google Chrome browser). As
QUIC is a variation of
HTTP/S over UDP, it can bypass filtering. Enabling this option ensures the protocol is blocked, and therefore the services fall back to using
HTTP/S over TCP and can be filtered appropriately.
Intercept all running processes
The agent has the capability to intercept HTTP/S traffic from any running process, but by default this is limited to set of known browser-based applications (listed below). Enabling this option allows interception of any application.
Known browser-based applications intercepted by default
- Internet Explorer
- Google Earth
The service hostname is determined by the region chosen for the Web Security service, and cannot be changed directly.
Update repository (URL)
The URL to check for new software updates. If your service provider has directed you to change this or if you wish to try pre-release versions, the following alternative URLs are available:
- Windows agent beta releases:
- Windows agent release candidates:
- Windows agent stable releases:
Check for updates every
Specify the frequency with which to check for new software updates.
This can be used to create a custom list of applications for the agent to intercept, and should be used with the Intercept all running processes option detailed above. A version of the
json file should be hosted on a public web server and must follow the same format as the original.
An internal ID of the agent profile which may be requested by the Service Provider during a troubleshooting session. This ID cannot be changed.