WSO2 is now Choreo LabsLearn more

Trusted AI Governance
Build

Create agents and AI apps with the tools and languages your teams already use.

Connect

Link agents securely to your APIs, data, models and business systems.

Run

Deploy, observe and operate agents and AI apps reliably at any scale.

Govern

Control identity, access, cost and policy for every agent in production.

Agent Management

Developer Platform

  • API Management Cloud

    Design, secure and publish APIs with governance and analytics built in.

    Sign Up Now
  • Integration Cloud

    Connect apps, data and AI agents with low-code and pro-code integration.

    Sign Up Now
  • Identity & Access Management Cloud

    Secure sign-in and access for customers, partners, workforce and agents.

    Sign Up Now
  • Agent Management Cloud

    Build, run and govern AI agents with full visibility and control.

    Sign Up Now
  • Developer Platform Cloud

    Ship cloud-native apps faster on an internal developer platform.

    Sign Up Now

Self-Hosted

Full control over your stack. Deploy directly to your own servers, bare metal, cloud, or Kubernetes environment. Your data never leaves your perimeter.

Product Downloads
Choreo Labs
AI Governance
Platform
Solutions
Resources
Article

Customer IAM (CIAM) - turning identity data into gold!

Transforming the customer experience is at the heart of digital transformation. Digital technologies are changing the game of customer interactions, with new rules and possibilities that were unimaginable few years ago. Customer Identity and Access Management (CIAM) is an emerging area in IAM, which is an essential ingredient for creating digital customer experiences. Today’s increasingly sophisticated customers view digital interactions as the primary mechanism for interacting with brands and, consequently, expect deeper online relationships delivered simply and seamlessly.

Furthermore, customers expect some control around how firms collect, store, manage, and share their profile data. With competition only a click away, your firm’s misuse of customer data, whether deliberate or inadvertent, can significantly damage brand equity. Yahoo! was in the middle of a series of data breaches in the last couple of years, exposing personal information of more than 1 billion users and this cost the company $350 million. Yahoo had to lower the sales price of its email and other digital services to Verizon Communications from $4.83 billion to $4.48 billion to account for the potential backlash from the data breaches.

The role CIAM plays in an enterprise today has the same weight a business API had in the industry for several years. In 2013, 90% of Expedia’s business was coming through its APIs. Salesforce generates almost 50% of its annual $3 billion in revenue through APIs, while at eBay APIs contribute 60% to the annual revenue. In the same capacity in which APIs became the public face of your company, CIAM drives revenue growth by leveraging identity data to acquire and retain customers. It’s your new public face!. CIAM builds a layer of interactions with the customer — or in other words, CIAM drives the layer of interactions with the customer.

According to the latest Forrester report on CIAM, 67% of the Asia Pacific market, 64% of North America market and 54% Europe market have adopted CIAM.

Workforce IAM vs. CIAM

Customer focused IAM systems are different from their traditional IAM (Workforce IAM) counterpart. Workforce IAM looks inward. It focuses on B2E (business-to-employee) and B2B (business-to-business) interactions. The goal of workforce IAM is to reduce the risk and cost associated with on-boarding and off-boarding new employees, partners, and suppliers, while the purpose of customer IAM (CIAM) is to help drive revenue growth by leveraging identity data to acquire and retain customers. If CIAM processes are cumbersome, customers will go to your competitors where these processes are more streamlined or easier to use. The same is not true of employees. Very few employees leave their employer because business-to-employee (B2E) IAM processes are archaic or difficult to use.

On-boarding

In B2E IAM, on-boarding is the responsibility of the employer, while in B2C mostly it’s self service. In other words, for employees, it's the HR department who initiates the employee on-boarding process and remains the owner of user accounts, while for customers, it can be any of the following cases:

  • A person who anonymously shows interest in products and services offered by your company. For example, this person may visit the Toyota website and look for all the Corolla models under lease. This is useful information to nurture an anonymous visitor such as this to a customer. You will have no clue who this person is, but track when the same person visits the site repeatedly via cookies, and personalize the site to fit to his/her expectations — which could possibly lead him/her to engage with the company.
  • A person who fills the contact form for an inquiry or to use free services offered by the company, by simply sharing their contact information. For example, a user may download a product or a white-paper by providing his/her contact information. Or per person may register for a company event by completing an online form. You will probably not call this person a customer — rather a lead. Leads are defined as people who may be interested in your product or service. The hope is they will eventually become a customer.
  • A person who has bought some product or service from your company — and now wants to signup to consume the company’s services online. There is an account verification involved in this process, to make sure that it's the same customer who bought the product or service before, who's now signing up. Account verification is part of the know your customer (KYC) process. KYC is the process of a business identifying and verifying the identity of its clients. The term is also used to refer to bank and anti-money laundering regulations which govern these activities. Support for know your customer/account verification is a key part of a CIAM system, triggered during the on-boarding process.
  • A person who signs up directly with the company through an online portal. Many e-commerce applications and online retailers follow this approach.
  • A person who signs up via a known public identity provider. This vastly reduces the initial barrier for registration — and there are multiple studies which confirm the huge success rate in user registration after integrating with known public identity providers (such Facebook, Google, and Microsoft Live).

In a CIAM system, most of the time on-boarding happens via an online registration form. Even in the case where you fetch user attributes required for registration via a third party identity provider, the last leg of the registration will include some sort of a form submission. The user experience of the customer on-boarding portal is among the top priorities of a CIAM system.

