808bits

IBM® Crypto for C

FIPS 140-2 certificate #775 · IBM® Corporation · data as of 2026-10-21

IBM® Crypto for C, from IBM® Corporation, holds FIPS 140-2 certificate #775 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. 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 number775
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorIBM® Corporation · website
Software versions1.4.5

Module description

Quoted from the NIST CMVP entry for this certificate.

The ICC is a C language implementation of cryptographic functions which uses the cryptographic library provided by the OpenSSL project. This enables IBM products to use an open source solution for cryptography and a FIPS 140-2 certified cryptographic provider.

Approved algorithms (7)

AlgorithmCAVP certificates
AES426, 468
DSA177, 192
HMAC200, 226
RNG220
RSA184, 189
SHS497, 535
Triple-DES456, 484

Other algorithms

RC2; RC2-40; RC2-60; RC4; Blowfish; CAST; MD2; MD4; MD5; RIPEMD; HMAC MD5; Diffie-Hellman (key agreement; key establishment methodology provides a minimum of 112 bits of encryption strength; non-compliant less than 112-bits of encryption strength); DES; RSA (encrypt/decrypt)

Tested configurations

  • SUN Solaris 9 (UltraSparc), HPUX 11i (PA-RISC 2.0), AIX 5.2 (PowerPC), RHEL v4 (IA-32, AMD64, PowerPC, zSeries), SLES 9.1 (IA-32, PowerPC, zSeries), SLES 9.0 (AMD64), Windows Server 2003 with SP1 (AMD64, IA-32) (single-user mode)

Validation history

DateTypeLab
2007-05-18InitialSAIC-VA

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: 2007-05-18

Source documents