808bits

Symantec Messaging Gateway Cryptographic Module

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

Symantec Messaging Gateway Cryptographic Module, from Symantec Corporation, holds FIPS 140-2 certificate #2849 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2849
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSymantec Corporation · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Symantec Messaging Gateway Cryptographic Module provides cryptographic functions for the Messaging Gateway platforms software. The module's logical cryptographic boundary is the shared library files and their integrity check HMAC files. The module is a multi-chip standalone embodiment installed on a General Purpose Device. All operations of the module occur via calls from host applications and their respective internal daemons/processes. As such there are no untrusted services calling the services of the module.

Security level exceptions

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

Approved algorithms (9)

AlgorithmCAVP certificates
AES4124
CVL931
DRBG1244
DSA1117
ECDSA939
HMAC2695
RSA2238
SHS3393
Triple-DES2255

Other algorithms

EC Diffie-Hellman (CVL Cert. #931, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength; non-compliant less than 112 bits of encryption strength); AES XTS (AES Cert. #4124; non-compliant); PRNG

Tested configurations

  • CentOS 6 running on a Dell PowerEdge R430 with Intel Xeon E5-2600

Validation history

DateTypeLab
2017-02-27InitialEWA - Canada
2019-04-16Update

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: 2017-02-27, 2019-04-16

Source documents