808bits

Sterling Crypto-C

FIPS 140-2 certificate #921 · Sterling Commerce, Inc. · data as of 2026-09-03

Sterling Crypto-C, from Sterling Commerce, Inc., holds FIPS 140-2 certificate #921 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 number921
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorSterling Commerce, Inc. · website
Software versions1.5

Module description

Quoted from the NIST CMVP entry for this certificate.

Sterling Crypto-C is a software module implemented as two dynamic libraries. Sterling Crypto-C provides security capabilities, such as encryption, authentication, and signature generation and verification for Sterling Commerce's managed file transfer solutions.

Approved algorithms (7)

AlgorithmCAVP certificates
AES605
DSA235
HMAC312
RNG403
RSA280
SHS655
Triple-DES578

Other algorithms

DES; RC2; RC4; Blowfish; CAST; MD2; MD4; MD5; RIPEMD; HMAC-MD5; 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); RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • and HP-UX 11i v2 (single-user mode)
  • IBM AIX 5L(TM) 5.3
  • Microsoft Windows Server 2003
  • Sun Solaris 10

Validation history

DateTypeLab
2008-02-29InitialEWA - Canada

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: 2008-02-29

Source documents