808bits

FireEye HX Series: HX 4400, HX 4400D, HX 4402, HX 9402

FIPS 140-2 certificate #2581 · 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. When installed, initialized and configured as specified in Section 3 of the Security Policy

Certificate

Certificate number2581
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorFireEye, Inc.
Hardware versionsHX 4400, HX 4400D, HX 4402, HX 9402
Firmware versions3.1.0

Module description

The FireEye HX series appliances enable security operations teams to correlate network and endpoint activity. Organizations can automatically investigate alerts generated by FireEye Threat Prevention Platforms, log management, and network security products, apply intelligence from FireEye to continuously validate Indicators of Compromises on the endpoints and identify if a compromise has occurred and assess the potential risk.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES3447
CVL533
DRBG843
ECDSA696
HMAC2195
RSA1758, 1759
SHS2836, 2837
Triple-DES1941

Other algorithms

Diffie-Hellman (CVL Cert. #533, key agreement; key establishment methodology provides 112 or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength); ECDH (key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength); MD5; DES; RC4; HMAC-MD5; NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2016-03-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: 2016-03-14

Source documents