808bits

FireEye CMS Series: CM2500V, CM7500V

FIPS 140-2 certificate #3127 · FireEye, Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode.

Certificate

Certificate number3127
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorFireEye, Inc. · website
Software versions8.0

Module description

The FireEye CM series is a group of management platforms that consolidates the administration, reporting, and data sharing of the FireEye NX, EX, FX and AX series in one easy-to-deploy, network-based platform. Within the FireEye deployment, the FireEye CM enables real-time sharing of the auto-generated threat intelligence to identify and block advanced attacks targeting the organization. It also enables centralized configuration, management, and reporting of FireEye platforms.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4775
CKGvendor affirmed
CVL1419, 1420
DRBG1653
DSA1286
ECDSA1200
HMAC3185
KTS
KTS
RSA2613, 2616
SHS3916, 3919
Triple-DES2537

Allowed algorithms

Diffie-Hellman (CVL Cert. #1419 with CVL Cert. #1420, key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #1419 with CVL Cert. #1420, key agreement; key establishment methodology provides 128 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • FEYEOS 8.0 on VMware ESXi 6.5 running on Dell R630 (single-user mode)

Validation history

DateTypeLab
2018-02-14InitialAcumen Security

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: 2018-02-14

Source documents