808bits

FireEye EX Series: EX3500, EX5500, EX8400, EX8500

FIPS 140-2 certificate #4056 · FireEye, Inc. · data as of 2026-09-08

FireEye EX Series: EX3500, EX5500, EX8400, EX8500, from FireEye, Inc., holds FIPS 140-2 certificate #4056 at overall level 1. The validation is active, with a sunset date of 2026-09-21. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Active. Sunset date 2026-09-21, 11 days away. This is the FIPS 140-2 sunset: after it, agencies may keep the module only in existing systems.
Caveat: When operated in FIPS mode and installed, initialized and configured as specified in Section 3 of the Security Policy

Certificate

Certificate number4056
StandardFIPS 140-2
Statusactive
Sunset date2026-09-21
Overall level1
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorFireEye, Inc. · website
Hardware versionsEX3500, EX5500, EX8400, EX8500
Firmware versions9.0.3

Module description

Quoted from the NIST CMVP entry for this certificate.

The FireEye EX series secures against advanced email attacks. As part of the FireEye Threat Prevention Platform, the FireEye EX uses signature-less technology to analyze every email attachment and successfully quarantine spear-phishing emails used in advanced targeted attacks.

Security level exceptions

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

Approved algorithms (12)

AlgorithmCAVP certificates
AESC1720
CKGvendor affirmed
CVLC1720
DRBGC1720, C1934
DSAC1720
ECDSAC1720
HMACC1720, C1934
KAS-SSCvendor affirmed
KTS
RSAC1720
SHSC1720, C1934
Triple-DESC1720

Allowed algorithms

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

Tested configurations

  • N/A

Validation history

DateTypeLab
2021-10-28InitialAcumen 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 active
  • Validation dates on record: 2021-10-28

Source documents