808bits

Seagate Secure® TCG Opal SSC Self-Encrypting Drive FIPS 140-2 Module

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

Seagate Secure® TCG Opal SSC Self-Encrypting Drive FIPS 140-2 Module, from Seagate Technology LLC, holds FIPS 140-2 certificate #2291 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: When operated in FIPS mode

Certificate

Certificate number2291
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip embedded
VendorSeagate Technology LLC · website
Hardware versionsP/Ns 1HN162 and 1M2162
Firmware versions0002SDM7, 0002LIM7 and 0002SED7

Module description

Quoted from the NIST CMVP entry for this certificate.

The Seagate Secure® TCG Opal SSC Self-Encrypting Drive FIPS 140-2 Module is embedded in Seagate Momentus® Thin Self-Encrypting Drives (SEDs). 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
  • Mitigation of Other Attacks: N/A

Approved algorithms (6)

AlgorithmCAVP certificates
AES1343, 2803, 2804, 2947
DRBG62
HMAC1597
PBKDFvendor affirmed
RSA650
SHS1225, 2352

Other algorithms

NDRNG

Validation history

DateTypeLab
2014-12-10InitialUL 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: 2014-12-10

Source documents