808bits

YubiHSM 2 Cryptographic Module

FIPS 140-2 certificate #3916 · Yubico, Inc. · data as of 2026-09-13

YubiHSM 2 Cryptographic Module, from Yubico, Inc., holds FIPS 140-2 certificate #3916 at overall level 3. 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, installed, initialized, and configured as specified in Section 3 of the Security Policy. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number3916
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle Chip
VendorYubico, Inc. · website
Hardware versionsSLE78CLUFX3000PH and SLE78CLUFX5000PH
Firmware versions2.2.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The YubiHSM 2 is a USB-based, multi-purpose cryptographic device that is primarily used in servers. It is optimized for a small form factor and low power requirements.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (11)

AlgorithmCAVP certificates
AESC1680
CKGvendor affirmed
CVLC1680
DRBGC1680
ECDSAC1680
HMACC1680
KAS-SSCvendor affirmed
KBKDFC1680
KTS
RSAA985, C1680
SHSC1680

Allowed algorithms

EC Diffie-Hellman (shared secret computation provides between 128 and 256 bits of encryption strength); NDRNG; RSA (CVL Cert. #C1680, key unwrapping; key establishment provides between 112 and 150 bits of encryption strength); RSA (key unwrapping; key establishment provides between 112 and 150 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2021-05-03InitialAcumen 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: 2021-05-03

Source documents