808bits

SecureAgent® Software Cryptographic Module

FIPS 140-2 certificate #2133 · SecureAgent® Software Inc. · data as of 2026-08-28
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. No assurance of module integrity when operating in non-FIPS mode

Certificate

Certificate number2133
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorSecureAgent® Software Inc. · website
Software versions2.2.006

Module description

The SecureAgent® Software Cryptographic Module provides the core cryptographic services for several secure communications and controller systems designed and manufactured by SecureAgent® Software.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES2044
HMAC1243
RNG1067
SHS1790

Other algorithms

NDRNG; AES (non-compliant); RSA (non-compliant); DSA (non-compliant); SHA-1 (non-compliant); SHA-224 (non-compliant); SHA-256 (non-compliant); SHA-384 (non-compliant); SHA-512 (non-compliant); ANSI X9.31 RNG (non-compliant); PBKDF (non-compliant); TDES (non-compliant); ARCFOUR; BLOWFISH; CAMELLIA; CAST5; DES; RC2; SEED; SERPENT; TWOFISH; Elgamal; HAVAL; MD2; MD4; MD5; RMD160; TIGER; TIGER1; TIGER2; WHIRLPOOL; SIMPLE_S2K; SALTED_S2K; ITERSALTED_S2K

Tested configurations

  • Sun Solaris 10 running on an IDG 9074 Secure Communications Controller (single-user mode)

Validation history

DateTypeLab
2014-04-25InitialCOACT INC CAFE LAB

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: 2014-04-25

Source documents