808bits

Symantec Cryptographic Module

FIPS 140-2 certificate #1591 · Symantec Corporation · data as of 2026-10-21

Symantec Cryptographic Module, from Symantec Corporation, holds FIPS 140-2 certificate #1591 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 number1591
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorSymantec Corporation · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Symantec Cryptographic Module is a software module with a multi-chip standalone embodiment. The overall security level of the module is 1. SymCrypt is implemented in the C programming language and consists of a shared library that is linked with SSIM application components. It is designed to execute on a host system with a General Purpose Computer (GPC) hardware platform.

Approved algorithms (7)

AlgorithmCAVP certificates
AES1607
DSA498
HMAC943
RNG861
RSA789
SHS1420
Triple-DES1052

Other algorithms

DES; Blowfish; CAST; IDEA; RC2; RC4; RC5; MD2; MD4; MD5; RipeMD; MDC-2; Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant); RSA (Cert. #789, key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • Microsoft Windows Server 2003 (32-bit)
  • Red Hat Enterprise Linux 4.8 (32-bit) (single-user mode)

Validation history

DateTypeLab
2011-08-12InitialEWA - 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: 2011-08-12

Source documents