808bits

PowerMax NVMe and VMAX 12G SAS Module

FIPS 140-2 certificate #3506 · Dell EMC · data as of 2026-09-03

PowerMax NVMe and VMAX 12G SAS Module, from Dell EMC, holds FIPS 140-2 certificate #3506 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: When installed, initialized and configured as specified in the Security Policy Section 3

Certificate

Certificate number3506
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorDell EMC · website
Hardware versions303-493-001C-03 [1]; and 303-305-100A-06 [2]
Firmware versionsv3.09.34.00 [1]; and v3.08.41.00 [2]

Module description

Quoted from the NIST CMVP entry for this certificate.

Dell EMC Data at Rest Encryption (DARE) provides hardware-based, on-array, encryption for storage systems, including VMAX and PowerMax. DARE protects against unauthorized access when drives are physically removed. Encryption (AES-XTS 256-bit) occurs in the I/O module, allowing support for all back end drive types. Dell EMC Efficient Encryption leverages the same hardware module as DARE. Host encrypted data (AES-XTS 256-bit) is decrypted using shared keys, for the sole purpose of allowing Data Reduction capabilities to be applied before data is securely stored on drive.

Security level exceptions

  • Physical Security: Level 2
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (3)

AlgorithmCAVP certificates
AES3586, 3598
HMAC2296
SHS2961

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-08-08InitialEWA - Canada
2022-02-25UpdateEWA - Canada

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: 2019-08-08, 2022-02-25

Source documents