Seagate Secure® TCG Enterprise SSC Self-Encrypting Drives FIPS 140 Module
Seagate Secure® TCG Enterprise SSC Self-Encrypting Drives FIPS 140 Module, from Seagate Technology LLC, holds FIPS 140-2 certificate #4398 at overall level 2. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
Caveat: When operated in FIPS mode
Certificate
| Certificate number | 4398 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-Chip Embedded |
| Vendor | Seagate Technology LLC · website |
| Hardware versions | ST2000NX0333[1], ST2000NX0353[2] |
| Firmware versions | KF06[1], EF06[2] |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Seagate Secure® TCG Enterprise SSC Self-Encrypting Drives FIPS 140 Module is embodied in Seagate Enterprise Capacity® HDD v4 Self-Encrypting Drives model disk drives. 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
- Mitigation of Other Attacks: N/A
Approved algorithms (9)
| Algorithm | CAVP certificates |
|---|---|
| AES | 1343, 2841, 2842, 2947 |
| CKG | vendor affirmed |
| DRBG | 62 |
| ENT | |
| HMAC | 1597 |
| KTS | |
| PBKDF | A1777 |
| RSA | 1021 |
| SHS | 1225, 2383 |
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2022-12-22 | Initial | Leidos 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 at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2022-12-22