Cisco Secure Access Help

PDF

Cisco Secure Access Help

Manage Endpoint Security

Want to summarize with AI?

Log in

Describes Manage Endpoint Security in Cisco Secure Access. Secure Access is a converged cloud security solution that enables fast, reliable, and secure private network connections to your applications.


Secure Access is a converged cloud security solution that enables fast, reliable, and secure private network connections to your applications. End users are assured of a secure, transparent user experience, anywhere they work — office, home, or on the road. User devices can read, write, and update private resources by setting up virtual private networks (VPNs) or zero trust network access (ZTNA) connections to Secure Access through IPsec network tunnels.

About Endpoint Posture

Posture is a service in Secure Access that allows you to check the state, also known as posture, of all the endpoints that are connecting to a network for compliance with corporate security policies. This allows you to control user access to protected areas of a network. See View a Endpoint Posture.

About Posture Profiles

Posture profiles define requirements for end-user devices when accessing the network and private resources. There are two types of profiles, depending on your connection type:

  • VPN - Define posture requirements for end-user devices connecting to the network using VPN. The VPN client must be installed on the end-user device. Requirements are checked when the device connects to the network. See Manage VPN Connection Posture Profiles.
  • Zero Trust Access - Define posture profiles for user devices that connect to resources on the network without using VPN. See Manage Zero Trust Access Posture Profiles.

Endpoint Posture Assessment

Endpoint posture assessment involves orchestrating and performing data collection and evaluating the posture of a given endpoint.

Typically, endpoint posture information is gathered and then published to appropriate data repositories to make collected information available for further analysis supporting organizational security processes.

Endpoint posture assessment typically includes:

  • Collecting the attributes of a given endpoint;
  • Making the attributes available for evaluation and action; and
  • Verifying that the endpoint's posture is in compliance with enterprise standards and policy.

Endpoint Attributes

Cisco Secure Access can evaluate certain attributes and conditions on end-user devices. This guide describes the endpoint attributes evaluated by Secure Access.


Supported Operating Systems

This option checks for the existence of any required operating systems that are needed on the endpoint device.

The operating system hosts and manages your data, applications, and connected devices. Inadequate protections for the operating system could also affect the performance of all of these components and ultimately affect productivity of your users and the organization.

The following sections describe the supported operating systems and package dependencies for Secure Access posture profiles.

Zero Trust Connections

  • Windows
  • Mac OS X
  • Linux
  • iOS
  • Android (version 14 or later)
  • Chrome Enterprise Premium
  • Edge for Business

VPN Connections

  • Windows
  • Mac OS X
  • Linux

Inadequate protections for the operating system could also affect the performance of all of these components and ultimately affect productivity of your users and the organization.


Firewall Conditions

This option checks for the existence of a firewall on the endpoint device.

  • Windows
    • Require the platform-native firewall to be running on the endpoint device.
  • Mac OS X
    • Require the platform-native firewall to be running on the endpoint device.

Endpoint Security Agents

This option checks for the existence of an endpoint security agent required to be running on the endpoint device. The Endpoint Security Agent is a modern solution that delivers comprehensive, multilayered protection to safeguard your device against diverse threats. Its unified architecture allows you to deploy multiple solutions through a single agent for streamlined management and enhanced security.


System Password Enforcement

This option checks whether a system password is required on the endpoint device.


Disk Encryption

This option checks for the existence of disk encryption running on the endpoint device.

Disk encryption ensures that files are always stored on disk in an encrypted form. The files become available to the operating system and applications in readable form while the system is running and unlocked by a trusted user. An unauthorized user inspecting the contents of the disk directly finds garbled random-looking data instead of the actual files.

With user data encryption enabled, the /home directory in the file system is encrypted and user data is available when the system is running. The user /home partition is mounted on a separate disk partition and block level encryption is enabled for that disk.

Note
By default, the disk encryption check only detects for the presence of the disk encryption software but does not require that particular disk drives are encrypted. On a Windows platform, it is possible to require that the default C:\ drive is encrypted. For more information, see Welcome to Cisco Secure Access.

