> Security > Resource Rule. The Resource
Rules List page appears.
You must add a resource rule to allow access to Identity as a Service applications or API application protected by Identity as a Service.
1. Log in to your Identity as a Service administrator account.
2. Click
> Security > Resource Rule. 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.
Attention: You must maintain the default of all groups if you want to allow external authentication and bypass second-factor authentication for users who do not already exist in Identity as a Service. External Authentication without second-factor is only available to low risk users of Authentication APIs that support External Authentication.
6. Click Next. The Authentication Conditions Settings page appears.
7. If you do not Enable Advanced Risk Factors, do the following:
a. Select the Authentication Flow from the drop-down list. The Authentication Flow flowchart updates based on the selection.
b. Click Submit to save the Resource Rule.
8. If you want to Enable Advanced Risk Factors complete the remaining steps in this procedure.
9. Select Enable Advanced Risk Factors to add additional risk factors to the resource rule.
10. Select Enable Strict Access for Application to set the resource rule to deny access regardless of the outcome from other resource rules. If this option is disabled for any resource rule that denies access, the user is allowed access if at least one resource rule allows access.
11. For each Advanced Risk Factor, click the Deny option to deny access to the application if the risk factor fails regardless of the results of the other risk factors.
12. 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.
13. 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.
14. Click Source IP Address. The IP Address Risk Setting dialog box appears. Do one of the following:
a. Select Custom and add the required IP Allowed Addresses and IP Denied Addresses.
b. Select IP List Address and select the IP List to allow or deny.
c. Select None to not restrict any IP addresses.
d. Click OK to return to the Authentication Conditions Settings.
15. 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.
16. 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.
17. Set the risk score for application conditions to set the risk percentage a user receives if they fail to meet the condition, as follows:
● Click the dot next to the condition setting and slide the risk scale to the risk percentage
-or-
● Click the 0% and enter the risk points and then click OK.
The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decision. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.
18. If applicable, set the Transaction Condition settings. See Create and manage resource rules for more details on Transactions.
a. Click Transaction One. The Transaction Context Conditions Settings dialog box appears.
b. Change the Name for the transaction context or leave it at One.
c. Select the Transaction Rule from the drop-down list.
d. Define the number of risk points you want to assign to the transaction rule.
e. Optional. Select another Transaction Rule from the drop-down list and define the number of risk points assigned to the rule.
f. Repeat this procedure for additional Transaction Rules to apply another risk score.
g. Set the Risk Limit. If the accumulated risk score from the selected transaction rules exceed the risk limit, the resource rule transaction context fails.
19. If you add Transaction Items, set the Transaction Rules as follows:
a. On the Transaction page, under Transactions Rules, click Add. The Add Transaction Rule dialog box appears.
b. Enter a Name for the transaction rule.
c. By default, the outer boolean operator for a Transaction Rule is AND. You can also use OR .
d. Select the AND or OR boolean operator for the initial group expression.
e. Select the Expression for the Transaction Item.
i) Select the Transaction Item from the drop-down list.
ii) Select the Operator from the drop-down list.
iii) Add a value in the Value text box.
f. To add another Expression to the rule,click Add Rule and repeat Step e.
g. To add another set of rules to the Transaction Rule, click Add Group.
h. Select the AND or OR operator for each added group expression.
i. Repeat Step e.
j. Click Submit.
k. Repeat these steps to add more transaction rules.
20. Test the Transaction Rule, as follows:
a. Click to 
next
to the rule to test the rule. The Test Rule
dialog box appears.
b. Enter values for each of the transaction details that would be used as part of the Authentication API and then click Test Rule. The response indicates whether the supplied transaction details would trigger a risk.
c. Repeat this procedure for Transaction Two.
21. If applicable, add an External Risk Engine, as follows:
a. Click Add External Risk Engine. The External Risk Engine Context Conditions Settings dialog box appears.
b. Change the Name for the external risk engine.
c. Select the External Risk Engine from the drop-down list.
d. Select the Risk Rule from the drop-down list.
e. Define the Risk Points you want to assign to the external risk engine rule.
f. Set the Risk Limit for the external risk engine rule. This limit applies when the Accumulated Risk Score is above the risk limit value.
g. Click OK. The External Risk Engine appears in the resource rule Risk Factor list.
h. Optional. Select another Risk Rule from the drop-down list and define the number of risk points assigned to the rule.
i. Repeat this procedure for additional external risk engines. You can create a maximum of 5 external risk engines.
Note: Transaction items and external risk engines apply only to Authentication APIs.
22. Set the Authentication Decision risk level 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.
23. Select the Authentication Flows for Low Risk, Medium Risk, and High Risk from the drop-down lists. The Authentication Flows flowchart updates based on your selections.
24. Click Submit to create the resource rule.