This guide provides information about how to use CA RiskMinder (referred to as RiskMinder later in the guide) Web services to enable your online application to programmatically perform risk evaluation and related tasks. This document describes the Web services implementation of RiskMinder.
RiskMinder is an adaptive authentication solution that evaluates each online transaction in real time by examining a wide range of collected data against the configured rules. It then assigns each transaction a risk score and advice. The higher the risk score, the greater is the possibility of a fraud, the negative is the advice. Based on your business policies, your application can then use this risk score and advice to approve or decline a transaction, ask for additional authentication, or alert a customer service representative.
RiskMinder offers you the flexibility to modify the configuration parameters of any of the risk evaluation rules in keeping with your policies and risk-mitigation requirements. It also gives you the flexibility to modify the default scoring configurations, scoring priorities, and risk score for any rule and selectively enable or disable the execution of one or more rules.
Besides pre-configured out-of-the-box rules, RiskMinder’s field-programmable custom rules capability allows for industry-specific rules to be selectively deployed and augmented based on your requirements.
Note: See "Understanding RiskMinder Basics" in the CA RiskMinder Installation and Deployment Guide to understand the basic concepts of RiskMinder and its architecture.
This section discusses the Web services provided by RiskMinder, the checks that you must perform before implementing the Web services, and steps to generate Java client stubs. It covers the following topics:
Note: CA RiskMinder still contains the terms Arcot and RiskFort in some of its code objects and other artifacts. Therefore, you will find occurrences of Arcot and RiskFort in all CA RiskMinder documentation. In addition, some of the topics in this guide do not follow the standard formatting guidelines. These inconsistencies will be fixed in a future release.
|
Copyright © 2013 CA.
All rights reserved.
|
|