Simulating Actions from the Intelligent Adaptive Authentication demo app
- 18 Oct 2024
- 3 Minutes to read
- DarkLight
Simulating Actions from the Intelligent Adaptive Authentication demo app
- Updated on 18 Oct 2024
- 3 Minutes to read
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
You can also handle actions such as authentications and transactions via the OneSpan Intelligent Adaptive Authentication demo app. In the app, select the relevant parameters from the Mock device data menu item.
Mobile login
If Ms Doe accesses her account details on her mobile device via the OneSpan Intelligent Adaptive Authentication demo app, the MobileLoginAttempt event will match the Risk Management component rules that correspond to the parameters you selected in the Mock device data menu. These rules are part of the Adaptive Authentication campaign and the Mobile Login Compromised Device division. The login attempt can match different rules, according to the selected parameter.
Mocked device data parameters and relevant M-Banking rules in the Risk Management component | |
Matched Risk Management component rule | Description |
|---|---|
Selected parameter: Rooted | |
Rooted (Medium) | If the user attempts to log in with a rooted device, the Intelligent Adaptive Authentication service will accept the login without prompting any challenges. |
Selected parameter: Hooking framework | |
hookingFrameworks detected (High) | If a hooking framework has been detected, the Intelligent Adaptive Authentication service will prompt the user to enter their PIN. |
Selected parameter: Application repackaging | |
applicationRepackaged detected (Medium) | If a device, for which application repackaging has been used, is detected, the Intelligent Adaptive Authentication service will decline the login. |
Selected parameter: Library injection | |
libraryInjection Detected (Medium) | If a device with library injection is detected, the Intelligent Adaptive Authentication service will decline the login. |
Selected parameter: Secure element | |
Secure element not supported (Low) | If the user logs in with a device, for which no secure element could be detected, the Intelligent Adaptive Authentication service will accept the login without prompting any challenges. |
To complete the action, a Cronto image and a notification are sent to the mobile device.
Mobile transaction
If Ms Doe handles transactions on her mobile device via the OneSpan Intelligent Adaptive Authentication demo app, the M-Banking Transfer event will match the Risk Management component rules that correspond to the parameters you selected in the Mock device data menu. These rules are part of the Adaptive Authentication Mobile Payments campaign and Compromised Device divisions. The transaction attempt(s) can match different rules, according to the selected parameter.
Mocked device data parameters and relevant rules in the Risk Management component | |
Risk Management component rule | Description |
|---|---|
Selected parameter: Rooted | |
Rooted device high amount (High) | If the user attempts to carry out the transaction with a rooted device and the transaction amount is higher than 100.00, the Intelligent Adaptive Authentication service will decline the transaction. |
Rooted device detected (High) | If the user attempts to carry out the transaction with a rooted device and the transaction amount is lower than 100.00, the Intelligent Adaptive Authentication service will either decline the transaction or prompt a challenge for Face Recognition authentication. |
Selected parameter: Hooking framework | |
Hooking Framework detected high amount (High) | If a hooking framework has been detected and the transaction amount is higher than 100.00, the Intelligent Adaptive Authentication service will decline the transaction. |
Hooking Framework detected (Medium) | If a hooking framework has been detected and the transaction amount is lower than 100.00, the Intelligent Adaptive Authentication service will prompt a challenge for Face Recognition authentication. |
Selected parameter: Application repackaging | |
Application repackaged detected high amount (Medium) or Application repackaged detected (Medium) | If a device, for which application repackaging has been used, is detected, the Intelligent Adaptive Authentication service will decline the transaction, independent of transaction amount. |
Selected parameter: Library injection | |
LibraryInjection detected high amount (Medium) or LibraryInjection detected (Medium) | If a device with library injection is detected, the Intelligent Adaptive Authentication service will decline the transaction, independent of transaction amount. |
Selected parameter: Secure element | |
Secure element not supported high Amount (Low) or Secure element not supported (Low) | If a device, for which no secure element could be detected, is used, the Intelligent Adaptive Authentication service will decline the transaction, independent of the transaction amount. |
To complete the transaction, if not declined, the mobile app will prompt Ms Doe for the protection type to validate the action.
Was this article helpful?