808bits

Duo Security Cryptographic Module

FIPS 140-2 certificate #2671 · Duo Security, Inc. · data as of 2026-10-09

Duo Security Cryptographic Module, from Duo Security, Inc., holds FIPS 140-2 certificate #2671 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. This validation entry is a non-security relevant modification to Cert. #1938. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number2671
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorDuo Security, Inc. · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Duo Security Cryptographic Module is a cryptographic engine for mobile devices. The module delivers core cryptographic functions to Duo Security's Two-Factor Authentication mobile application.

Security level exceptions

  • Physical Security: N/A
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (9)

AlgorithmCAVP certificates
AES2125
CVL28
DRBG233
DSA666
ECDSA319
HMAC1296
RSA1094
SHS1849
Triple-DES1351

Other algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RNG; Dual EC DRBG

Tested configurations

  • Android 4.0 running on a Galaxy Nexus

Validation history

DateTypeLab
2016-07-07InitialAcumen 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: 2016-07-07

Source documents