808bits

Apricorn FIPS Module 140-2

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

Apricorn FIPS Module 140-2, from Apricorn, Inc., holds FIPS 140-2 certificate #1965 at overall level 2. 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: None

Certificate

Certificate number1965
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorApricorn, Inc. · website
Hardware versionsREV. A [A,B] or REV. A with CAN 1A [A,B]
Firmware versions4.0 [A] or 4.1 [B]

Module description

Quoted from the NIST CMVP entry for this certificate.

The Apricorn FIPS 140-2 Module is a flexible FIPS module with the ability to interface to multiple types of authentication or hardware. Completely contained within a small footprint/boundary, the module is designed to allow simple integration into various secure storage systems requiring a FIPS validated encryption boundary and does not require software. The Apricorn FIPS 140-2 Module is used in the Aegis Fortress, Padlock DT FIPS, and the Padlock SSD families.

Security level exceptions

  • EMI/EMC: Level 3
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (3)

AlgorithmCAVP certificates
AES2235
DRBG260
SHS1911

Other algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2013-06-14InitialAEGISOLVE, Inc.
2014-04-16UpdateAEGISOLVE, Inc.
2014-06-27UpdateAEGISOLVE, Inc.
2015-10-20UpdateAEGISOLVE, 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-06-14, 2014-04-16, 2014-06-27, 2015-10-20

Source documents