What is the Client Connectivity Policy?

This article explains how you can use the Client Connectivity Policy to ensure devices can only connect to your network when they comply with the organizational security requirements.

Overview

Part of implementing your Zero Trust Network Access (ZTNA) corporate security policy and reducing the attack surface, is to check the posture of devices before they connect to the network. The Client Connectivity Policy lets you create the rules that define the requirements on the device. After a SDP user successfully authenticates, the Cato Client runs checks to verify the relevant conditions on the device. For example, the Client verifies that the anti-malware software is up-to-date, otherwise it doesn't connect to your network.

The Client can identify device conditions based on the following items:

  • Device Posture Profile: This verifies the security posture of the device for the supported Device Checks, see below Defining Device Posture Requirements.

  • Platform: This identifies the operating system of the device. For example, you can require that only Windows devices are allowed to connect.

  • Location: This identifies the physical location of the device. For example, define a list of countries that the Client doesn't connect to the network if the device is located in that county (based on IP geo-location).

Sample Use Case

Company ABC is based in the UK and has a mix of corporate employees and third party contractors. Corporate employees use Windows devices, but the third party contractors use their own devices. To protect the network, the company wants to ensure that only devices with the following conditions are able to connect:

  • The device is located in the UK

  • Devices used by corporate employees have the required device certificate

  • Devices used by third party contractors have anti-malware software, disk encryption and patch management software installed on the device

To ensure devices connecting to its network comply with its security requirements, the company creates the following Client Connectivity Policy Allow rules:

ClientConnectivity_UseCase.png
  • Rule 1 - Corporate employees: On a device used by a corporate employee, the Client checks that the device:

    • Is a Windows device

    • Has the required certificate installed

    • Is located in the UK

  • Rule 2 - Third party contractors: On a device used by a third party contractor, the Client checks that the device:

    • Has Anti-Malware software, disk encryption and patch management software installed

    • Is located in the UK

The Client only connects to the network if it identifies that the device complies with appropriate conditions for the corporate employee or third party contractor.

Controlling Device Access to your Network

The Client Connectivity Policy is an ordered rule base that sequentially checks if the device conditions match the required conditions for the SDP user. Once a device matches a rule, it can connect to your network. Rules that are listed after the matching rule are not applied to the device. If a device does not match any rule, it is blocked by the final implicit rule of the policy (ANY ANY block).

For more information about defining rules for in the Client Connectivity Policy, see Configuring the Client Connectivity Policy.

Defining Device Posture Requirements

To enforce compliance requirements for SDP users, first decide the device posture requirements for user segments in your organization. You can then use the Client Connectivity Policy to implement these requirements.

Each Client Connectivity Policy rule can contain a Device Posture Profile. This lets you define detailed device posture requirements (Device Checks) for devices in your organization. When you include multiple checks in a single profile, they have an AND relationship. For example, you can create a Device Posture Profile that contains Anti-Malware, Firewall and Disk Encryption checks.

You can create different checks per operating system and check for the presence of specific vendors and versions installed on a device. This lets the Client perform granular checks of devices to validate the posture.

Device Checks are supported for Windows and macOS Clients. For more information about the requirements for each check, see Creating Device Posture Profiles and Device Checks.

Defining Additional Compliance Requirements

You can prevent the Client connecting to your network based on the device's operating system and/or the location of the device. Each Client Connectivity Policy rule contains options to include Platforms and Countries. If the Client identifies the device is running a non-compliant operating system or located in a non-compliant location it does not connect to your network.

Was this article helpful?

1 out of 2 found this helpful

0 comments

Add your comment