808bits

Unity 12 Gb/s SAS I/O Module with Encryption

FIPS 140-2 certificate #2912 · EMC Corporation · data as of 2026-09-03

Unity 12 Gb/s SAS I/O Module with Encryption, from EMC Corporation, holds FIPS 140-2 certificate #2912 at overall level 1. 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: None

Certificate

Certificate number2912
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorEMC Corporation · website
Hardware versionsStorage Processor SAS Module with P/N 362-000-332, P/N 363-000-071, P/N 363-000-084 and P/N 364-000-096 and Pluggable I/O SAS Module with P/N 362-000-333, P/N 363-000-071, P/N 363-000-084 and P/N 364-000-063
Firmware versions03.90

Module description

Quoted from the NIST CMVP entry for this certificate.

The EMC Unity 12 Gb/s SAS I/O Module with Encryption is a high-density SAS controller chipset executing specialized firmware that provides Data At Rest Encryption (D@RE) for EMC Unity storage arrays. It implements 256-bit AES-XTS encryption/decryption to encrypt and decrypt data as it is being written to or read from a SAS drive. The two variants are the Storage Processor SAS Module variant which is embedded on the printed circuit board (PCB) of the Storage Processor and the Pluggable I/O SAS Module variant which is embedded on the PCB of a pluggable I/O Module.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (2)

AlgorithmCAVP certificates
AES3586, 3598
KTS

Tested configurations

  • N/A

Validation history

DateTypeLab
2017-05-16InitialDXC Technology

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-05-16

Source documents