How Highly Regulated Identity can be used
Safeguard sensitive customer operations such as updating account information, admin or security settings, accessing sensitive data or apps, sending money, making an open banking payment, and more.
Strong Customer Authentication (SCA) lets users review and approve sensitive operations in real time. Dynamic Linking ties transaction details to the SCA approval confirmation to help prevent transaction tampering.
A certified FAPI 1 Advanced security profile implementation to ensure data privacy and app security. FAPI protects the end-to-end flow against cyber and fraud risks like transaction tampering. (FAPI is the Financial Grade API working group at the OpenID Foundation).
Here’s when the magic of the Customer Identity Cloud kicks in: customizing is easy. Simply use Actions to run custom policy and adopt new UX templates for the MFA waiting screen and custom consent screen. Easy, right?
CIBA (Client Initiated Back-channel Authentication) allows user authentication to be initiated by a backend application instead of the user device. This way, for out-of-band interactions, you can skip the often-forgotten, less secure verification questions. With CIBA, call center agents, for example, can send an authentication request right to the end user's device, so they can verify their identity with a single tap.
Some organizations have stricter compliance and audit policies that require them to have complete control over their encryption keys. Customer Managed Keys is our way of tackling this. You can import self-generated keys for encryption and rotate and rekey tenant keys.