808bits

Seagate® Momentus® Thin Self-Encrypting Drives TCG Opal FIPS 140 Module

FIPS 140-2 certificate #1451 · Seagate Technology LLC · data as of 2026-10-21

Seagate® Momentus® Thin Self-Encrypting Drives TCG Opal FIPS 140 Module, from Seagate Technology LLC, holds FIPS 140-2 certificate #1451 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number1451
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip embedded
VendorSeagate Technology LLC · website
Hardware versionsHW 9WC142 [1, 2, 3, 4, 5, 6, 7, 8], 9WC14C [3, 4, 7, 8]
Firmware versionsFW 1003HPMA [1], 1002HPBA [2], 1001DEMA [3], 1001SDMA [4], 1004HPMA [5], 1003HPBA [6], 1002DEMA [7], 1002SDMA [8]

Module description

Quoted from the NIST CMVP entry for this certificate.

The Seagate® Momentus® Thin Self-Encrypting Drive (SED) FIPS 140 Module is embedded in Seagate Momentus Thin SED model disk drives. The cryptographic module (CM) provides a wide range of cryptographic services using FIPS approved algorithms. Services include hardware-based data encryption, instantaneous user data disposal with cryptographic erase, independently controlled and protected user data LBA ranges, and authenticated FW download. The services are provided through an industry-standard TCG Opal SSC interface.

Security level exceptions

  • EMI/EMC: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES1392, 1341
RNG737
RSA648
SHS1223

Validation history

DateTypeLab
2010-11-22InitialDOMUS
2012-07-18UpdateUL 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: 2010-11-22, 2012-07-18

Source documents