808bits

SAFE-Key Device

FIPS 140-2 certificate #3186 · BiObex, LLC · data as of 2026-09-13

SAFE-Key Device, from BiObex, LLC, holds FIPS 140-2 certificate #3186 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 utilizing a Trusted Path as specified in the Security Policy

Certificate

Certificate number3186
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorBiObex, LLC · website
Hardware versions1.4
Firmware versionsBoot 1.2.0.0, PEM 1.2.0.0, BIOS 1.2.0.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The SAFE-Key device is a USB-based hardware security token; its primary purpose is two-factor authentication. The device supports three modalities: web-based two-factor authentication (patented), two-factor authentication for protected file decryption and two-factor authentication for digital signature generation. The two factors are something you have (i.e. a specific SAFE-Key device) and something you know (i.e. a password). It also supports one-factor, something you have (i.e. a specific SAFE-Key device) authentication.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (9)

AlgorithmCAVP certificates
AES5373
CKGvendor affirmed
CVL1839
DRBG2080
HMAC3561
KASvendor affirmed
KTS
RSA2874
SHS4313

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2018-05-24InitialCYGNACOM SOLUTIONS INC

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-05-24

Source documents