808bits

DiamondLink/CL100

FIPS 140-2 certificate #628 · Cryptek, Inc. · data as of 2026-10-21

DiamondLink/CL100, from Cryptek, Inc., holds FIPS 140-2 certificate #628 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: When operated in FIPS mode

Certificate

Certificate number628
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorCryptek, Inc. · website
Hardware versionsP/Ns 5010D26200-4 Rev. C, 5010D26200-4 Rev. D, 5010D26200-5 Rev. D and 5010D26200-5 Rev. E
Firmware versions2.1.9 and 2.4.0.3

Module description

Quoted from the NIST CMVP entry for this certificate.

DiamondLink is a managed secure network appliance that features DiamondTEK's self protecting security computer. DiamondLink automatically identifies and authenticates the user to the network, encrypts communications and determines which data and servers the user is authorized to access. Security functions include token based user I&A, firewall filtering, IPSec, Data Driven Access Control (DDAC) capabilities and centralize management using the DiamondTEK DiamondCentral.

Security level exceptions

  • Design Assurance: Level 3

Approved algorithms (5)

AlgorithmCAVP certificates
HMAC-SHA-1vendor affirmed
RNG24
RSA19
SHS63
Triple-DES71

Other algorithms

DES (Cert. #132); DES MAC (Cert. #132, vendor affirmed); MD5; HMAC-MD5; Diffie Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant)

Validation history

DateTypeLab
2006-01-27InitialUL Verification Services, 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: 2006-01-27

Source documents