HID Risk Management Solution (RMS) Web Component - Non-Financial

Important: It is assumed that you have already configured HID RMS Web Component - Login Flow. If not, configure it and then proceed with this section. The HID RMS Web Component - Login Flow is the main component which includes all the Component settings.

Non-Financial Flow: All flow except Financial such as Fund Transfer comes under Non-Financial Flow. You can use this flow along with User Management components for operations such as Device Friendly Name Update, Active/Suspend Device, Add Device, Update Password etc.,. This component can be used in any Temenos Digital flow where there is a requirement of adaptive authentication. These actions can also be tracked from RMS Dashboard.

Configuration:

Mandatory Non-financial Component Settings	thresholdScore	<Risk Score, can be set from 0 - 10>, this threshold settings will be decide the Step-Up or Step-Down
	MFA	allowed value <“STD_PWD”, “OTP_SMS”, “OTP_EML”, “APPROVE”, “OTP_HWT”>
	tmCookieTag	<cookie value associated with the RMS>, mandatory field This identifier is issued by RMS .Each new device used by the user to access the protected application will be tagged by RMS. This attribute is mandatory and should be always sent.
	tmCookieSid	<cookie value associated with the RMS>, mandatory field This identifier is issued by RMS and serves as a unique identification of a user's session. Its value is persistent throughout the whole session and is stored as a cookie pair.
	SecondFactor	allowed value <"OTP_SMS" "OTP_EML", "Approve", "NO_MFA">

Non-Financial Services

ServiceName	DataModel	Mapping	Purpose	Invoking
HIDRMSService	RMSActionCreate	rmsActionCreate	To create an action in RMS.	RMSThreatMarkAPI/actionCreate
HIDRMSService	RmsActionComplete	rmsActionComplete	This service is complete the action in RMS.	RMSThreatMarkAPI/actionComplete
HIDRMSService	RmsActionComplete	rmsActionReject	This service is used to reject/Cancel the action in RMS.	RMSThreatMarkAPI/actionReject

Non-Financial Component Public Function:

Functions	Descriptions
updateActioninRMS	This function update RMS about completion of any Non-Financial action when invoked. Parameters : → NA Return Type : → NA
anlyzeAction	This function calculate the risk score on the action being called. Parameter : → username, actionType, sessionId Return Type :- NA
stepUpAuthentication	This function performs the MFA.

Functions

Descriptions

updateActioninRMS

This function update RMS about completion of any Non-Financial action when invoked.

Parameters : → NA

Return Type : → NA

anlyzeAction

This function calculate the risk score on the action being called.

Parameter : → username, actionType, sessionId

Return Type :- NA

stepUpAuthentication

This function performs the MFA.

Sequential Diagram

Flow Chart Diagram

Functional Flow

Let's consider Active/Suspend action for understanding the functional Flow:

User is already into the application's dashboard page and selects option to rename.
After clicking the Submit option, based on the detail captured by the HID RMS, Risk Score is generated for that user.
After getting the Risk Score from the HID RMS, system compares the Risk Score with thresholdScore (Component Setting). Application then decides for MFA authentication i.e., SMS OTP, SMS EMAIL, and Approve.
- If Risk Score > thresholdScore, MFA Authenticator will be shown for Authentication which is defined in component properties as MFA.
- If Risk Score < thresholdScore, there will be no Authenticator shown.