808bits

BC-FJA (Bouncy Castle FIPS Java API)

FIPS 140-2 certificate #3585 · Legion of the Bouncy Castle 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. No assurance of the minimum strength of generated keys

Certificate

Certificate number3585
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorLegion of the Bouncy Castle Inc. · website
Software versions1.0.0

Module description

The Bouncy Castle FIPS Java API is a comprehensive suite of FIPS Approved algorithms implemented in pure Java. All key sizes and modes have been implemented to allow flexibility and efficiency, and additional algorithms are available in non-approved operation as well.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3756
CVL704, 705, 706
DRBG1031
DSA1043
ECDSA804
HMAC2458
KAS73
KASvendor affirmed
KBKDF78
KTSvendor affirmed
KTS
KTS
PBKDFvendor affirmed
RSA1932
SHA-33
SHS3126
Triple-DES2090

Allowed algorithms

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

Tested configurations

  • Centos 6.4 with on Java SE Runtime Environment v8 (1.8.0) on vSphere 6 running on a Cisco UCSB-B200-M4 Blade with an Intel® Xeon® E5
  • Solaris 11 with on Java SE Runtime Environment v7 (1.7.0) on vSphere 6 running on a Cisco UCSB-B200-M4 Blade with an Intel® Xeon® E5
  • Ubuntu 14.04 LTS on Java SE Runtime Environment v8 (1.8.0) on VMWare ESXi 6.0 running on Simplivity OmniCube with an Intel® Xeon® E5 (single-user mode)

Validation history

DateTypeLab
2019-12-17InitialAcumen Security

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: 2019-12-17

Source documents