808bits

CM180D

FIPS 140-2 certificate #1070 · CipherMax, Inc. · data as of 2026-09-14

CM180D, from CipherMax, Inc., holds FIPS 140-2 certificate #1070 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1070
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorCipherMax, Inc. · website
Hardware versionsP/N 81-00038-01 Version ILC 6.11
Firmware versions5.4.0.36

Module description

Quoted from the NIST CMVP entry for this certificate.

CM180D delivers a complete solution for all primary and secondary disk-based storage application, with in-line encryption processing, discrete security administration controls, and a comprehensive, automated key management system. The integration of powerful encryption processing and high port count, any-to-any connectivity allows for CM180D to deliver an enormous amount of functionality with far less consumption space, power, and cooling than first generation in-line encryption appliances.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Design Assurance: Level 3

Approved algorithms (7)

AlgorithmCAVP certificates
AES629
DSA241
HMAC326
RNG360
RSA289
SHS670
Triple-DES590

Other algorithms

MD5; Diffie-Hellman (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant); RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength: non-compliant)

Validation history

DateTypeLab
2008-12-24InitialUL Verification Services, Inc.
2009-02-23Update

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: 2008-12-24, 2009-02-23

Source documents