808bits

VMware's BC-FJA (Bouncy Castle FIPS Java API)

FIPS 140-2 certificate #3673 · VMware, Inc. · data as of 2026-09-13

VMware's BC-FJA (Bouncy Castle FIPS Java API), from VMware, Inc., holds FIPS 140-2 certificate #3673 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 installed, initialized and configured as specified in the Security Policy Section 3 and operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number3673
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorVMware, Inc. · website
Software versions1.0.2.1, 1.0.2.2, 1.0.2.3

Module description

Quoted from the NIST CMVP entry for this certificate.

VMware’s BC-FJA (Bouncy Castle FIPS Java API) is a software cryptographic module that provides cryptographic functions and services to various VMware applications via a well-defined Java-language application programming interface (API).

Security level exceptions

  • Physical Security: N/A

Approved algorithms (15)

AlgorithmCAVP certificates
AESA2054, A2841, C2205
CKGvendor affirmed
CVLA2054, A2841, C2205
DRBGA2054, A2841, C2205
DSAA2054, A2841, C2205
ECDSAA2054, A2841, C2205
HMACA2054, A2841, C2205
KAS-SSCvendor affirmed
KBKDFA2054, A2841, C2205
KTSvendor affirmed
PBKDFvendor affirmed
RSAA2054, A2841, C2205
SHA-3A2054, A2841, C2205
SHSA2054, A2841, C2205
TDESA2054, A2841, C2205

Allowed algorithms

NDRNG; MD5; RSA (CVL Cert. #C2205, key wrapping; key establishment methodology provides between 150 and 256 bits of encryption strength)

Tested configurations

  • CentOS 8 with JDK 11 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • Photon OS 3.0 with JDK 8 on VMware ESXi 8.0 running on Dell PowerEdge R650 with Intel Xeon Gold 6330
  • Photon OS 4.0 with JDK 11 on VMware ESXi 8.0 running on Dell PowerEdge R650 with Intel Xeon Gold 6330 (single user mode)
  • SUSE Linux Enterprise Server 15 with JDK 11 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • Ubuntu 16.04 with JDK 11 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • Ubuntu 16.04 with JDK 8 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • Ubuntu 18.04 with JDK 11 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • Ubuntu 18.04 with JDK 11 running on Dell Latitude E7470 with Intel Core i5
  • Ubuntu 18.04 with JDK 8 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • VMware Photon OS 2.0 with JDK 11 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • VMware Photon OS 2.0 with JDK 8 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • VMware Photon OS 3.0 with JDK 11 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • VMware Photon OS 3.0 with JDK 8 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • Windows 10 with JDK 11 running on Dell Latitude E7470 with Intel Core i5
  • Windows Server 2016 with JDK 11 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • Windows Server 2016 with JDK 8 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126
  • Windows Server 2019 with JDK 11 on VMware ESXi 7.0 running on Dell PowerEdge R740 with Intel Xeon Gold 6126

Validation history

DateTypeLab
2020-06-22InitialAcumen Security
2021-05-14UpdateAcumen Security
2024-03-07UpdateAcumen 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: 2020-06-22, 2021-05-14, 2024-03-07

Source documents