808bits

BlackRidge Technology Cryptographic Module

FIPS 140-2 certificate #3151 · BlackRidge Technology International, Inc. · data as of 2026-09-08

BlackRidge Technology Cryptographic Module, from BlackRidge Technology International, Inc., holds FIPS 140-2 certificate #3151 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. 186-2 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy. This validation entry is a non-security relevant modification to Cert. #2038.

Certificate

Certificate number3151
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorBlackRidge Technology International, Inc. · website
Software versions2.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The BlackRidge Technology Cryptographic Module provides cryptographic functions for BlackRidge TAC Gateway, BlackRidge TAC Endpoint for Linux, and BlackRidge Enterprise Manager.

Security level exceptions

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

Approved algorithms (9)

AlgorithmCAVP certificates
AES2273
CVL44
DRBG281
DSA709
ECDSA368
HMAC1391
RSA1166
SHS1954
Triple-DES1420

Allowed algorithms

EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • Red Hat Linux Enterprise 6.3 on a Dell OptiPlex 755 (single-user mode)

Validation history

DateTypeLab
2018-03-14InitialAcumen Security
2019-02-21Update

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: 2018-03-14, 2019-02-21

Source documents