RSA BSAFE Crypto-J Software Module
RSA BSAFE Crypto-J Software Module, from RSA, The Security Division of EMC, holds FIPS 140-2 certificate #1291 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.
Certificate
| Certificate number | 1291 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | RSA, The Security Division of EMC · website |
| Software versions | 4.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
RSA BSAFE Crypto-J security software is designed to help protect sensitive data as it is stored using encryption techniques to provide a persistent level of protection. RSA BSAFE Crypto-J supports a wide range of industry standard encryption algorithms offering Java developers the flexibility to choose the option most appropriate to meet their requirements.
Approved algorithms (9)
Other algorithms
ANSI X9.31 RNG (non-compliant); DES; DESX; Diffie-Hellman; ECAES (non-compliant); EC Diffie-Hellman; EC Diffie-Hellman with Cofactor; ECIES; HMAC-MD5; MD2; MD5; MD5Random; PBE; PBE with SHA1 and Triple-DES; RC2; RC4; RC5; RIPEMD160; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA Keypair Generation MultiPrime; RSA OAEP; SHA1Random
Tested configurations
- Microsoft Windows XP SP2 with Sun JRE 5.0
- Microsoft Windows XP SP2 with Sun JRE 6.0 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2010-04-12 | Initial | SAIC-VA |
| 2010-09-07 | Update | SAIC-VA |
| 2011-03-28 | Update | SAIC-VA |
| 2013-01-24 | Update |
Status timeline
As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.
- 2026-08-21: first observed by this tracker, status historical
- Validation dates on record: 2010-04-12, 2010-09-07, 2011-03-28, 2013-01-24