808bits

IBM CryptoLite for C

FIPS 140-2 certificate #750 · IBM® Corporation · data as of 2026-09-03

IBM CryptoLite for C, from IBM® Corporation, holds FIPS 140-2 certificate #750 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 number750
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorIBM® Corporation · website
Software versions3.23

Module description

Quoted from the NIST CMVP entry for this certificate.

IBM CryptoLite is a C software package providing advanced cryptographic services in a very small footprint. CryptoLite supports public key encryption, digital signatures, symmetric ciphers, hash functions, message authentication codes, and other cryptographic algorithms through a simple programming interface. There are no runtime dependencies and the code has been optimized for high performance.

Security level exceptions

  • Cryptographic Module Specification: Level 3

Approved algorithms (7)

AlgorithmCAVP certificates
AES498
DSA205
HMAC252
RNG278
RSA214
SHS568
Triple-DES511

Other algorithms

RC2; CAST-5; CAST-6; Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112-bits of encryption strength); MD5; MD2; HMAC-MD2; HMAC-MD5; Whirlpool; Arc-Four; DES

Tested configurations

  • AIX 5200-07 (32-bit kernel), AIX 5200-07 (64-bit kernel), AIX 5300-03 (32-bit kernel), AIX 5300-03 (64-bit kernel) (single-user mode)

Validation history

DateTypeLab
2007-03-23InitialSAIC-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-03-23

Source documents