Adaptive access and security controls for Enterprise Web, TCP, and SaaS applications

In today’s ever changing situations, application security is vital for any business. Making context-aware security decisions and then enabling access to the applications reduces the associated risks while enabling access to users.

The Citrix Secure Private Access service adaptive access feature offers a comprehensive zero-trust access approach that delivers secure access to the applications. Adaptive access enables admins to provide granular level access to the apps that users can access based on the context. The term “context” here refers to:

• Users and groups (users and user groups)
• Devices (desktop or mobile devices)
• Location (geo-location or network location)
• Device posture (device posture check)
• Risk (user risk score)

The adaptive access feature applies adaptive policies to the applications that are being accessed. These policies determine the risks based on the context and make dynamic access decisions to grant or deny access to the Enterprise Web, SaaS, TCP, and UDP apps.

How it works

To grant or deny access to applications, admins create policies based on the users, user groups, the devices from which the users access the applications, the location (country or network location) from where the user is accessing the application, and the user risk score.

The adaptive access policies take precedence over the application-specific security policies that are configured while adding the SaaS or a Web app in the Secure Private Access service. The per-app level security controls are overwritten by the adaptive access policies.

The adaptive access policies are evaluated in three scenarios:

• During a Web, TCP, or a SaaS app enumeration from the Secure Private Access service – If the application access is denied to this user, the user cannot see this application in the workspace.

• While launching the application – After you have enumerated the app and if the adaptive policy is changed to deny access, users cannot launch the app even though the app was enumerated earlier.

• When the app is opened in a Citrix Enterprise Browser or a Remote Browser Isolation service – The Citrix Enterprise Browser enforces some security controls. These controls are enforced by the client. When the Citrix Enterprise Browser is launched, the server evaluates the adaptive policies for the user and returns those policies to the client. The client then enforces the policies locally in the Citrix Enterprise Browser.

Create an adaptive access policy with multiple rules

You can create multiple access rules and configure different access conditions for different users or user groups within a single policy. These rules can be applied separately for both HTTP/HTTPS and TCP/UDP applications, all within a single policy.

Access policies within Secure Private Access allow you to enable or disable access to the apps based on the context of the user or user’s device. In addition, you can enable restricted access to the apps by adding the following security restrictions:

• Restrict clipboard access
• Restrict printing
• Restrict downloads
• Restrict uploads
• Display watermark
• Restrict key logging
• Restrict screen capture

For more information on these restrictions, see Available access restrictions.

Ensure that you have completed the following tasks before configuring an access policy.

• Set up identity and authentication
• Configured applications

1. On the navigation pane, click Access Policies and then click Create policy.

   

   For the first-time users, the Access Policies landing page does not display any policies. Once you create a policy, you can see it listed here.

2. Enter the policy name and description of the policy.
3. In Applications, select the app or set of apps on which this policy must be enforced.

4. Click Create Rule to create rules for the policy.

   

5. Enter the rule name and a brief description of the rule, and then click Next.

   

6. Select the users’ conditions. The Users condition is a mandatory condition to be met to grant access to the applications for the users. Select one of the following:

   • Matches any of – Only the users or groups that match any of the names listed in the field and belonging to the selected domain are allowed access.
   • Does not match any - All users or groups except those listed in the field and belonging to the selected domain are allowed access.

   

7. (Optional) Click + to add multiple conditions based on the context.

   When you add conditions based on a context, an AND operation is applied on the conditions wherein the policy is evaluated only if the Users* and the optional contextual based conditions are met. You can apply the following conditions based on context.

   • Desktop or Mobile device – Select the device for which you want to enable access to the apps.
   • Geo location – Select the condition and the geographic location from where the users are accessing the apps.
   • Network location – Select the condition and the network using which the users are accessing the apps.
   • Device posture check – Select the conditions that the user device must pass to access the application.
   • User risk score – Select the risk score categories based on which the users must be provided access to the application.
8. Click Next.

9. Select the actions that must be applied based on the condition evaluation.

   • For HTTP/HTTPS apps, you can select the following:
     • Allow access
     • Allow access with restrictions
     • Deny access

     Note:

     If you select Allow access with restrictions, then you must select the restrictions that you want to enforce on the apps. For details on the restrictions, see Available access restrictions options. You can also specify if you want the app to open in a remote browser or in Citrix Secure Browser.

   • For TCP/UDP access, you can select the following:
     • Allow access
     • Deny access

   

10. Click Next. The Summary page displays the policy details.

11. You can verify the details and click Finish.

    

Points to remember after a policy is created

• The policy that you created appears under the Policy rules section and is enabled by default. You can disable the rules, if required. However, ensure that at least one rule is enabled for the policy to be active.

