808bits

McAfee Virtual SIEM Cryptographic Module

FIPS 140-2 certificate #2067 · McAfee, Inc. · data as of 2026-09-03

McAfee Virtual SIEM Cryptographic Module, from McAfee, Inc., holds FIPS 140-2 certificate #2067 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 number2067
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 Virtual SIEM Cryptographic Module provides cryptographic services required by the McAfee SIEM virtual environments.

Security level exceptions

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

Approved algorithms (9)

AlgorithmCAVP certificates
AES2228, 2231
CVL32, 35
DSA689, 692
ECDSA342, 345
HMAC1356, 1359
RNG1114, 1117
RSA1140, 1143
SHS1916, 1919
Triple-DES1394, 1397

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 on VMWare ESXi 5.0 running on a McAfee SIEM appliance

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