2.5 Distinctive Use Cases of OARM
You can use the OARM User Authentication activity, in conjunction with out-of-the-box rules to perform a wide range of tasks.
- Risky IP use cases where the Administrator wants to configure IP addresses that are considered as risky for the organization. See Configuring a Risky IP Use Case in Oracle Adaptive Risk Management tutorial for detailed instructions on using this rule in OARM.
- Geo-velocity use cases where the Administrator wants to configure access for authentication of a user based on the distance and the time gap between the users current location and where they last logged in from. See Configuring a Geo-Velocity Based Use Case in Oracle Adaptive Risk Management tutorial for detailed instructions on using this rule in OARM.
In addition to the out-of-the-box User Authentication activity, Administrators can create their own custom activities and create rules using the information collected from it. Rules are customized according to business needs. These rules can be transactional in nature, monitoring various aspects of the user activity that the business is interested in. Some examples of custom activities are internet banking or bill paying in a banking application. You can add rules that use the information, like the amount involved in the payment, user information, and so on to identify a fraudulent money transfer. See Configuring a Custom Activity Use Case in Oracle Adaptive Risk Management tutorial for detailed instructions on configuring a custom activity in OARM.
For more information on these use cases, see Key Use Cases of OARM for Enhanced Security and Risk Mitigation.