808bits

Dolphin DCI 1.2

FIPS 140-2 certificate #1392 · Doremi Labs · data as of 2026-10-21

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

Certificate

Certificate number1392
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip embedded
VendorDoremi Labs · website
Hardware versionsDOLPHIN-DCI-1.2-A0, DOLPHIN-DCI-1.2-A1, DOLPHIN-DCI-1.2-C0 and DOLPHIN-DCI-1.2-C1
Firmware versions(2.0.4, 99.03 and 22.03-0) or (2.0.4, 99.03 and 22.03-1)

Module description

Quoted from the NIST CMVP entry for this certificate.

The Dolphin DCI 1.2 is a PCI-card that provides a standard definition/high definition serial digital interface. This is a Doremi decoder hardware card that contains a JPEG-2000 decoder hardware and BNC serial digital interface connectors used in Doremi Digital Cinema Servers like the DCP-2000. The Dolphin DCI 1.2 utilizes a dual-link encoded serial digital interface for output of DCI compliant resolutions up to 2040x1080p24 (2K-film). It can also operate single link for lower resolution material (i.e. trailers, advertisement, etc.).

Approved algorithms (5)

AlgorithmCAVP certificates
AES521, 532, 1252
HMAC271, 731
RNG326, 693, 696, 700
RSA600, 601
SHS593, 1148

Other algorithms

MD5; HMAC-MD5; TRNGs; RSA (key wrapping, key establishment methodology provides 112 bits of encryption strength);

Validation history

DateTypeLab
2010-08-12InitialAEGISOLVE, Inc.
2013-06-07UpdateAEGISOLVE, 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: 2010-08-12, 2013-06-07

Source documents