808bits

RSA BSAFE Crypto-J JCE Provider Module

FIPS 140-2 certificate #595 · RSA, The Security Division of EMC · data as of 2026-09-15

RSA BSAFE Crypto-J JCE Provider Module, from RSA, The Security Division of EMC, holds FIPS 140-2 certificate #595 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.

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 number595
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorRSA, The Security Division of EMC · website
Software versions3.5

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 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 (7)

AlgorithmCAVP certificates
AES271
DSA140
HMAC86
RNG106
RSA71
SHS356
Triple-DES354

Other algorithms

DES (Cert. #326); Diffie-Hellman (key agreement, key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); DESX; MD2; MD5; RIPEMD 160; RNG (ANSI X9.31, MD5, SHA1; non-compliant); RC2; RC4; RC5; PBE (SHA256, SHA384, SHA512); Raw RSA; RSA Keypair Generation MultiPrime; RSA (key wrapping, key establishment methodology provides between 112 bits and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); HMAC-MD5

Tested configurations

  • Windows XP Professional SP2 with Java JRE 1.4.2 (in single user mode)

Validation history

DateTypeLab
2005-12-01InitialSAIC-VA
2006-03-06Update
2007-10-12Update
2008-01-04Update
2008-10-16Update
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: 2005-12-01, 2006-03-06, 2007-10-12, 2008-01-04, 2008-10-16, 2010-09-07, 2011-03-28, 2013-01-24

Source documents