808bits

McAfee Endpoint Encryption for Files and Folders

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

McAfee Endpoint Encryption for Files and Folders, from McAfee, Inc., holds FIPS 140-2 certificate #1132 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 number1132
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMcAfee, Inc. · website
Software versions3.1.1.7 and 3.1.2.11

Module description

Quoted from the NIST CMVP entry for this certificate.

McAfee Endpoint Encryption for Files and Folders is a user transparent and high performing client software for encryption of files and folders on local drives, network shares, removable media and CD/DVD. E-mail attachments may also be encrypted for both internal and external recipients. In addition, the centralized McAfee Endpoint Encryption management system provides flexible and powerful management of encryption policies and keys, robust recovery tools, policy enforcement and remote deployment.

Approved algorithms (4)

AlgorithmCAVP certificates
AES891
DSA323
RNG512
SHS884

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant); RC5; AES (non-compliant)

Tested configurations

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

Validation history

DateTypeLab
2009-05-22InitialUL Verification Services, Inc.
2009-07-24Update

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: 2009-05-22, 2009-07-24

Source documents