808bits

IBM® Crypto for C

FIPS 140-2 certificate #2420 · IBM® Corporation · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number2420
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorIBM® Corporation · website
Software versions8.4.1.0

Module description

The IBM Crypto for C v8.4.0.0 (ICC) cryptographic module is implemented in the C programming language. It is packaged as dynamic (shared) libraries usable by applications written in a language that supports C language linking conventions (e.g. C, C++, Java, Assembler, etc.) for use on commercially available operating systems. The ICC allows these applications to access cryptographic functions using an Application Programming Interface (API) provided through an ICC import library and based on the API defined by the OpenSSL group.

Security level exceptions

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

Approved algorithms

Other algorithms

RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength); Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #441, #442, #443, #444, #445, #446, #447, #448, #449, #450, #451, #452 and #453, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); MD2; MD4; MD5; MDC2; RIPEMD; HMAC-MD5; DES; CAST; Camellia; Blowfish; Password based encryption; RC4; RC2; TRNG; KBKDF (non-compliant); DSA (non-compliant)

Tested configurations

  • AIX® 7.1 64-bit running on an IBM 8286-42A POWER8 with PAA
  • AIX® 7.1 64-bit running on an IBM 8286-42A POWER8 without PAA
  • Microsoft Windows Server 2008® 64-bit running on S2600CP with PAA
  • Microsoft Windows Server 2008® 64-bit running on S2600CP without PAA
  • Red Hat Linux Enterprise Server 7.0 64-bit running on S2600CP with PAA
  • Red Hat Linux Enterprise Server 7.0 64-bit running on S2600CP without PAA
  • Red Hat Linux Enterprise Server 7.0 BE 64-bit running on an IBM 8286-42A POWER8 with PAA
  • Red Hat Linux Enterprise Server 7.0 BE 64-bit running on an IBM 8286-42A POWER8 without PAA
  • SLES 11 64-bit running on an IBM zSeries z196 type 2817 model M32 with CPACF
  • SLES 11 64-bit running on an IBM zSeries z196 type 2817 model M32 without CPACF (single-user mode)
  • Solaris® 11 64-bit running on Netra SPARC T4-1 Server with PAA
  • Solaris® 11 64-bit running on Netra SPARC T4-1 Server without PAA
  • Ubuntu 14.04 LE 64-bit running on IBM 8247-22L POWER8 with PAA
  • Ubuntu 14.04 LE 64-bit running on IBM 8247-22L POWER8 without PAA

Validation history

DateTypeLab
2015-08-05Initialatsec information security corporation

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: 2015-08-05

Source documents