Many of today’s leading smartphones, including the Apple iPhone and Samsung Galaxy, come with native face and fingerprint authentication technologies. We expect this trend to continue with all devices. As device manufacturers continue to make biometric security hardware standard, we believe that the right approach is to utilize these native capabilities for RSA SecurID Access. This helps to ensure that your end-users have a consistent and familiar experience, whether they are using these devices for purchasing products online or logging into their corporate email accounts.

Recognizing this, we have consolidated support for biometrics into a single authentication option called Device Biometrics. When you configure your assurance levels, you can choose Device Biometrics, which currently supports iOS Touch ID and Face ID and Android fingerprint authentication.

As part of this effort, as of March 27, 2018, we have decided to remove the Eyeprint ID option in the RSA SecurID Authenticate for iOS and Android apps and the Cloud Authentication Service.  Eyeprint biometric data stored within the Authenticate app on these devices will be removed as part of this update. As a reminder, RSA does not store any biometric data in the Cloud Authentication Service.

All other authentication options, such as Approve, SecurID Token, Voice Tokencode, and many more, continue to function the same. You are welcome to adjust the authentication options to meet your organizational needs. Refer to the following topic for information on how to modify your authentication options in assurance levels: https://community.rsa.com/docs/DOC-54071.

By adding support for native device biometric authentication, RSA SecurID Access enables organizations and their end-users to take advantage of these authentication options for securely accessing their enterprise applications. This approach further complements RSA’s risk-based analytics with device-level capabilities that can be leveraged for higher levels of identity assurance.

If you have any questions about this change, please contact RSA Support. Thank you.