Ultrastar® DC SN640 NVMe™ PCIe 3.0 Self-Encrypting Drive
Ultrastar® DC SN640 NVMe™ PCIe 3.0 Self-Encrypting Drive, from Western Digital Technologies, Inc., holds FIPS 140-2 certificate #4309 at overall level 1. 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: None
Certificate
| Certificate number | 4309 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Hardware |
| Embodiment | Multi-Chip Embedded |
| Vendor | Western Digital Technologies, Inc. · website |
| Hardware versions | P/N WUS4AB0A1D9ELE8 |
| Firmware versions | R501000Q |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Ultrastar® DC SN640 NVMe™ PCIe 3.0 Self Encrypting Drive, from Western Digital, targets broad deployment opportunities in data center IT and cloud environments. The Ultrastar DC SN640 SSD is designed to maximize flash memory perfomance. The Ultrastar DC SN640, optimized to deliver high performance, ultra-low latency, high scalablity, provides lower TCO compared to SATA-based SSDs. The Ultrastar DC SN640 allows cloud installations to better manage peak demands, especially workloads associated with AI/ML, OLTP, virtualization, CDN, etc.
Security level exceptions
- Roles, Services, and Authentication: Level 2
- EMI/EMC: Level 3
- Design Assurance: Level 2
- Mitigation of Other Attacks: N/A
Approved algorithms (8)
| Algorithm | CAVP certificates |
|---|---|
| AES | 3580, 3913, A1232, C1973 |
| CKG | vendor affirmed |
| DRBG | A1232 |
| ENT | |
| HMAC | 2280 |
| PBKDF | A1232 |
| RSA | A1184, A1232 |
| SHS | 2942 |
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2022-09-26 | Initial | UL 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 at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2022-09-26