Security vs. usability is a long lasting debate. Finding the right balance is extremely hard. Someone I met from the Google Chrome security team mentioned  that they can spend months collecting feedback for merely changing the colors and find the right alignment of the text on the Chrome page displayed to the user - and they discover that the public certificate of a web site is not valid. To avoid automated form submissions and spam, many on-boarding portals use a CAPTCHA. A CAPTCHA plays a key role in customer conversion rates. People hate spam — but people hate CAPTCHA too! Over the time it’s been proven that even the hardest CAPTCHAs can be solved by state of art machine learning algorithms. There are many companies who have shared their experience with CAPTCHA — and one thing in common is — after introducing CAPTCHA, the customer conversion rate has rigorously decreased. With the new reCAPTCHA from Google, a significant number of users can now attest they are human without having to solve a CAPTCHA. Instead, with a single click they’ll confirm they are not a robot. The Google reCAPTCHA takes-away most of challenges enterprises face in customer on-boarding — and provides the right balance between usability and security.

Progressive Profiling

A CIAM system provides ingredients to nurture an anonymous user to a well-known customer. Progressive profiling is the process by which a system learns about a customer in a progressive manner. First, the anonymous user is just a visitor to the company web site. His/her preferences can be tracked via cookies and the company can promote content that is interesting to him/her. At one stage, the anonymous user will become a lead, by completing a contact form. Now the CIAM system has the opportunity to link all the preferences tracked against the anonymous user with the new lead. Over time the preferences of the lead can be tracked in a more meaningful way — and the company’s marketing/sales team can work in a collaborative manner to make him/her a customer. At this point you collect the most reliable data about the customer — with proper verification. From there onwards, the CIAM system will keep tracking customer preferences — and will produce more meaningful data to company management to make much informed decisions. Once the customer decides to sign up with credentials (may be to use the company’s online portal), the CIAM system has the opportunity to track and relate all user interactions together to build one unified user profile.

Authentication

Authentication in a CIAM system differs in many ways from a traditional IAM (workforce IAM) system. Let’s walk through the differences and the similarities:

  • Social login is a key success factor in CIAM and a good CIAM system should support login with multiple social identity providers. 88% customers in the US claim to have logged into a web site or a mobile application using social login. Workforce IAM systems do not encourage social login — it’s treated as a high risk factor as the enterprise has no control over how the user credentials are stored and managed by a 3rd party identity provider. The same risk factor is present even in CIAM. But, then again, it’s a compromise between convenience and security. It also depends on which vertical we are talking about - for example, financial institutions do not even worry about integrating social login.
  • Strong authentication is encouraged both in CIAM and workforce IAM. Workforce IAM systems rely on hardware tokens for MFA (multi-factor authentication), while at a large scale CIAM systems use soft tokens like OTP over SMS/Email or TOTP (Google Authenticator). Both Google and LinkedIn use FIDO U2F internally for employee authentication. FIDO U2F is on its way to becoming the de facto standard for multi-factor authentication. Yubico is one of the top vendors that build FIDO U2F compliant security keys. Eventhough FIDO is not mainstream in the CIAM market yet, with the support from Google and Facebook, it shows some promise in the mass market.
  • 41% of customers in the US are interested in password-less authentication. Almost all consumer mobile applications produced by vendors in financial, retail, and airline domains  have supports login with touch ID.
  • Risk-based authentication is a non-static authentication system which takes into account the profile of the agent requesting access to the system to determine the risk profile associated with that transaction. The risk profile is then used to determine the complexity of the challenge. Based on risk factors, the system will decide whether to use SMS OTP — or use knowledge based authentication (KBA). To determine the risk of the transaction — the authenticate system may use a risk engine, which takes into the consideration, the geographical location where the transaction is initiated from, the frequency, the value of the transaction, and many other things.
  • Workforce IAM systems use stricter account locking policies  compared to CIAM systems in instances of failed login attempts. CIAM systems may use a CAPTCHA or an auto unlock after some time. Workforce IAM systems probably need the IAM administrators' help to unlock an account.
  • Single Sign On (SSO) is a must in a CIAM system when you have multiple portals to perform business functions. For example, if you are a PG&E (The Pacific Gas and Electric Company) customer, you might have noticed that when you want to view your current electricity/gas usage, you are redirected to opower.com from the pge.com — but you retain the same login session. Also, if you are a publisher with multiple news publications, you will let your customers browse between them with a single login session.

Self-service Portal

The audience of the self-service portal in a CIAM system is the customer. It is the one-stop shop for a customer to view/update his/her profile, manage consent given to third party applications, reset password, manage credentials, manage preferences, configure account recovery options, view concurrent login sessions, view activity logs, request for a data export, associate social login, etc. Security and compliance are two important aspects in CIAM. If you are familiar with the General Data Protection Regulation (GDPR), you might have already noticed that some of the self-service portal functions listed above are driven by it.

About Author

Prabath Siriwardena

Senior Director - Security Architecture - Choreo Labs

Prabath is the Vice President - Security Architecture at WSO2. Prabath has over 11 years of industry experience that currently involves providing security architecture solutions to many of WSO2’s key customers.

Read Prabath's Blog
https://blog.facilelogin.com

Follow Prabath on Twitter
https://twitter.com/prabath