Supported Browsers

This option checks for the existence of a required web browser on the endpoint device.


Windows Registry Conditions

This option checks for the existence of a registry key or the value of the registry key on the endpoint device. The posture check for this partcular field only requires the path to the directory containing the registry and should not include the registry name.


Windows Domain Join

This option enforces a check to verify if the device has joined a Windows domain. You have the option to also specific a specific SID to ensure a device is joined to a specific Domain.

At this time Secure Access supports both Azure AD and Microsoft Entra. Events generated from successful or failed domain joins and snapshots of detailed posture checks are avilable in the Activity Search Report. By using the Azure AD you can reduce the risk of devices joined to unapproved domains. Add and managed your domains within your posture profile; see step 9 of Add a Client-Based Zero Trust Access Posture Profile.


File Conditions

This option checks for the existence of a file, the date of a file, and the versions of a file on the endpoint device.

Note
File conditions are checked against case-sensitive checksum protocols.

Process Conditions

This option checks if an application or process is running or not running on the endpoint device.

Note
You must include the full name of a process along with its extension to ensure the proper functionality of the Process Conditions option. For example, instead of 'Firefox,' use 'Firefox.exe.'

Certificate Conditions

Secure Access supports certificate and Security Assertion Markup Language (SAML) authentication for remote access VPN connection profiles. This option checks if any required server certificates are present and valid on the endpoint device.

Prerequisites

  • You must enable the certificates for authentication when end-users connect on a VPN. For more information, see Add VPN Profiles.

About Certificate Conditions

Note
Secure Access also supports certificate and RADIUS authentication for remote access VPN connection profiles.

A user on VPN is authenticated with both a client certificate and SAML server. The client certificates are installed on every users' device and are validated by CA certificate(s) to verify identity. SAML is an open standard that allows identity providers (IdP) to pass authorization credentials to service providers. When a user logs into a SAML-enabled application, the service provider requests authorization from the appropriate IdP. The identity provider authenticates the user's credentials and returns the authorization to the service provider. Once authorized, the user can use the application. In the case of certificate and SAML authentication, certificates are authenticated before SAML authentication.

When selected, you can configure up to two certificates to authenticate each endpoint. For each certificate, configure the following attributes:

  • Subject — The subject field identifies the entity that owns or is associated with the public key embedded in the certificate. It often corresponds to the hostname or domain name the VPN server uses.

    Note
    The subject field is important because it ensures that VPN clients can verify the identity of the server they are connecting to by checking the certificate's subject against the expected hostname. The Common Name (CN) within the subject field is often used to identify the primary hostname of the server.
  • Issuer — The issuer field is the entity (trusted authority) that issues the digital certificates used for authentication and secure communication within a VPN. These certificates verify the identity of the VPN server and clients, ensuring secure access to the network.

  • Subject alternate name — The subject alternative name field allows a single certificate to cover multiple hostnames or IP addresses, ensuring secure connections when a VPN client connects to a server with different names or addresses.

You select the Type to check when validating the endpoint certificate. You can manually enter a Value, or you can select SAML attribute name from the Type drop-down to use the values provided by the SAML identity provider (IdP) that is integrated with Secure Access.


View a Endpoint Posture

To view the Endpoint Posture profile requirements defined for end-user devices when accessing the network and private resources.

Note
Each requirement is optional; and requirements can be configured in any order. However, endpoints must meet all conditions of any configured requirement.

Before you begin

  • You must have the full Admin user role. For more information, see Manage Accounts.

Procedure

  1. Navigate to Secure > Profiles > Endpoint Posture Profiles.


    Endpoint Posture Profiles page with option for adding endpoint posture profile
  2. For Zero Trust Connection, click Posture Profile Name to view the browser based integration details.

    • Applied Criteria— The applied criteria for the browser based integration.

    • Applied Rules—The applied rules for the browser based integration.

  3. Click Edit.