How to set up Image-Based Behavioral Identity Check (Image Note Assertion)

The feature introduces a simple, personalized challenge that verifies identity using user-specific choices made during registration.

Users select an image and provide a personal note during signup. During login, after entering their username, they must select the same image and re-enter the note. Access is granted only if both match the stored data.

This step adds a behavioral layer to authentication, enhancing security through personalized verification.

1. Configure the Image-Based Behavioral Identity Check

   1. Log in to the ZTrust Admin Console and select the realm you want to configure.

      

      
   2. Go to the Authentication section

      
   3. Next, create a copy of the browser authentication flow and configure the Image Note Assertion step within it.

      
   4. It should be configured as shown below.

      
   5. Next, configure the flow for registration. Return to the Authentication section to proceed.

      
   6. Navigate to the Required action tab

      
   7. Then enable the Image note assertion like below

      
   8. Now configuration is completed. We will attempt to register and log in to the self-service portal.

2. Registration

   1. If a user does not exist in ztrust, please register as a user by providing below details.

      
   2. After filling in all the required fields, the user is directed to the next page where they must select an image and provide a prompt.

      
   3. For example, the user selects an image, enters a note, and then submits the information.

      
   4. User successfully created in ZTrust.

3. Login

   1. The user created in ZTrust will now attempt to log in with the same user. After successful validation, they are redirected to the next page for personal note verification.

      

      
   2. If the personal note is incorrect, an error message will be displayed as shown below.

      
   3. If the correct image and corresponding prompt are selected, ZTrust grants access to the user

      
   4. User successfully logged into to the SSP