McAfee Firewall Enterprise Control Center
McAfee Firewall Enterprise Control Center, from McAfee, Inc., holds FIPS 140-2 certificate #1851 at overall level 2. 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 | 1851 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | McAfee, Inc. · website |
| Hardware versions | [FWE-C1015 and FIPS Kit: FWE-CC-FIPS-KIT1], [FWE-C2050 and FIPS Kit: FWE-CC-FIPS-KIT2] and [FWE-C3000 and FIPS Kit: FWE-CC-FIPS-KIT2] |
| Firmware versions | 5.2.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
McAfee Firewall Enterprise Control Center simplifies the management of multiple McAfee Firewall Enterprise appliances. Control Center enables centralized management and monitoring of the McAfee Firewall Enterprise solutions, allowing network administrators to centrally define firewall policy, deploy updates and inventory their firewall products.
Approved algorithms (8)
| Algorithm | CAVP certificates |
|---|---|
| AES | 1831, 1897 |
| DRBG | 163 |
| DSA | 575, 599 |
| HMAC | 1085, 1137 |
| RNG | 963, 1009 |
| RSA | 920, 972 |
| SHS | 1611, 1666 |
| Triple-DES | 1184, 1233 |
Other algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant); RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength); MD5
Validation history
| Date | Type | Lab |
|---|---|---|
| 2012-11-29 | Initial | EWA - Canada |
| 2012-12-12 | Update |
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: 2012-11-29, 2012-12-12