IBM® Crypto for C (ICC)
IBM® Crypto for C (ICC), from IBM® Corporation, holds FIPS 140-2 certificate #384 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.
Caveat: When operated in FIPS mode
Certificate
| Certificate number | 384 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | IBM® Corporation · website |
| Software versions | 1.1, 1.2, 1.2.1 and 1.2.2 |
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 (4)
Other algorithms
DES (Cert. #216); HMAC-SHA-1 (Cert #159, vendor affirmed; non-compliant); RC2; RC2-40; RC2-60; RC4; Blowfish; CAST; MD2; MD4; MD5; RIPEMD; HMAC-MD5; DSA (non-compliant); Diffie-Hellman (key agreement)
Tested configurations
- Sun Solaris 5.8, AIX 5.2, Windows 2000 Professional and Advanced Server, SUSE Linux Enterprise Server 8 (x86 and PowerPC), RedHat Linux Advanced Server 2.1 (x86), z/Linux 2.4, and HPUX 11i (all in single user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2004-02-17 | Initial | SAIC-VA |
| 2004-04-27 | Update | |
| 2004-12-02 | Update |
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: 2004-02-17, 2004-04-27, 2004-12-02