808bits

DualAuth Cryptographic Module

FIPS 140-2 certificate #4121 · DualAuth · data as of 2026-10-09

DualAuth Cryptographic Module, from DualAuth, holds FIPS 140-2 certificate #4121 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 operated in FIPS mode. No assurance of the minimum strength of generated keys. This validation entry is a non-security relevant modification to Cert. #3273

Certificate

Certificate number4121
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorDualAuth · website
Software versions2.2

Module description

Quoted from the NIST CMVP entry for this certificate.

DualAuth Cryptographic Module is a standards-based, drop-in compliant cryptographic engine for servers, PCs, network appliances, mobile devices, and other deployments. The module delivers core cryptographic functions and features robust algorithm support, including Suite B algorithms. DualAuth Cryptographic Module offloads secure key management, data integrity, data at rest encryption, and secure communications to a trusted implementation.

Security level exceptions

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

Approved algorithms (9)

AlgorithmCAVP certificates
AES4750
CKGvendor affirmed
DRBG1631
DSA1273
ECDSA1185
HMAC3164
RSA2594
SHS3893
Triple-DES2524

Tested configurations

  • CentOS 7.3 running on a Dell Optiplex 755 with an Intel Celeron 430 processor (single-user mode)

Validation history

DateTypeLab
2022-01-03InitialLeidos Accredited Testing & Evaluation (AT&E) Lab

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-01-03

Source documents