808bits

McAfee Endpoint Encryption for PCs

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

McAfee Endpoint Encryption for PCs, from McAfee, Inc., holds FIPS 140-2 certificate #1601 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 number1601
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMcAfee, Inc. · website
Software versions5.2.6

Module description

Quoted from the NIST CMVP entry for this certificate.

McAfee Endpoint Encryption for PCs is a Software Only Module which resides on general purpose computer systems. The module is used for whole disk encryption that enables users to secure sensitive data stored on hard disk drives in the event of a lost or stolen workstation or laptop computer. McAfee Endpoint Encryption for PCs is an enterprise class software product that is centrally managed and can be deployed to large heterogeneous enterprise environments.

Security level exceptions

  • Design Assurance: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES1366
DSA446
RNG752
SHS1247

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); NDRNG

Tested configurations

  • Windows Vista 64-bit (single-user mode)
  • Windows XP 32-bit

Validation history

DateTypeLab
2011-09-08InitialCOACT INC CAFE LAB
2011-10-04UpdateCOACT INC CAFE LAB

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-09-08, 2011-10-04

Source documents