Secure apps with MFA

On the Policy page, you can secure apps with MFA by applying rules-based authentication profiles.

You can also include JavaScript to identify specific circumstances when you want to block an application or you want to require additional authentication methods. For details, see Application access policies with JavaScript.

Watch the video!

To apply a rules-based authentication profile to an app

  1. Click Policy in the Admin Portal.

  2. (Optional) Click Add Rule to specify conditional access.

    The Authentication Rule window appears.

  3. Click Add Filter on the Authentication Rule window.

  4. Define the filter and condition using the drop-down menus.

    Filter Description Conditions available

    IP Address

    The computer’s IP address when the user logs in. You can create rules based on:

    • Whether the IP address is inside or outside the corporate network.

      Use either the inside secure zone or outside secure zone condition. Secure Zones are defined in Settings > Network > Secure Zones.

    • Whether the IP address is inside a subset of your corporate network.

      Use the inside secure zone... condition. If you select this condition, you also need to indicate the specific Secure Zone (IP range configured in the IP table in Settings > Network > Secure Zones).

    To configure the IP address condition, you first need to configure the IP address range in Settings > Network > Secure Zones. See Define Secure Zones. The specified authentication profile is then applied to users whose IP address matches the specified IP address value, or falls within the specified IP address range.

    Also see Disable Secure Zones to exempt certain IP addresses or ranges from policy rules.

    • inside secure zones
    • outside secure zones
    • inside secure zone...
    Identity Cookie

    The cookie that is embedded in the current browser by CyberArk Identity after the user has successfully logged in.

    • Is present
    • Is not present

    Day of Week

    Specific days of the week (Sunday through Saturday). You can select one or more, based on either User Local Time or UTC.

    Checkboxes for each day of the week and radio buttons to select either User Local Time or UTC


    A date before or after which the user logs in that triggers the specified authentication requirement, based on either User Local Time or UTC.

    • Less than <selected date>
    • Greater than <selected date>

    User Local Time or UTC

    Date Range

    A specific date range, based on either User Local Time or UTC.

    Date pickers and radio buttons for User Local Time or UTC

    Time Range

    A specific time range in hours and minutes, based on either User Local Time or UTC.

    Strings representing time ranges in the format hh:mm, with radio buttons for User Local Time or UTC

    Network Level Authentication

    This filter is used to apply authentication profiles based on whether an RDP client has completed Network Level Authenticaton ("NLA").

    • is done

    • is not done


    The browser used for opening the CyberArk Identity portal.

    • equal to
    • not equal to


    CyberArk Identity roles that a user belongs to. If a user belongs to multiple roles, the authentication rule that comes first (highest priority on top) is honored.

    If a role is renamed following the creation of an authentication rule using Role as a filter, the authentication rule will automatically update with the new role name. If a role is deleted, the portion of the any authentication rule using that role as a filter will also be deleted.

    This filter is only applicable to managing web application access.

    • equal to
    • not equal to


    The country based on the IP address of the user computer.

    • equal to
    • not equal to

    Risk Level

    Risk Level: The authentication factor is the risk level of the user logging on to the User Portal. For example, a user attempting to log in to CyberArk Identity from an unfamiliar location can be prompted to enter a password and text message (SMS) confirmation code because the external firewall condition correlates with a medium risk level. This Risk Level filter requires additional licenses. If you do not see this filter, contact CyberArk support. The supported risk levels are:

    • Non Detected -- No unexpected activities are detected.
    • Low -- Some aspects of the requested identity activity are unexpected. Remediation action or simple warning notification can be raised depending on the policy setup.
    • Medium -- Many aspects of the requested identity activity are unexpected. Remediation action or simple warning notification can be raised depending on the policy setup.
    • High -- Strong indicators that the requested identity activity is an anomaly and the user's identity has been compromised. Immediate remediation action, such as MFA, should be enforced.
    • Undetermined -- Not enough user behavior activities (frequency of system use by the user and length of time user has been in the system) have been collected.

    The following video illustrates how to create an authentication rule based on risk level.

    • equal to
    • not equal to

    Managed Devices

    A device is considered “managed” if it is enrolled in CyberArk Identity and you use CyberArk Identity for device management. A device that is enrolled for only single sign-on or endpoint authentication is not considered a managed device. For more information about the difference, refer to Mobile Device Management or single sign-on only.

    The Windows Cloud Agent does not include device management features. Enrolled Windows machines are not considered managed devices.

    This filter is only applicable to managing web application access.

    • True
    • False

    Certificate Authentication

    Whether or not you use a digital certificate issued by your organization’s trusted certificate authority. You can upload a certificate using the Admin Portal > Settings > Authentication > Certificate Authorities. Users can also individually use CyberArk as their trusted certificate authority and automatically install the digital certificate by enrolling their devices.

    For example, if you configure an authentication rule to use the Certificate Authentication condition, then CyberArk Identity checks for a digital certificate issued by a trusted certificate authority and enforces the specified authentication profile before allowing access to this application.

    CyberArk support must enable the Certificate Authentication filter for your company.
    • is used
    • is not used
  5. Click the Add button associated with the filter and condition.

  6. Select the profile that you want applied if all filters/conditions are met in the Authentication Profile drop-down, then click OK.

    The authentication profile is where you define the authentication mechanisms. If you have not created the necessary authentication profile, select the Add New Profile option. See Create authentication profiles.

  7. (Optional) In the Default Profile (used if no conditions matched) drop-down, you can select a default profile to be applied if a user does not match any of the configured conditions.

  8. If you have no authentication rules configured and you select Not Allowed in the Default Profile drop-down, users will not be able to log in to the service.

  9. (Optional) If you have more than one authentication rule, you can drag and drop the rules to a new position in the list to control the order they are applied.

  10. Click Save.