808bits

RSA BSAFE(R) Crypto-J JSAFE and JCE Software Module

FIPS 140-2 certificate #2469 · Dell Inc. · data as of 2026-10-21

RSA BSAFE(R) Crypto-J JSAFE and JCE Software Module, from Dell Inc., holds FIPS 140-2 certificate #2469 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS Mode. No assurance of the minimum strength of generated keys

Certificate

Certificate number2469
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorDell Inc. · website
Software versions6.2 and 6.2.1.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 strong encryption techniques to provide a persistent level of protection. It supports a wide range of industry standard encryption algorithms offering Java developers the flexibility to choose the option most appropriate to meet their requirements.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Physical Security: N/A
  • Design Assurance: Level 3

Approved algorithms (11)

AlgorithmCAVP certificates
AES3263
CVL471, 1024
DRBG722
DSA932
ECDSA619
HMAC2062
KTS
PBKDFvendor affirmed
RSA1663
SHS2701
Triple-DES1852

Other algorithms

AES (non-compliant); DES; DESX; Diffie-Hellman (CVL Cert. #1024, key agreement); EC Diffie-Hellman (CVL Cert. #1024, key agreement); ECIES; RNG (non-compliant); HMAC-MD5; MD2; MD5; PKCS#5; PKCS#12; RC2; RC4; RC5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength); RSA (non-compliant); RIPEMD160; scrypt; Shamir Secret Sharing; Triple-DES (non-compliant)

Tested configurations

  • Google Dalvik(tm) JRE 6.0 on Google(tm) Android(tm) 4.1.2 ARMv7 (32-bit) running on Google Nexus 7(tm) (Wi-Fi, 2012)
  • OpenJDK 8.0 on CentOS 6.7 (64-bit) running on a Dell(TM) PowerEdge(TM) (single-user mode)
  • Oracle(R) JRE 8.0 on Microsoft(R) Windows 8.1 (64-bit) running on an HP ENVY 15

Validation history

DateTypeLab
2015-10-30InitialGossamer Security Solutions
2016-04-12UpdateGossamer Security Solutions
2017-01-24UpdateGossamer Security Solutions
2017-02-09UpdateGossamer Security Solutions
2020-11-23UpdateGossamer Security Solutions

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: 2015-10-30, 2016-04-12, 2017-01-24, 2017-02-09, 2020-11-23

Source documents