808bits

Symantec Scanner Cryptographic Module

FIPS 140-2 certificate #1827 · Symantec Corporation · data as of 2026-09-03

Symantec Scanner Cryptographic Module, from Symantec Corporation, holds FIPS 140-2 certificate #1827 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 number1827
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 Scanner Cryptographic Module Version 1.0 provides cryptographic services to the Scanner component of the Symantec Messaging Gateway solution, a secure email gateway offering. The Scanner provides filtering services on inbound and outbound message flows and is responsible for taking actions on emails based on filtering verdicts.

Approved algorithms (7)

AlgorithmCAVP certificates
AES1809
DSA567
HMAC1067
RNG954
RSA906
SHS1588
Triple-DES1167

Other algorithms

MD5; Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 219 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (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

  • CentOS 5.5 (single-user mode)

Validation history

DateTypeLab
2012-11-05InitialEWA - 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: 2012-11-05

Source documents