RSA BSAFE Alternative Product Options

Document created by RSA Link Team Employee on Sep 26, 2016
Version 1Show Document
  • View in full screen mode

Summary:

Customers seeking alternative products or migration options may wish to consider the following:

  • CCME: CCME users may consider OpenSSL. A FIPS 140 validated version of OpenSSL is currently under development. Customers can also choose to take OpenSSL through FIPS 140 validation themselves. An alternative option is Mocana Corporation’s FIPS 140 validated NanoCrypto library.

  • MES: MES users may consider OpenSSL. An alternative option is Mocana Corporation’s NanoSSL library.

  • Crypto-J: Crypto-J users using the standard JCE API may consider the Sun JCE Provider, which is the most prevalent available option. Alternative options include the IBM JCE Provider which is FIPS 140 validated, and the Legion of Bouncy Castle. Customers using the custom legacy API should be aware that they will need more effort to transition.

  • SSL-J: SSL-J users using the standard JSSE API may consider the Sun JSSE Provider, which is the most prevalent available option. An alternative option is the IBM JSSE Provider. Customers using the custom legacy API should be aware that they will need more effort to transition.

  • Cert-J: Cert-J users may consider the Sun JCE Provider. An alternative option is the IBM JCE Provider. Customers using the custom legacy API should be aware that they will need more effort to transition.

 

For additional documentation, downloads, and more, visit the RSA BSAFE page on RSA Link.

 

EOPS Policy:

RSA has a defined End of Primary Support policy associated with all major versions. Please refer to the Product Version Life Cycle for additional details.

Attachments

    Outcomes