808bits

Datastax BoringCrypto Module

FIPS 140-2 certificate #4667 · DataStax, Inc. · data as of 2026-10-09

Datastax BoringCrypto Module, from DataStax, Inc., holds FIPS 140-2 certificate #4667 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode. No assurance of the minimum strength of generated keys.

Certificate

Certificate number4667
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorDataStax, Inc. · website
Software versions853ca1ea1168dff08011e5d42d94609cc0ca2e27

Module description

Quoted from the NIST CMVP entry for this certificate.

Software library for Datastax applications that use BoringSSL and other user-space applications which require cryptographic functionality.

Security level exceptions

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

Approved algorithms (11)

AlgorithmCAVP certificates
AESA3514
CVLA3514
DRBGA3514
ECDSAA3514
HMACA3514
KAS
KAS-SSCA3514
KTS
RSAA3514
SHSA3514
Triple-DESA3514

Allowed algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • Ubuntu 20.04 on Supermicro SYS-6019U-TN4R4T with Intel® Xeon® Platinum 8360 with PAA
  • Ubuntu 20.04 on Supermicro SYS-6019U-TN4R4T with Intel® Xeon® Platinum 8360 without PAA (single-user mode)

Validation history

DateTypeLab
2023-11-30InitialAcumen 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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2023-11-30

Source documents