808bits

RSA BSAFE® Crypto-J Toolkit Module

FIPS 140-1 certificate #289 · RSA, The Security Division of EMC · data as of 2026-09-13

RSA BSAFE® Crypto-J Toolkit Module, from RSA, The Security Division of EMC, holds FIPS 140-1 certificate #289 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. Validation Sunsetting Policy - FIPS 140-1 Certificate. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number289
StandardFIPS 140-1
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorRSA, The Security Division of EMC · website
Software versions3.3.4.2

Module description

Quoted from the NIST CMVP entry for this certificate.

The Crypto-J Module is a Java-language software development kit that allows software and hardware developers to incorporate encryption technologies directly into their products. The tested Crypto-J Module is a Java-language API available as a Java ARchive, or JAR, file.

Security level exceptions

  • Operating System Security: Tested as meeting Level 1 with Windows NT SP 6 (single user mode), JVM v1.3.1, JRE v1.3.1

Approved algorithms (5)

AlgorithmCAVP certificates
AES45
DSA63
RSAvendor affirmed
SHA-197
Triple-DES112

Other algorithms

DES (Cert. #168); DESX; RC2; RC4; RC5; MD2; MD5; HMAC-SHA-1 (Cert #97); Diffie-Hellman (key agreement); Base64

Validation history

DateTypeLab
2003-02-04InitialSAIC-VA
2004-10-01Update
2004-12-14Update
2004-12-16Update
2008-01-04Update
2008-10-16Update
2010-09-07UpdateSAIC-VA
2011-03-28UpdateSAIC-VA
2013-01-24Update
2016-02-12UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab

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: 2003-02-04, 2004-10-01, 2004-12-14, 2004-12-16, 2008-01-04, 2008-10-16, 2010-09-07, 2011-03-28, 2013-01-24, 2016-02-12

Source documents