808bits

FireEye NX Series: NX1500V, NX2500V, NX2550V, NX4500V, NX6500V

FIPS 140-2 certificate #4006 · FireEye, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and installed, initialized and configured as specified in Section 3 of the Security Policy.

Certificate

Certificate number4006
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorFireEye, Inc. · website
Software versions9.0.3

Module description

The FireEye Network Threat Prevention Platform identifies and blocks zero-day Web exploits, droppers (binaries), and multi-protocol callbacks to help organizations scale their advanced threat defenses across a range of deployments, from the multi-gigabit headquarters down to remote, branch, and mobile offices. FireEye Network with Intrusion Prevention System (IPS) technology further optimizes spend, substantially reduces false positives, and enables compliance while driving security across known and unknown threats.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AESC1749
CKGvendor affirmed
CVLC1749
DRBGC1749, C2043
DSAC1749
ECDSAC1749
HMACC1749, C2043
KAS-SSCvendor affirmed
KTS
KTS
RSAC1749
SHSC1749, C2043
Triple-DESC1749

Allowed algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • FEYE 9.0 on VMware ESXi 6.7 running on Dell PowerEdge R630 with Intel Xeon E5 (single-user mode)

Validation history

DateTypeLab
2021-08-10InitialAcumen 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: 2021-08-10

Source documents