Integrate Druva

Limitation: Resource rules for SAML applications cannot have resource rules with External Authentication set as the First Authentication Step.

Create a resource rule to protect access to a SAML application

1.      Log in to your Identity as a Service administrator account.

2.      Click > Security > Resource Rules. The Resource Rules List page appears.

3.      Click + next to the application you want to protect with a resource rule. The Add Resource Rules page appears.

4.      Enter a Rule Name and Rule Description for the resource rule.

5.      In the Groups list, select the group or groups of users restricted by the resource rule.

These are the groups to which the resource rule applies. If you do not select any groups, by default the resource rule applies to all groups.

6.      Click Next. The Authentication Conditions Settings page appears.

7.      Click Date/Time to set the conditions as follows:

a.      Select one of the following:

–  Allow Date/Time  to set when a user can access the application.

–  Deny Date/Time to set when the user cannot access the application.

The Date/Time Context Condition Settings appear.

b.      Select the Condition Type:

–  Specific Date Range Condition—Allows or denies access to the application during a select period of days.

–  Time-of-day and/or Day of Week Recurring Conditions—Allows or denies access to the application on a specific time of day, day of the week, or both. Recurring times selected only apply to days not denied.

–  Clear Selection—Clears existing Date and Time conditions.

c.      Set the Condition Type settings, as follows:

i)        Select Use local time zone to use the local time zone or deselect Use local time zone to use the local time zone and begin typing the time zone in the Begin Typing Timezone name field and select the time zone from the drop-down list.

ii)      If you selected Specific Date Range Condition, click Start Date to select a start date from the pop-up calendar. Optionally, select the End Date.

iii)     If you selected Time-of-Day and/or Day-of-Week, click Start Time and select the start time from the pop-up clock. Optionally set the End Time. You must also select the days of the week for the condition.

d.      Click Save to return to the Authentication Conditions Settings page.

8.      Click Geolocation to set the Location Condition Settings, as follows:

a.      Select Allow or Deny to create an allowed or denied country list.

b.      From the Selected Countries drop-down list, select the countries to add or deny access to the application. Repeat until you have added all the desired countries to the list.

c.      Select Allow Anonymous IP Address to increase the risk of users authenticating from an anonymous IP.

d.      Click Save to save to return to the Authentication Conditions Settings page.

Note: Identity as a Service uses GeoLite2 data created by MaxMind, available from http://www.maxmind.com.

9.      Click Source IP Address to set the IP Context Condition Settings, as follows:

a.      Click Add to add the IP Addresses that you want to allow or block.

b.      Enter the IP Address/CIDR that you want to allow or block.

c.      Click the icon to toggle between Allow and Block.

d.      Repeat steps a-c until all the required IP addresses/CIDR are added to the list.

e.      Click Save to return to the Authentication Conditions Settings page.

10.  Click Machine Authentication to set the Machine Authentication Condition Settings, as follows:

a.      Set the Machine Authentication Risk is less than or equal to the value that the machine authenticator's total risk score must be less than during authentication to pass this condition.

The risk score is based on the attribute differences between a user's Machine Authentication information and that recorded on Identity as a Service before the condition fails. If an attribute does not match, the attribute incurs the number of risk points shown in Non-Matching Risk Points for that attribute. The Non-Matching Risk Points values of each non-matching attribute are added together, resulting in a total risk score. This score is normalized to be out of 100 as follows:

Total Risk Score = (Total Risk Points of Failing Attributes / Maximum Risk Points of All Enabled Attributes) * 100

The resource rule condition fails when the number of non-matching risk points exceeds the Machine Authentication Risk value defined in this step. A value of 0 means that a single attribute difference causes the Device Fingerprint condition to fail. The default value is 3. The value between 0-50 can be entered.

The default value is defined by the Machine Risk Limit. See Manage machine authenticator settings.

b.      Click Save.

11.  Define the Location History / Known Locations and Travel Velocity conditions. The Risk-Based Authentication (RBA) settings of your Identity as a Service account define the location history and travel velocity conditions. See Manage risk-based authentication settings for more information.

12.  Set the risk score for application conditions by clicking the dot next to the condition setting and sliding the risk scale to the risk percentage a user receives if they fail to meet the condition. The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decisions. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.

13.  Set the risk threshold for Medium Risk and High Risk, as follows:

a.      Click the risk threshold percentage to the right of Medium Risk or High Risk. The Risk Threshold dialog box appears.

b.      Enter the risk percentage.

c.      Click OK.

14.  Set the Authentication Decisions for low, medium, and high risk, as follows:

a.      Select the first-factor from the drop-down list.

The type of authenticator selected is the first type of authentication challenge a user must complete to access the application. The list of Second Factors authenticators available updates based on the type of first-factor authenticator selected.

b.      Click the check boxes to select the Second Factors.  

The authenticators you select are those that can be used to complete the authentication challenge.

c.      Click and drag the Second Factors authenticators for the risk level so that they are ordered from top to bottom in order of preference.

d.      Repeat step c  for Medium Risk and High Risk.

Note: You cannot add second factors to medium and high risk if you select Deny Access is selected as the first-factor.

15.  Enable Smart Login. Smart Login is available only if your account has been enabled to allow Smart Login. Smart Login can be used to authenticate to the Identity as a Service Admin Portal, User Portal, OIDC, and SAML applications integrated with Identity as a Service. See Protect applications with a resource rule for more information.

a.      Select Enable Smart Login.

When you enable Smart Login, first-factor and second-factor Authenticators are used for fallback authentication.

b.      Select the first-factor authentication method used for fallback.

Entrust recommends using Skip Password for first-factor. If you do not want to enable fallback authentication, select Deny Access from the first-factor drop-down list.

c.      Click the check boxes to select the Second Factors used for Fallback authentication. 

Entrust recommends selecting Mobile Smart Credential Push as the second factor fallback authentication method. The authenticators you select are those that can be used to complete the authentication challenge.

d.      Click and drag the Second Factors authenticators for the risk level so that they are ordered from top to bottom in order of preference.

e.      Repeat these steps for Medium Risk and High Risk.

Note: You cannot add second factors to medium and high risk if you select Deny Access as the first-factor.

16.  Optional: Select Disable Single Sign-On for Application to force a user to re-authenticate using the authenticator level required when the user accesses the application.

Note: This setting is only available for resource rules that protect Identity as a Service Administrator and User Portals and SAML applications.

17.  Optional: Click Show KBA Advanced Settings to modify the Q&A challenge size and Number of Wrong Answers Allowed for the resource rule. This setting is visible only if you select KBA for second-factor authentication and you have modified the Identity as a Service default settings for Knowledge-based authentication (see Modify knowledge-based authentication settings).

18.  Click Submit to create your resource rule.