000034526 - New Release of  AA Cloud 12.2 Upgrade in RSA Adaptive Authentication (Cloud) 12.2

Document created by RSA Customer Support Employee on Dec 13, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000034526
Applies ToRSA Product Set: Adaptive Authentication (Cloud)
RSA Product/Service Type: Adaptive Authentication (Cloud)
RSA Version/Condition: 12.2
IssueAdaptive Authentication Cloud version 12.2 was successfully installed in Production on Sunday (Dec 4th).
This release started as an Adaptive Authentication On Premise release, however, during the work on this release we had to change the timeline and scope to enable the release of a smaller On Premise version as Beta to a Customer and another release to the RSA Production Cloud environment. (The team adjusted to these changes and managed to deliver these two versions on time. 
In addition, in this release we extended the team and added few team members from the India engineering group. This cooperation will continue in future releases.)
This release includes the following functionalities:
  • Eco System - The Eco System is part of a phased approach designed to enhance fraud detection by using data elements from different sources. The RSA Risk Engine can now consume data elements that are not predefined by RSA and use them for risk assessment.
RSA Adaptive Authentication (Cloud) 12.2 introduces the first phase of this approach in which the RSA Risk Engine uses 3rd party facts from the web and/or mobile channel, in addition to RSA’s predefined facts, to calculate a risk score.

The RSA Risk Engine is both dynamic and self-learning, allowing it to consume different types of data that may positively impact fraud detection.

  • Performance improvements - RSA has improved product infrastructure (Event Messaging) to enable higher availability and better response times.
  • Custom Facts Enhancement - RSA has increased the number of custom facts that you can send, up to 40, per SOAP API request.