808bits

Ultrastar® SS300 TCG Enterprise SSD

FIPS 140-2 certificate #3271 · Western Digital Corporation · data as of 2026-10-21

Ultrastar® SS300 TCG Enterprise SSD, from Western Digital Corporation, holds FIPS 140-2 certificate #3271 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, installed, initialized and configured as specified in Sections 2.1 and 7.2 of the Security Policy

Certificate

Certificate number3271
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorWestern Digital Corporation · website
Hardware versionsP/Ns HUSTR7676ASS205 (1) [1, 2, 3], HUSTR7638ASS205 (1) [1, 3], HUSTR7619ASS205 (1) [1, 3], HUSTR7696ASS205 (1) [1, 3] and HUSTR7648ASS205 (1) [1, 2, 3]
Firmware versionsR500 [1], R512 [2] or R520 [3]

Module description

Quoted from the NIST CMVP entry for this certificate.

Ultrastar® Self-Encrypting TCG Enterprise drives meet or exceed the most demanding performance and security requirements. The Ultrastar SS300 solid-state TCG Enterprise 2.5-inch SAS drive supports multiple TLC capacities, a 12 Gbps SAS-3 Interface and multiple Drive Write Day rates.

Security level exceptions

  • EMI/EMC: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (7)

AlgorithmCAVP certificates
AES4281, 4309
CKGvendor affirmed
DRBG1341
HMAC2817
PBKDFvendor affirmed
RSA2302
SHS3517, 3519

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2018-08-29InitialUL 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: 2018-08-29

Source documents