808bits

Apricorn Aegis Secure Key

FIPS 140-2 certificate #1876 · Apricorn, Inc. · data as of 2026-10-21

Apricorn Aegis Secure Key, from Apricorn, Inc., holds FIPS 140-2 certificate #1876 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: Tamper evidence determined as indicated in the Security Policy, Physical Security Policy section

Certificate

Certificate number1876
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorApricorn, Inc. · website
Hardware versionsASK-256-4GB, ASK-256-8GB, ASK-256-16GB and ASK-256-32GB
Firmware versionsV2.06A01.exe V1.39 with Security Controller Firmware Revision iStorage v12

Module description

Quoted from the NIST CMVP entry for this certificate.

The Apricorn Aegis Secure Key is a self-authenticating and self-encrypting secure USB flash drive based on DATALOCK® technology. The Apricorn Aegis Secure Key uses full-disk hardware based AES 256 bit encryption in CBC mode. The unit is not dependent on any host software and drivers. By design it is OS/Host independent and agnostic to any operating system (Win, Mac, Linux, Chrome, Android, Symbian, etc.), computer, or embedded device that supports the standard mass storage class (USB/USB OTG).

Approved algorithms (3)

AlgorithmCAVP certificates
AES1514
DRBG177
SHS1728

Other algorithms

NDRNG

Validation history

DateTypeLab
2013-01-30InitialUL Verification Services, Inc.
2013-03-08UpdateUL Verification Services, Inc.
2013-03-28UpdateUL Verification Services, Inc.
2016-06-16UpdateUL Verification Services, 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: 2013-01-30, 2013-03-08, 2013-03-28, 2016-06-16

Source documents