Integrate with PingOne Protect for risk evaluations

Applies to:

Ping SDK for Android
Ping SDK for iOS
Ping SDK for JavaScript

The Ping SDKs can integrate with PingOne Protect to evaluate the risk involved in a transaction.

PingOne Protect is supported in the following servers:

Advanced Identity Cloud: Use the official PingOne Protect nodes
PingAM 7.5 and later: Use the official PingOne Protect nodes
PingAM 7.2 - 7.4: Use the marketplace PingOne Protect nodes

A flowchart illustrating how risk predictors evaluate many different data points to determine whether to allow a user access or prompt mitigation.

Figure 1. A flowchart illustrating how risk predictors evaluate many different data points.

You can instruct the Ping SDKs to use the embedded PingOne Signals SDK to gather information during a transaction. Your authentication journeys can then gather this information together and request a risk evaluation from PingOne.

Based on the response, you can choose whether to allow or deny the transaction or perform additional mitigation, such as bot detection measures.

You can use the audit functionality in PingOne to view the risk evaluations:

Figure 2. Risk evaluation records in the PingOne audit viewer.

Steps

Step 1. Set up the servers: In this step, you set up your PingOne Advanced Identity Cloud or PingAM server, and your PingOne instance to perform risk evaluations.

For example, you create a worker application in PingOne and configure your server to access it. You also create an authentication journey that uses the relevant nodes.
Step 2. Install dependencies: In this step, you add the required PingOne Protect module and dependencies to your project.

We provide instructions for Android, iOS, and JavaScript projects.
Step 3. Develop the client app: With everything prepared, you can now add Ping SDK code to your client application to evaluate risk by using PingOne Protect.

You’ll learn how to initialize the collection of contextual data, gather and send it to the server for a risk evaluation, and how to pause and resume behavioral data collection.