808bits

RSA BSAFE® Crypto-J JSAFE and JCE Software Module 6.2.4

FIPS 140-2 certificate #3184 · Dell Inc. · data as of 2026-08-28
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

Certificate

Certificate number3184
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorDell Inc. · website
Software versions6.2.4

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. 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

AlgorithmCAVP certificate
AES5026
CKGvendor affirmed
CVL1570, 1571, 1572
DRBG1841
DSA1321
ECDSA1283
HMAC3340
KAS156
KTS
KTSvendor affirmed
PBKDFvendor affirmed
RSA2711
SHS4085
Triple-DES2591

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits or 128 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #1570, key agreement; key establishment methodology provides between 112 bits and 256 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • Google(TM) ART(TM) JRE 8.0 on Google Android(TM) 7.1.2 ARMv8 (64 bit) running on Google Nexus(TM) 5X with a Qualcomm(R) Snapdragon(TM) processor
  • OpenJDK 8.0 on CentOS 7.3 (64-bit) running on Dell PowerEdge(TM) with an Intel Xeon(R) processor (single-user mode)
  • Oracle(R) JRE 8.0 on Microsoft(R) Windows(R) 10 (64-bit) running on Dell(TM) Optiplex(TM) with an Intel(R) Core(TM) i5 processor

Validation history

DateTypeLab
2018-05-22InitialGossamer 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: 2018-05-22, 2020-11-23

Source documents