Device and client controls

Prev Next

By default, users have full control over their devices—including all client settings.

The administrator can use numerous configuration controls to restrict or define the operation of the user's device and the features that appear in the client.

See Configuring policies to create or change device and client controls.


Device controls

Ringfencing

Ringfencing reduces the security risk of malware transmission between user devices such as laptops on public networks. Ringfence rules can block inbound and/or outbound local traffic except for the traffic required to establish the tunnel to the Gateways.

This is intended for use when a user is on a hostile network such as in a coffee shop or airport terminal. Advanced ringfencing can make the device invisible to other users on the same public network. The tunneled traffic to the Gateways is encrypted and also invisible on public networks. SPA renders the destination invisible to other users. Together, these features allow users to operate in hostile network environments with the highest levels of isolation possible.

If any of the user's device policies contain ringfence rules, traffic in and/or out of the user's machine can be blocked according to the actions set within those rules. As with most firewalls, all rules—including those set by AppGate ZTNA—have a priority. The client tries to set its ringfence rules to the highest possible priority, but locally installed firewall rules can override them. This is a concern on server operating systems, where some rules may be set by the operating system to ensure correct server operation. Ringfencing must not be used to control east-west traffic between servers in a data center. Use third-party tools such as Illumio for east-west traffic control. AppGate ZTNA is designed to protect north-south traffic, and the ringfencing feature is provided on a best-effort basis specifically for protecting devices on untrusted, unprotected, hostile networks.

NOTE

Ringfence rules may restrict some services for users—for example, instant messaging or IP telephony.

Device proxy

Device proxy imposes a PAC file on the device to help manage outbound user traffic not destined for the AppGate ZTNA system. This can be used to filter traffic destined for the internet.

There are three ways to handle user traffic:

  • Split tunneling. The PAC file handles traffic not included in AppGate ZTNA entitlements. Application traffic is handled by AppGate ZTNA; all other traffic is handled by the PAC file rules. This option directs other traffic to destinations outside the AppGate ZTNA system, such as a cloud-based SaaS proxy service. Take care when creating PAC file rules to ensure traffic intended for AppGate ZTNA is not intercepted, because PAC file rules are applied before any AppGate ZTNA routes.

  • Internal proxy. Where a proxy server exists behind an AppGate ZTNA Gateway, the PAC file can be used with an entitlement. In this case, other traffic is directed to an internal proxy behind a Gateway using an entitlement.

  • AppGate ZTNA as default Gateway. AppGate ZTNA can also handle the other traffic. The Site settings Route all traffic through tunnel (Default Gateway) and Alternative default route for all user traffic direct this traffic to a default Gateway on a dedicated Site. Specific AppGate ZTNA entitlements are always applied before the remaining traffic is directed to the default Gateway.

When the device proxy is active, the appgate-driver makes the following registry changes:

HKLM\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\ProxySettingsPerUser = DWORD:0

Tells Windows to use the settings set by the full client.

HKLM\Software\Policies\Microsoft\Internet Explorer\Control Panel\Proxy = DWORD:0

Disables the proxy options in Windows Control Panel so users cannot change proxy settings while the full client runs.

HKLM\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings = BINARY:<blob-including-pac-url-and-flags>

Contains the actual proxy configuration.

See Configuring policies for more details.


Client controls

The device policy includes several configuration options that affect client behavior.

Specific client features can be hidden in the client UI and their values preset by the policy. See the AppGate ZTNA Client Guide for details.

Using the Managed by Admin option lets you constrain the user experience for specific situations. Settings are managed by item—if you select Attention Level only, that option is removed from the user’s UI while everything else remains unchanged.

Client feature options including admin management settings for hiding various functionalities.