808bits

Ranger Cryptographic Module

FIPS 140-2 certificate #4230 · Tavve Holdings, LLC · 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 number4230
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorTavve Holdings, LLC · website
Software versions1.0.2.1, 1.0.2.2 and 1.0.2.3

Module description

The Ranger Cryptographic Module provides cryptographic functions for Tavve’s Ranger-based applications.

Security level exceptions

  • Physical Security: N/A

Approved algorithms

AlgorithmCAVP certificate
AESA1641, A2113, C2204
CKGvendor affirmed
CVLA1641, A2113, C2204
DRBGA1641, A2113, C2204
DSAA1641, A2113, C2204
ECDSAA1641, A2113, C2204
HMACA1641, A2113, C2204
KAS-SSCvendor affirmed
KBKDFA1641, A2113, C2204
KTS
KTSvendor affirmed
KTS
PBKDFvendor affirmed
RSAA1641, A2113, C2204
SHA-3A1641, A2113, C2204
SHSA1641, A2113, C2204
Triple-DESA1641, A2113, C2204

Allowed algorithms

MD5; NDRNG; RSA (CVL Certs. #A1641, #A2113 and #C2204, 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
2022-05-16InitialAcumen Security
2022-06-03UpdateAcumen 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: 2022-05-16, 2022-06-03

Source documents