Jumio
Overview
By combining Okta with Jumio, you can add document identity proofing to your registration workflow. Okta provides user registration and authentication, and Jumio can provide Identity Proofing services. Scanning government IDs, “live-proofing,” and other techniques help you gather additional information from online customers to gain more confidence that they are who they say they are.
Resources
The Challenge
- Identity fraud is at an all-time high, with account takeover tripling between 2016 and 2017*
- With the rise of data breaches and the dark web, enterprises need a higher level of assurance than personally identifiable information to protect against fraud
- Authenticating digital customers securely and quickly is a growing challenge for enterprises
The Solution
- By combining Okta with Jumio, you can add document identity proofing to your security arsenal
- Scanning government IDs, “live-proofing,” and other techniques ensure online customers are who they say they are
- AI-driven algorithms keep fraudsters out and let your customers in, with no unreasonable access hurdles
- Customers, now authenticated and identified in Okta, can then be granted secure access to apps and assets
Securely authenticate new account registrations
With the combination of Okta and Jumio in place, organizations can require customers attempting to open new accounts to first prove their identity, using a variety of methods that are easy to perform but difficult for fraudsters to spoof. These methods include scanning the front and back of a driver’s license or other government-issued ID card, taking and transmitting a “selfie,” and passing a liveness detection test requiring a new customer to follow a moving dot on their device (this provides additional protection against those trying to cheat the selfie test with a prior photo or video). Suspicious users can be given a Multi-Factor Authentication (MFA) challenge from Okta to further validate identity. In the majority of cases the combination of proofs can be submitted in under a minute. Once a legitimate customer completes the security actions, the desired new account will be opened; while fraudulent attempts to open an account will be blocked.
Provide step-up authentication for new service requests
When existing account holders digitally request new services, it represents another opportunity for fraud to come into play. But with Okta + Jumio, enterprises can assign users to groups (such as “existing customer accounts”), can centrally manage their access privileges, and can protect legitimate account holders from fraudulent account takeover by using ID proofing and step-up authentication during new service requests. For example, when an existing customer tries to open a new credit card, the finance company can use Jumio’s ID proofing and Okta’s MFA as additional layers of security to validate that this request is coming from the real customer, while denying fraudulent requests.
Use ID proofing to securely and easily authenticate customers at scale
- Enable efficient gatekeeping that lets legitimate users in but keeps fraudulent users out, automatically
- Minimize customer abandonment with an intuitive process that utilizes documents they already own
- Provide step-up authentication for questionable access requests with Okta Multi-Factor Authentication
- Protect registration, transactions, and customer access so security can scale with the enterprise
To learn more about this integration, contact us.
* https://www.javelinstrategy.com/press-release/identity-fraud-hits-all-time-high-167-million-us-victims-2017-according-new-javelin
Capabilities
Access
- OIDC OpenID Connect is an extension to the OAuth standard that provides for exchanging Authentication data between an identity provider (IdP) and a service provider (SP) and does not require credentials to be passed from the Identity Provider to the application.
- WS-Federation
- SAML Security Assertion Markup Language is an open standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP) that does not require credentials to be passed to the service provider.
- SWA Secure Web Authentication is a Single Sign On (SSO) system developed by Okta to provide SSO for apps that don't support proprietary federated sign-on methods, SAML or OIDC.
Provisioning
- Attribute Sourcing
- Create Creates or links a user in the application when assigning the app to a user in Okta.
- Update Okta updates a user's attributes in the app when the app is assigned. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app.
- Deactivate Deactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated. Accounts can be reactivated if the app is reassigned to a user in Okta.
- Sync Password Push either the users Okta password or a randomly generated password to the app. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password.
- Group Push Push existing Okta groups and their memberships to the application. Groups can then be managed in Okta and changes are reflected in the application.
- Group Linking Link Okta groups to existing groups in the application. Simplifies onboarding an app for Okta provisioning where the app already has groups configured.
- Schema Discovery Import the user attribute schema from the application and reflect it in the Okta app user profile. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema.
- Attribute Mastering The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile.
- Attribute Writeback When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. For example the user profile may come from Active Directory with phone number sourced from another app and written back to Active Directory.
