808bits

DataLocker H350

FIPS 140-2 certificate #2826 · DataLocker Inc. · data as of 2026-10-21

DataLocker H350, from DataLocker Inc., holds FIPS 140-2 certificate #2826 at overall level 3. 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: Files distributed with the module mounted within the Read-Only drive are excluded from validation

Certificate

Certificate number2826
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorDataLocker Inc. · website
Hardware versionsP/Ns MXKB1B500G5001FIPS, MXKB1B001T5001FIPS, MXKB1B002T5001FIPS, DL-H350-0250SSD, DL-H350-0500SSD, DL-H350-1000SSD
Firmware versions1.1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

DataLocker H350 is a secure USB hard disk drive with 256-bit AES encryption and PKI operations combined with advanced authentication and policy management capabilities to help organizations control user access to sensitive data. DataLocker H350 allows enterprise management features like password recovery and remote kill.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (6)

AlgorithmCAVP certificates
AES1412, 4139
DRBG1257
HMAC2712, 2715
PBKDFvendor affirmed
RSA2255, 2256
SHS1282, 3409

Other algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2017-01-31InitialUL Verification Services, Inc.
2018-07-27UpdateUL 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: 2017-01-31, 2018-07-27

Source documents