808bits

Hewlett Packard Enterprise BouncyCastle Module

FIPS 140-2 certificate #4585 · Hewlett Packard Enterprise Development LP · 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 installed, initialized and configured as specified in the Security Policy Section 8 and operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number4585
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorHewlett Packard Enterprise Development LP · website
Software versions1.0.2.3

Module description

The Hewlett Packard Enterprise BouncyCastle module 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

Approved algorithms

AlgorithmCAVP certificate
AESA2113
CKGvendor affirmed
CVLA2113
DRBGA2113
DSAA2113
ECDSAA2113
HMACA2113
KAS-SSCvendor affirmed
KBKDFA2113
KTS
KTSvendor affirmed
KTS
PBKDFvendor affirmed
RSAA2113
SHA-3A2113
SHA-3-Customizedvendor affirmed
SHSA2113
Triple-DESA2113

Allowed algorithms

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

Tested configurations

  • VMware Photon OS 2.0 with JDK 11 on VMware ESXi 6.7 running on Dell PowerEdge R830 with Intel Xeon E5
  • VMware Photon OS 2.0 with JDK 7 on VMware ESXi 6.7 running on Dell PowerEdge R830 with Intel Xeon E5
  • VMware Photon OS 2.0 with JDK 8 on VMware ESXi 6.7 running on Dell PowerEdge R830 with Intel Xeon E5 (single-user mode)

Validation history

DateTypeLab
2023-09-06InitialAcumen 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: 2023-09-06

Source documents