808bits

DIGISTOR® C Series Advanced SSD and Seagate® BarraCuda™ 515 SSD

FIPS 140-2 certificate #4294 · DIGISTOR · data as of 2026-08-28
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. When installed, initialized and configured as specified in the Security Rules Section of the Security Policy. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number4294
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorDIGISTOR · website
Hardware versionsDIG-M2N22566-AI, DIG-M2N25126-AI, DIG-M2N210006-AI, DIG-M2N220006-AI, ZP256MC30012, ZP512MC30012, ZP1024MC30012, ZP2048MC30012, ZP256MC30022, ZP512MC30022, ZP1024MC30022 and ZP2048MC30022
Firmware versionsECPM13.1

Module description

DIGISTOR® C Series Advanced and Seagate® BarraCuda™ 515 SSDs provide endpoint security for Data at Rest. These are FIPS 140-2 L2-certified with AES 256-bit encryption. Firmware renders secured portions of the drive unreadable at the sector level. Authentication keys from user-supplied credentials use the maximum length allowed; keys are not stored in their final form. Zero-trust access prevents data breaches and ransomware attacks. Keep Alive heartbeat automatically hides secured data. Unerasable data access logs provide audit trails. Data destruction verification ensures that data was erased.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AESC1358
CKGvendor affirmed
DRBGC1358
HMACC1358
KTS
PBKDFA1725
RSAC1357, C1358
SHSC1357, C1358

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2022-09-10InitialAEGISOLVE, Inc.
2022-09-15UpdateAEGISOLVE, 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: 2022-09-10, 2022-09-15

Source documents