808bits

Seagate Secure® TCG Enterprise SSC Pulsar.2 Self-Encrypting Drive FIPS 140 Module

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

Seagate Secure® TCG Enterprise SSC Pulsar.2 Self-Encrypting Drive FIPS 140 Module, from Seagate Technology LLC, holds FIPS 140-2 certificate #1862 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 number1862
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip embedded
VendorSeagate Technology LLC · website
Hardware versions1BU282
Firmware versions0003

Module description

Quoted from the NIST CMVP entry for this certificate.

The Seagate Secure« Enterprise Self-Encrypting Drives FIPS 140 Module is embodied in the Seagate Pulsar.2 SED model disk drive. These products meet the performance requirements of the most demanding Enterprise applications. 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 bands and authenticated FW download.

Security level exceptions

  • EMI/EMC: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES1811, 1343
DRBG62
RSA650
SHS1225

Validation history

DateTypeLab
2013-01-07InitialSAIC-VA
2013-01-25UpdateLeidos 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: 2013-01-07, 2013-01-25

Source documents