808bits

RSA BSAFE® Crypto-J JSAFE and JCE Software Module

FIPS 140-2 certificate #1502 · RSA, The Security Division of EMC · data as of 2026-08-28
Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS140_MODE or FIPS140_SSL_MODE

Certificate

Certificate number1502
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorRSA, The Security Division of EMC · website
Software versions5.0 or 5.0.1

Module description

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

AlgorithmCAVP certificate
AES1465, 1766
DRBG57, 117
DSA464, 552
ECDSA182, 236
HMAC863, 1036
RNG802, 940
RSA717, 881
SHS1328, 1549
Triple-DES988, 1143

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 SP3 with Sun JRE 5.0
  • Microsoft Windows XP SP3 with Sun JRE 6.0 (single-user mode)

Validation history

DateTypeLab
2011-02-24InitialSAIC-VA
2011-03-28UpdateSAIC-VA
2011-09-19UpdateSAIC-VA
2013-01-24Update

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: 2011-02-24, 2011-03-28, 2011-09-19, 2013-01-24

Source documents