Scenario 2

This scenario covers how to enable App Protection for untrusted devices.

There are many definitions for trusted and untrusted devices. For this scenario, let’s consider a device trusted if the Endpoint analysis (EPA) scan is successful. All other devices are considered untrusted devices.

  1. Configure Adaptive Authentication.
  2. Create an Authentication policy with the EPA scan using the following steps:

    1. Sign in to Citrix ADC Administration UI. In the Configuration tab, navigate to Security > AAA-Application Traffic > Virtual Servers. Click the virtual server that you want to use, auth_vs in this case.

      Virtual servers

    2. Navigate to Authentication Policies > Add Binding.

      Authentication policies

      Add binding

    3. Click Add to create a policy.

      Policy binding

    4. Create an authentication policy based on the EPA scan. Enter the name of the policy. Select Action Type as EPA. Click Add to create action.

      Create Authentication Policy

      Create Authentication EPA Action screen appears.

      Create Authentication EPA

    5. On the Create Authentication EPA Action screen, enter the following details and click Create to create an action:
      • Name: Name of the EPA action. In this case EPA_Action_FileExists.
      • Default Group: Enter the default group name. If the EPA expression is True, users are added to the default group. The Default Group in this case is FileExists.
      • Quarantine Group: Enter the quarantine group name. If the EPA expression is False, users are added to the quarantine group.
      • Expression: Add the EPA expression that you want to scan. In this example, we consider the EPA scan to be successful if a particular file is present: sys.client_expr("file_0_C:\\\\epa\\\\avinstalled.txt")

      You return to the Create Authentication Policy screen.

    6. Enter true in the Expression editor, and click Create.

      Authentication EPA true

      You return to the Policy Binding screen.

    7. On the Policy Binding screen, do the following:

      1. Select the Goto Expression as NEXT.

      2. In the Select Next Factor section, select the LDAP policy that you’ve configured for the authentication in the Application Delivery Controller (ADC).

      3. Click Bind.

        Policy binding details

  3. Create a Smart Access Policy for trusted devices:

    1. Select Smart Access Policies on the Authentication Virtual Server page of the auth_vs server.

      Authentication virtual servers

    2. Click Add Binding.

      Add binding

    3. On the Policy Binding screen, click Add in the Select Policy section.

      Select policy

      The Create Authentication Smart Access Policy screen appears.

      Authentication Smart Access

    4. On the Create Authentication Smart Access Policy screen, enter Name for the Smart Access Policy and click Add to create a Smart Access Profile.

      The Create Authentication Smart Access Profile screen appears.

    5. Add Name for the action. Enter trusted in Tags. The tag is later referenced in the Broker Access Policy rule for configuring. Click Create.

      Create Authentication profile

      You return to the Create Authentication Smart Access Policy screen.

    6. In the Expression section, enter the expression for which you want to push the tag. In this case, since the tag is pushed for trusted devices, enter AAA.USER.IS_MEMBER_OF("FileExists"). Click Create.

      Tag for trusted devices

      You return to the Policy Binding screen.

    7. Select the Goto Expression as End and Click Bind.

      Select go to expression

  4. Create a Smart Access Policy for untrusted devices:

    1. Follow the instructions of the previous step, except sub-steps v and vi.

    2. For the sub-step v, on the Create Authentication Smart Access Profile screen, add Name for the action. Enter untrusted in Tags. The tag is later referenced in the Broker Access Policy rule for configuring. Click Create.

    3. For the sub-step vi, in the Expression section of the Create Authentication Smart Access Policy screen, enter the expression for which you want to push the tag. In this case, since the tag is pushed for untrusted devices, enter AAA.USER.IS_MEMBER_OF("FileExists").NOT.

  5. Configure the Broker Access policy rules:

    1. Install the Citrix PowerShell SDK and connect to the cloud API as explained in the Citrix blog Getting started with PowerShell automation for Citrix Cloud.

    2. Run the command Get-BrokerAccessPolicyRule.

      A list of all the broker access policies for all the delivery groups which are present is displayed.

    3. Find the DesktopGroupUid for the delivery group that you want to change.

      Desktop Group UID

    4. Get the policies that are applied only to a particular delivery group using the command:

      Get-BrokerAccessPolicyRule -DesktopGroupUid 7

    5. To filter users using trusted devices, create another Broker Access policy using the command:

      New-BrokerAccessPolicyRule -Name CAP_Desktops_AG_Trusted-DesktopGroupUid 7 - AllowedConnections ViaAG -AllowedProtocols HDX, RDP -AllowedUsers AnyAuthenticated - AllowRestart $true -Enabled $true-IncludedSmartAccessFilterEnabled $true

    6. To disable App Protection for trusted devices and enable App Protection for untrusted devices, use the following command:

      Set-BrokerAccessPolicyRule CAP_Desktops_AG_trusted -IncludedSmartAccessTags Workspace:trusted -AppProtectionKeyLoggingRequired $false -AppProtectionScreenCaptureRequired $false

      Set-BrokerAccessPolicyRule CAP_Desktops_AG -IncludedSmartAccessTags Workspace:untrusted -AppProtectionKeyLoggingRequired $true -AppProtectionScreenCaptureRequired $true

  6. Verification:

    Sign out of Citrix Workspace app and sign in again. Launch the protected resource from a trusted device, one that meets the EPA scan condition. You see that the App Protection policies are not applied. Launch the same resource from an untrusted device. You see that the App Protection policies are applied.

Scenario 2

In this article