Skip navigation
All Places > Products > RSA BSAFE > Blog

RSA BSAFE

2 posts

It has been more than a year since I announced that RSA is extending support for its BSAFE toolkits. See my previous post here

 

RSA is actively addressing issues and adding new algorithm support, from adding new SHA-3 support, supporting JDK or JSSE properties, implementing control of algorithms and key sizes, to keeping the platform support updated, in order to keep RSA, Dell EMC, and all our customers' products as secure as possible.

 

We have released new versions of SSL-J, Crypto-J, Micro Edition Suite, and Crypto-C Micro Edition (CCME) to address security vulnerabilities, and to add new algorithms and ensure our modules remain FIPS 140-2 validated.

 

RSA has submitted both CCME 4.1.4 and Crypto-J 6.2.5 to NIST Cryptographic Module Validation Program, CMVP, for FIPS validation some months ago already. According to CMVP's Module In Process list, the review of CCME started around the first week of October. The status of Crypto-J is still Pending Review. CMVP has quite a backlog of modules to review so we appreciate your patience while CMVP do their best to review all submissions.

 

We are making the new releases available to our entire customer base under a valid BSAFE maintenance contract. If you have not yet renewed your support contract to benefit from these new releases, contact RSA Support by sending an email to support@rsa.com.

 

 

Cheers,

François

RSA BSAFE Product Manager

Have you heard that RSA is extending support for BSAFE products? This is now official and has been posted as a Product Advisory at RSA announces support extension for some of the BSAFE® product suite  

 

What this means is that if you haven't made the switch to an alternate FIPS-validated crypto module now is the time to benefit from a bit more time to migrate while staying secure. All we ask is that you are on the most recent version of CCME, MES, Crypto-J, SSL-J or Cert-J.

 

Why? Because security is not stagnant. Cryptography evolves. Algorithms considered secure today may not be secure tomorrow. If you are security-conscious, you always keep your own devices up-to-date. You press that "Update Now" button because as a user you know the updated version of your app or your operating system will be a bit better. A bit more stable. A bit more secure. A bit faster. All this makes sense as you trust the app vendor and your operating system vendor.

 

If you are one of those mobile app, OS or product vendors that incorporates a cryptographic module in your code, there is no "Update Now" button. But you should still "update now" any time this is possible for the same reasons you update your devices. A bit better. A bit more stable. A bit more secure. A bit faster. To that I will also add that most recent versions of our BSAFE product suite support most recent Operating Systems, JDK, compilers, etc. We are also adding new algorithms as RSA, Dell EMC and Dell Technologies will continue investing in BSAFE to keep our products secure when used. The new algorithms we are adding into BSAFE may eventually end up in public releases between now and January 2022 so you, as customers, can also benefit from them.

 

François

RSA BSAFE Product Manager