FireEye MX Series: MX 900, MX 8400
FireEye MX Series: MX 900, MX 8400, from FireEye, Inc., holds FIPS 140-2 certificate #2580 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.
Certificate
| Certificate number | 2580 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | FireEye, Inc. |
| Hardware versions | MX 900, MX 8400 |
| Firmware versions | 2.0.3 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The FireEye MX series appliances are mobile management platforms that work in conjunction with the FireEye MTP App to assimilate and disperse threat information to mobile endpoints, and offer integration with MDM solutions for a true detect to fix solution.
Security level exceptions
- Roles, Services, and Authentication: Level 3
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms (8)
| Algorithm | CAVP certificates |
|---|---|
| AES | 3447 |
| CVL | 533 |
| DRBG | 843 |
| ECDSA | 696 |
| HMAC | 2195 |
| RSA | 1758, 1759 |
| SHS | 2836, 2837 |
| Triple-DES | 1941 |
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
| Date | Type | Lab |
|---|---|---|
| 2016-03-14 | Initial | Acumen 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