Skip to main content

Policy management

The policies management console allows you to review the list of existing policies, update, delete, or create new ones.

Policies main page


From left navigation, go to Policies > Standard to see the list of predefined standard policies. Standard policies are either predefined by SecureAuth or by the administrator in your organization. On this page, you only can do the following operations:

  • Specify the target applications

  • Enable or disable the policy

  • Provide the parameters for the policy


To create or update policies, from the left navigation, go to Policies > Advanced. On this page, you can create, update or delete policies in addition to the available options in Standard mode. As an administrator, you can use this mode to create new pre-defined policies so that they appear in the Standard mode.

Deleting a policy

To delete a policy, click the trash bin icon and approve the confirmation.

Editing a policy

To edit a policy, click the pencil icon. It takes you to the edit mode of Policy details page, where you can update the selected policy.

Creating a new policy

To create a new policy, go to the bottom of the table and click Create New Policy. It takes you to the Policy details page, where you can define a new policy.

Policy details page

You can create a new policy or view and update an existing one from this page.

Arculix policies page

Policy Information

You specify the general policy information in this section.

Arculix policy information section


Name of policy.


(Optional). Description of policy.


Select the event on which the policy will be evaluated. Available options:

  • Authentication – Policy applies to first-time authentication events and continuous authenticatio events.

    For example, a user logs in to a SAML-based application and it provides continuous authentication access when the user switches to another SAML-based application while still logged in.

  • Enrollment – Policy applies to users logging in for the first time.

    For example, when a user logs in for the first time, it forces device pairing.


To universally apply this policy to all applications, select the Apply to All Applications check box.

Otherwise, select the SAML applications to which the policy applies from the list.


To make this policy active, select the Enabled check box.


To show this policy on the Standard policies page, select the Predefined check box.


In this section, you specify the conditions for which you would like the policy's action to be executed. The policy will be executed only when all condition predicates are met. In other words, the logic between the condition predicates is AND.

Below you can find the list of condition predicates.


The policy will be applied in all circumstances for the specified application(s) and event. For example, you want to temporarily disable MFA for all users.

Active Directory Groups

If integrated with your organization's Active Directory, you can specify one or more user groups so that the policy will be executed if the authenticating user belongs to any of the specified groups.

Overall LOA Score

To learn more, see LOA score.

You can specify the threshold for the LOA score to trigger the policy execution. You can set the policy to be executed either when the LOA score is greater than or equal to or smaller than or equal to a specific value.

For instance, if you set it to be greater than or equal to 3 and choose the Auto Approve action for the policy, the user will be allowed to log in without multi-factor authentication.


Allows you to specify the condition based on the user's IP address. You can specify one or multiple IP addresses or a range of IPs using CIDR notation. They can be separated by commas, like,,


Allows you to specify the country where the user is located. This is based on the geo-location information obtained from the user's browser or mobile device.

If more than one country is specified, the condition is met when the user is located in any of them.

Time of Day

Allows you to define the time and day pattern when the user is trying to authenticate. You can specify not only the time range but also the days of the week. For example, combined with the Country condition, you can increase the friction for the users located in a specific country when they're trying to get access to the system while it's outside of business hours or during the weekend.

Login to Other Applications

Allows you to define a condition based on applications that the user has signed into within the specified period of time.

Selecting the Require matching IP address? option ensures that this condition is met only when the user is coming from the same IP address for each application.

For example, you can define a policy that auto approves a user's request to authenticate to a web application if the same user has used MFA to their Windows machine from the same IP address within the last 5 minutes.

Paired Desktop Workstation

Allows you to define a condition based on whether the user has a paired workstation with the specified configuration; all selected fields must match in order for the condition to be met. This allows granular control of when to apply a policy. Configuration options include operating system type and version, whether the device is configured to use a firewall, password, or secure boot, IP address, and more.


User-Defined Condition

This predicate gives you the highest level of customization. You can create a predicate using the Ruby programming language.

For example the following predicate UI:


Can also be written in Ruby in the admin panel console as a custom predicate:


Visit the User-defined policy predicate page to learn more.


When all policy conditions are met, the specified action for the policy will be executed.

Here are the actions you can select for Authentication events:

  • Automatically Approve: Skips MFA by automatically approving the authentication

  • Automatically Reject: Blocks user access by rejecting the authentication automatically

  • Force Out Of Band: Overrides all current rules and forces the user to complete MFA

  • Change LOA Score: Increase or decrease the user's LOA score to tune the LOA score based on your needs

And the action you can define for Enrollment event:

  • Require Device Pairing Forces the user to pair their mobile device when they're authenticating for the first time or if one is not currently paired.

Actions Priority

In cases where there are multiple policies applied to the same transaction, the result is calculated according to the following order:

  1. If there is one or more matching policy with Automatically Reject action, the MFA gets rejected

  2. If the above rule is not true and there is one or more matching policy with Force Out of Band action, then the user gets MFA

  3. If the above rules are not true and there is one or more matching policy with Automatically Approve action, then MFA gets approved

For example, if five different policies match the current conditions and one of them is set to execute "Automatically Reject" action, then the user will be rejected no matter what action is specified for the other policies.