• A priority order is assigned to the policy by default. The priority with a lower value has the highest preference. The rule with a lowest priority number is evaluated first. If the rule (n) does not match the conditions defined, the next rule (n+1) is evaluated and so on.

  

Evaluation of rules with priority order example:

Assume that you have created two rules, Rule 1 and Rule 2. Rule 1 is assigned to user A and Rule 2 is assigned to user B, then both rules are evaluated. Assume that both rules Rule 1 and Rule 2 are assigned to user A. In this case, Rule 1 has the higher priority. If the condition in Rule 1 is met, then Rule 1 is applied and Rule 2 is skipped. Otherwise, if the condition in Rule 1 is not met, then Rule 2 is applied to user A.

Note:

If none of the rules are evaluated, then the app is not enumerated to the users.

Available access restrictions options

When you select the action Allow access with restrictions, you must select at least one of the security restrictions. These security restrictions are predefined in the system. Admins cannot modify or add other combinations. For details, see Available access restrictions options

Adaptive access based on devices

To configure an adaptive access policy based on the platform (mobile device or a desktop computer) from which the user is accessing the application, use the Create an adaptive access policy with multiple rules procedure with the following changes.

• In Step2: Conditions page, click Add condition.
• Select Desktop or Mobile device.
• Complete the policy configuration.

Adaptive access based on the location

An admin can configure the adaptive access policy based on the location from where the user is accessing the application. The location can be the country from where the user is accessing the application or the user’s network location. The network location is defined using an IP address range or subnet addresses.

To configure an adaptive access policy based on the location, use the [Create an adaptive access policy with multiple rules procedure with the following changes.

• In Step2: Conditions page, click Add condition.
• Select Geo-location or Network location.
• If you have configured multiple geo-locations or network locations, then select one of the following as per your requirement.
  • Matches any of – The geographic locations or network locations match any of the geographic locations or network locations configured in the database.
  • Does not match any – The geographic locations or network locations do not match with the geographic locations or network locations configured in the database.

  Note:

  • If you select Geo-location, the source IP address of the user is evaluated with the IP address of the country database. If the IP address of the user maps to the country in the policy, the policy is applied. If the country does not match, this adaptive policy is skipped and the next adaptive policy is evaluated.

  • For Network location, you can select an existing network location or create a network location. To create a new network location, click Create network location.

  • Ensure that you have enabled Adaptive Access from Citrix Cloud > Citrix Workspace > Access > Adaptive Access. If not, you cannot add the location tags. For details, see Enable Adaptive Access.

  • You can also create a network location from the Citrix Cloud console. For details, see Citrix Cloud network location configuration.

  

• Complete the policy configuration.

Adaptive access based on the device posture

You can configure Secure Private Access service to enforce access control using device posture tags. After a device is allowed to log in after the device posture verification, the device can be classified as compliant or non-compliant. This information is available as tags to Citrix DaaS service and Citrix Secure Private Access service and is used to provide contextual access based on device posture.

For complete details on Device Posture service, see Device Posture.

To configure an adaptive access policy based on the device posture, use the Create an adaptive access policy with multiple rules procedure with the following changes.

• In Step2: Conditions page, click Add condition.
• Select Device posture check and the logical expression from the drop-down menu.
• Enter one of the following values in custom tags:
  • Compliant - For compliant devices
  • Non-Compliant - For non-compliant devices

  Note:

  The syntax for the device classification tags must be entered in the same manner as captured earlier, that is initial caps (Compliant and Non-Compliant). Else the device posture policies do not work as intended.

Adaptive access based on user risk score

Important:

This feature is available to the customers only if they have the Security Analytics entitlement.

User risk score is a scoring system to determine the risks associated with the user activities in your enterprise. Risk indicators are assigned to user activities that look suspicious or can pose a security threat to your organization. The risk indicators are triggered when the user’s behavior deviates from the normal. Each risk indicator can have one or more risk factors associated with it. These risk factors help you to determine the type of anomalies in the user events. The risk indicators and their associated risk factors determine the risk score of a user. The risk score is calculated periodically and there is a delay between the action and the update in the risk score. For details, see Citrix user risk indicators.

To configure an adaptive access policy with risk score, use the Create an adaptive access policy with multiple rules procedure with the following changes.

• In Step2: Conditions page, click Add condition.

• Select User risk score and then select the risk condition.

  • Preset tags fetched from the CAS service

    • LOW 1–69
    • MEDIUM 70–89
    • HIGH 90–100

    Note:

    A risk score of 0 is not considered to have a risk level “Low.”

  • Threshold types
    • Greater than or equal to
    • Less than or equal to
  • A number range
    • Range