808bits

RSA BSAFE® Crypto-J Software Module

FIPS 140-2 certificate #1047 · 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 FIPS mode

Certificate

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

Module description

RSA BSAFE Crypto-J security software is designed to help protect sensitive data as it is stored using strong 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
AES670
DSA252
ECDSA73
HMAC354
RNG390
RSA312
SHS703
Triple-DES615

Other algorithms

AES-GCM (non-compliant); DES; Diffie-Hellman; DESX; ECAES (non-compliant); EC Diffie-Hellman; ECDHC; ECIES; MD2; MD5; PBE (SHA-1 and Triple-DES); RIPEMD 160; RNG (X9.31 non-compliant, MD5 and SHA-1); RC2; RC4; RC5; RSA OAEP (for key transport); Raw RSA; RSA Keypair Generation MultiPrime; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); HMAC-MD5

Tested configurations

  • 32-bit x86 Intel Pentium M w/ Windows XP SP2 Professional with Sun JRE 1.4.2
  • 32-bit x86 Intel Pentium M w/ Windows XP SP2 Professional with Sun JRE 1.5
  • 32-bit x86 Intel Pentium M w/ Windows XP SP2 Professional with Sun JRE 1.6 (single-user mode)

Validation history

DateTypeLab
2008-10-27InitialSAIC-VA
2009-01-26Update
2010-09-07UpdateSAIC-VA
2011-03-28UpdateSAIC-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: 2008-10-27, 2009-01-26, 2010-09-07, 2011-03-28, 2013-01-24

Source documents