808bits

ePO Cryptographic Module

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

ePO Cryptographic Module, from McAfee, Inc., holds FIPS 140-2 certificate #1587 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 with module RSA BSAFE® Crypto-J validated to FIPS 140-2 under Cert. #1047 operating in FIPS mode and with module RSA BSAFE® Crypto-C Micro Edition validated to FIPS 140-2 under Cert. #1092 operating in FIPS mode

Certificate

Certificate number1587
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorMcAfee, Inc. · website
Software versions1.0, 1.1, 1.2, 1.3, or 1.4

Module description

Quoted from the NIST CMVP entry for this certificate.

McAfee ePO Cryptographic Module provides cryptographic operations for McAfee ePolicy Orchestrator (ePO), a security management software that allows enterprises to unify the management of numerous end-point, network, and data security products.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Design Assurance: Level 3

Approved algorithms (6)

AlgorithmCAVP certificates
AES670, 860
DSA311
RNG390, 492
RSA312, 412
SHS703, 855
Triple-DES707

Other algorithms

NDRNG

Tested configurations

  • Windows XP (x86 32 bit) (single-user mode)

Validation history

DateTypeLab
2011-08-05InitialCOACT INC CAFE LAB
2011-11-17UpdateCOACT INC CAFE LAB
2012-04-02UpdateCOACT INC CAFE LAB
2012-08-16UpdateCOACT INC CAFE LAB
2013-01-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-08-05, 2011-11-17, 2012-04-02, 2012-08-16, 2013-01-04

Source documents