Configure Connector-based risk engines

Connector-based risk engines support configuration of the IDaaS API to support third-party risk engines without the need to do development. Before you begin, review the information about placeholders. Placeholders are optional and can be used in the HTTP Connector to further define the data requested from the external risk engine.

Placeholders

Connector-based risk engine configuration supports the use of placeholders. A placeholder is a symbol to mark a place and name when configuring connectors for the dynamic data and you do not have the values when composing the API call. The values are populated in when the call is made to the connector.

Placeholder restrictions

– REQ.—The placeholder's value comes from the Request body. The rest of placeholder after prefix REQ. must match one of the names in the transactionDetails of the request.

– AUTH—The authentication information gathered from the Authentication Method used in the risk engine configuration.

● Placeholders prefixed by REQ., USER., or ENV. include dynamic data that interacts with the user's inputs. The name after the prefix must match. In contrast, AUTH is a special type of placeholder.

● Placeholders cannot use delimiter symbols. The placeholders and resultItems used in the same HTTP Connector must be unique.

● A placeholder, once configured, must have its values, in one of the following:

– REQ. and ENV.—Request payload in the transactionDetails and usage must be RBA.

● All the values are mandatory. If any placeholder cannot find its matching values, the connector call will fail.

1. Click

> Configuration > External Risk Engines. The External Risk Engines page appears.

2. Click Add and then select Connector-based Risk Engines from the drop-down list. The Add External Risk Engine page appears.

Note: You can also enable or disable the external risk engine after you add it from the External Risk Engines page.

5. From the Authentication Request drop-down list, select how IDaaS authenticates to the risk engine to make a risk request. Options include:

● Authentication Request. The risk engine returns an authentication token. IDaaS uses the authentication token to make the authentication risk calls. If you select this option, you must add an Add Authentication Connector to configure how IDaaS makes the request to the risk engine to obtain the authentication token.

Note: What you include in this section depends on the risk engine being used and they type of information it requires to make the risk request and return the authentication token. The following steps describe the purpose of each setting, but depending on the risk engine, they may not all apply. Items with an asterisk (*) are required values.

a. Click Add next to Authentication Connector. The Add HTTP Connector page appears.

b. Enter a Name for the request.

c. From the Method drop-down list, select the HTTP request method used to make the request to the risk engine.

d. In the URL field, enter the URL of the login endpoint of the risk engine to obtain the token. If applicable, add required parameters to the URL that are used to make the request to the risk engine.

Note: The Domain part of the URL must be an external host name or an IP address. Internal hostnames are not allowed.

e. From the Authorization Type, drop-down list, select the authentication method passed to the risk engine to obtain the authentication token. Depending on the selection you make, you are prompted for additional information, as follows:

– Basic. Enter the User Name and Password for the risk engine.

– API_Key. Select the API Key Type and enter the API Key Value.

– BEARER_TOKEN. Enter the token value used by the risk engine.

f. If required, click Add to add authorization Headers to the HTTP request, and then enter the Header Name and Header Value. You can add as many headers as required to make the request.

g. If required, In the Results Items section, set the values used to return the risk assessment, as follows:

i) Enter the Key that is used to assess the risk.

ii) Select the Value Type, which can be either a String or a Numeric value, and enter the JsonPath for the results item.

Note: For more information on Query expressions for JSON, see RFC 9535, JSONPath: Query Expressions for JSON.

iii) Click Add to define additional Keys used to return the results of the risk assessment.

h. Optional. In the Request Body, add additional content, as required.

i. Click Add to save the HTTP Connector and return to the Add External Risk Engine.

● Basic Authentication. You are prompted to enter the username and password defined by the risk engine and include it in the risk request.

● Mutual TLS. You are prompted to upload the certificate file that is shared with the risk engine server.

Add a Risk Score Connector. The Risk Score Connector returns the risk score from the external risk engine.

a. Next to Risk Score Connector, click Add. The Add HTTP Connector page appears.

b. Enter a Name for the request.

c. From the Method drop-down list, select the HTTP request method used to make the request to the risk engine.

d. In the URL field, enter the URL of the risk data endpoint of the risk engine to obtain the risk data. If applicable, add required parameters to the URL that are used to make the request to the risk engine.

Note: The Domain part of the URL must be an external host name or an IP address. Internal hostnames are not allowed.

– Basic. Enter the User Name and Password for the risk engine.

– API_Key. Select the API Key Type and enter the API Key Value.

– BEARER_TOKEN. Enter the token value used by the risk engine.

f. If required, click Add to add authorization Headers to the HTTP request, and then enter the Header Name and Header Value. You can add as many headers, as required to make the request.

g. If required, In the Results Items section, set the values used to return the risk assessment, as follows:

i) Enter a name for the result item in the Key field that will be used as the risk item to compose the rules.

ii) Select the Value Type, which can be either a String or a Numeric value, and enter the JsonPath for the results item.

Note: For more information on Query expressions for JSON, see RFC 9535, JSONPath: Query Expressions for JSON.

iii) Click Add to define additional Keys used to return the results of the risk assessment.

Note: A resultItem used by a risk engine rule cannot be deleted.

h. Optional. In the Request Body, add additional content, as required.

i. Click Add to save the HTTP Connector and return to the Add External Risk Engine.

7. Add Rules used to assess the risk score. You must add at least one rule. Follow these steps:

c. From the Risk Item drop-down list, select The risk items available are based on the Result Items for the risk connector you created in step 7.

i) Click Add Group.

ii) Enter a Name for the group.

i) Select the AND or OR operator for each added group expression.

ii) Select the Risk Item from the drop-down list.

iii) Select the required Operator from the drop-down list.

iv) Add a value in the Value text box.

v) Click Add Rule.

vi) Repeat these steps to add more rules to the group.

vii) Click Save.

8. Click Save to save the external risk engine and return to the External Risk Engines page.