808bits

McAfee SIEM Cryptographic Module

FIPS 140-2 certificate #2068 · McAfee, Inc. · data as of 2026-10-21

McAfee SIEM Cryptographic Module, from McAfee, Inc., holds FIPS 140-2 certificate #2068 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: The module generates cryptographic keys whose strengths are modified by available entropy. No assurance of the minimum strength of generated keys.

Certificate

Certificate number2068
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMcAfee, Inc. · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The McAfee SIEM Cryptographic Module provides cryptographic services required by the McAfee SIEM environments.

Security level exceptions

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

Approved algorithms (9)

AlgorithmCAVP certificates
AES2229, 2230
CVL33, 34
DSA690, 691
ECDSA343, 344
HMAC1357, 1358
RNG1115, 1116
RSA1141, 1142
SHS1917, 1918
Triple-DES1395, 1396

Other algorithms

MD5; Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 160 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • McAfee Nitro OS 9.1 running on McAfee SIEM Appliance (single-user mode)

Validation history

DateTypeLab
2013-12-24InitialEWA - 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: 2013-12-24

Source documents