808bits

CloudLink Crypto Module

FIPS 140-2 certificate #2135 · AFORE Solutions Inc. · data as of 2026-08-28
Historical. RNG SP800-131A Revision 1 Transition. 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 9 and operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy. No assurance of the minimum strength of generated keys

Certificate

Certificate number2135
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorAFORE Solutions Inc. · website
Software versions1.0

Module description

The CloudLink Crypto Module is a general purpose cryptographic library which provides cryptographic services for all CloudLink application modules.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES2545
CVL104
DRBG378
DSA778
HMAC1566
RNG1220
RSA1300
SHS2146
Triple-DES1540

Other algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); ECC CDH (non-compliant); ECDSA (non-compliant); Dual-EC DRBG (non-compliant)

Tested configurations

  • Ubuntu 12.04 on VMWare ESXi 5.1.0 running on a Dell PowerEdge R520 with PAA
  • Ubuntu 12.04 on VMWare ESXi 5.1.0 running on a Dell PowerEdge R520 without PAA (single-user mode)

Validation history

DateTypeLab
2014-04-24InitialCGI Information Systems & Management Consultants 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: 2014-04-24

Source documents