808bits

Seagate Secure® TCG Opal SSC Self-Encrypting Drive

FIPS 140-2 certificate #3134 · Seagate Technology LLC · data as of 2026-08-28
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. This validation entry is a non-security-relevant modification to Cert. #1826

Certificate

Certificate number3134
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorSeagate Technology LLC · website
Software versionsN/A
Hardware versions9WU142 [1, 2, 3, 4, 5], 9WU14C [1, 2, 3, 4, 5], 9WU141 [1, 2, 3, 4, 5], 1DJ142 [1, 5, 6, 7], 1DJ14C [1, 5, 6, 7], 1DJ141 [1, 5, 6, 7], 1RS152 [1, 8, 9, 10], 1RS15C [1, 8, 9, 10] and 1RS15D [1, 8, 9, 10]
Firmware versions0001SDM7 [1], 0001SED7 [2], 0002SDM7 [3], 0002SED7 [4], 0001LIM7 [5], 1002SED7 [6], 1003SED7 [7], 0001YXM7 [8], 0002LIM7 [9] or 0004LIM7 [10]

Module description

The Seagate Secure® TCG Opal SSC Self-Encrypting Drive 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

AlgorithmCAVP certificate
AES1343, 1845
DRBG62
RSA650
SHS1225

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2018-02-21InitialLeidos Accredited Testing & Evaluation (AT&E) Lab

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-02-21

Source documents