Name: Getting Started with Risk-Based Authentication in SAP Customer Data Cloud
Uploaded: 2022-10-5
Duration: 265 s
Description: In this video, you’ll get an overview of Risk-Based Authentication in SAP Customer Data Cloud and how it can be used to heighten the security of your application.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div>In this video, you’ll get an overview of Risk-Based Authentication in SAP Customer Data Cloud and how it can be used to heighten the security of your application.</div></div></div></div></div></div>

Getting Started with Risk-Based Authentication in SAP Customer Data Cloud

In this video, you'll get an overview of risk based authentication and how it can be used to heighten the security of your application. With SAP Customer Data Cloud's risk based authentication feature. You can increase the security level of every log in when a user exhibits risky behavior. By stepping up their level of authentication. Risk based authentication, or RBA, is an added layer of account security, which can prevent malicious attacks and hacking attempts on your sides. It calculates the level of risk associated with a given login attempt and presents users with authentication challenges according to that risk level. Ava includes three types of rules to determine the risk level and its outcome. Global rules, which apply to all login attempts in your site or site groups. Account rules sets which apply to individual accounts and policy, which can be applied to specific scenarios. When you configure RPA rules, you will first have to select a risk factor or risk factors are events that can trigger a higher level of authentication, such as unsuccessful login attempts to the same accounts or to different accounts from the same IP address. Percentage of failed logins triggered after a specific number of attempts. A new device useful again where first login from a different country. You can choose all of these items or a subset of them in the console. You can create over rules based on existing RBA rule templates, or create a new custom rule from scratch without using any of the existing templates. The next step is to define what action to take when the risk factor event is triggered. SAP Customer Data Cloud allows you to apply the following security methods for a login attempt Captcha. This requires that users successfully pass a Captcha challenge, thereby preventing account hacks via automated login attempts. Two factor authentication. This requires that users passed two steps of authentication. The first step is providing a password when initially logging in, and the second step is providing an authentication code which users receive on their mobile device. Out. This looks out the user or IP address for a specified length of time, and multi-factor authentication via scripting. Authentication levels are associated with each authentication methods by their degree of security. A higher authentication level is considered more secure, so when defining rules, assign a higher required authentication level for more suspicious behavior. For example, you can define that when a user tries to login from a new country, they have to pass a two factor authentication with a level of 20. This would mean authenticating via an SMS or using an authenticator app. Users can also opt in to push notifications after opting in. The regular logic of RBA is applied to user login flows with the push notification used as a second factor. Authentication. For example, when the user tries to login from another device like a desktop, they use a receives a push notification to their mobile phone and can complete the login only after approving the notification. SAP Customer Data Cloud allows you to add Captcha challenges and two factor authentication to your login and registration. Screen. Says it supports Google Captcha solutions, including reCAPTCHA, an invisible reCAPTCHA for all screens. Risk based authentication errors can be viewed by date range in the audit log of the CDC console. The audit log displays all log entries for failures such as login failure and account locked out. You can also search for all errors of a particular user by using their UID and a custom query. This ends our overview of SAP Customer Data Cloud's risk based authentication.