Conditional Access Template

This template creates a configuration that checks if the remote device is compliant for accessing backend servers. It can be found in the COMPLIANT BACKEND ACCESS category when filtered for REMOTE platform.

If the remote device is not compliant for accessing backend servers, you can choose between two actions:

• Denies access to the session if the remote device is not compliant or corporate managed.
• Displays a message in the session if the remote device is not compliant or corporate managed.

deviceTRUST requires some simple but essential configuration steps to be performed to enable the template for your remoting and DaaS environments. We will guide you step-by-step through simple deviceTRUST configuration steps to enable the template within your remoting or DaaS environment.

We will perform the following steps:

1. Step 1: Prerequisites
2. Step 2: Contexts
3. Step 3: Actions

Step 1: Prerequisites

If the required deviceTRUST components (Agent, Console, Client Extension and License) are not yet installed, please visit the Getting Started for Remote guide and complete step 1 to 5 and then continue here with step 2 below.

Step 2: Contexts

The template has imported the following contexts:

Context	Description	Customizations
Corporate Device	Defines if the remote device is a corporate managed device.	You must update the following context condition with data suitable for your environment: REMOTE - DOMAIN ID Any Of 2 ITEMS When using AD or Microsoft Entra ID domain joined devices, replace DOMAIN_SID and AZURE_TENANT_ID with your corporate values. Example: S-1-5-21-1397108472-4176295369-1616608269 for a domain SID. REMOTE - HARDWARE BIOS SERIAL NUMBER Any Of 3 ITEMS When identifying physical devices, replace BIOS_SERIAL_NUMBER_X with BIOS serial numbers of your corporate devices. Example: PF1J8T36 REMOTE - IGEL UMS SERVER Equals UMS_SERVER_IP:30001 When using IGEL OS devices, replace UMS_SERVER_IP:30001 with the IP address of your IGEL UMS Server. Example: 192.168.0.22:30001 REMOTE - IGEL UMS CERT THUMPRINT SHA256 Equals UMS_CERTIFICATE_THUMBPRINT_SHA256 When using IGEL OS devices, replace UMS_CERTIFICATE_THUMBPRINT_SHA256 with your IGEL UMS Server certificate thumprint. Example: 0d57fdd21474ef7806818a661a5f1d1cb3361a8bb4ccd660dae6930a6a135a56 REMOTE - ELUX SCOUT NAME Equals SCOUT_NAME When using eLux devices, replace SCOUT_NAME with the name of your eLux Scout Server. Example: DTLDES01 REMOTE - ELUX SCOUT CERT THUMPRINT SHA256 Equals SCOUT_CERTIFICATE_THUMBPRINT_SHA256 When using eLux devices, replace SCOUT_CERTIFICATE_THUMBPRINT_SHA256 with your eLux Scout Server certificate thumprint. Example: 0d57fdd21474ef7806818a661a5f1d1cb3361a8bb4ccd660dae6930a6a135a56
Country	Defines the country in which the remote device is located.	None
Country Provider	Defines the country provider that reports the country of the remote device.	None
Device Type	Defines the remote device device type.	None
deviceTRUST Client	Defines the availability of the deviceTRUST Client Extension on the remote device.	None
Override	Defines if the session user is member of the override AD group.	You can add one or more user groups from your Microsoft Active Directory (AD) to exclude group members from actions.
Remote Controlled	Defines if the remote device is remote controlled.	None
Security State	Defines the security status of the remote device.	You must update the following context condition with data suitable for your environment: REMOTE - IGEL UMS SERVER Equals UMS_SERVER_IP:30001 When using IGEL OS devices, replace UMS_SERVER_IP:30001 with the IP address of your IGEL UMS Server. Example: 192.168.0.22:30001 REMOTE - IGEL UMS CERT THUMPRINT SHA256 Equals UMS_CERTIFICATE_THUMBPRINT_SHA256 When using IGEL OS devices, replace UMS_CERTIFICATE_THUMBPRINT_SHA256 with your IGEL UMS Server certificate thumprint. Example: 0d57fdd21474ef7806818a661a5f1d1cb3361a8bb4ccd660dae6930a6a135a56 REMOTE - ELUX SCOUT NAME Equals SCOUT_NAME When using eLux devices, replace SCOUT_NAME with the name of your eLux Scout Server. Example: DTLDES01 REMOTE - ELUX SCOUT CERT THUMPRINT SHA256 Equals SCOUT_CERTIFICATE_THUMBPRINT_SHA256 When using eLux devices, replace SCOUT_CERTIFICATE_THUMBPRINT_SHA256 with your eLux Scout Server certificate thumprint. Example: 0d57fdd21474ef7806818a661a5f1d1cb3361a8bb4ccd660dae6930a6a135a56
Virtualized	Defines if the remote device is virtualized.	None
Wi-Fi Security Mode	Defines if the remote device is connected to a secure Wi-Fi network.	None

Step 3: Actions

The template includes a notifying action that displays a message to the user about a context status and an enforcement action that actively controls access to the session. By default, only the notifying action is enabled and the enforcement action is disabled.

Action	Description	Default State	Customizations
Compliance Check - Conditional Access - Enforcement	Denies access to the session if the remote device is not compliant or corporate managed.	Deactivated	You must update the following context condition with data suitable for your environment: COUNTRY None Of AUTHORIZED_COUNTRY_1,… Replace AUTHORIZED_COUNTRY_X with your authorized countries using the ISO 3166-1 Alpha-2 code. Example: US
Compliance Check - Conditional Access - Notification	Displays a message in the session if the remote device is not compliant or corporate managed.	Activated	You must update the following context condition with data suitable for your environment: COUNTRY None Of AUTHORIZED_COUNTRY_1,… Replace AUTHORIZED_COUNTRY_X with your authorized countries using the ISO 3166-1 Alpha-2 code. Example: US

Troubleshooting

If your deviceTRUST installation or configuration does not work as expected, you can use the Troubleshooting guide to start troubleshooting.