Juniper Networks MX240, MX480, MX960, MX2010, and MX2020 3D Universal Edge Routers with RE1800 Routing Engine and Multiservices MPC
Certificate
| Certificate number | 3386 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Juniper Networks, Inc. · website |
| Hardware versions | MX240, MX480, MX960, MX2010 and MX2020 with components identified in Security Policy Table 1 |
| Firmware versions | Junos OS 17.4R1-S1 |
Module description
Juniper Networks MX Series is a robust portfolio of SDN enabled routing platforms that provide industry leading system capacity, density, security and performance. Key features include support for a wide range of L2/L3 VPN services and advanced broadband network gateway functions, along with integrated routing, switching and security services. Multiservices MPC supports Layer 3 services such as stateful firewall, NAT, IPsec, active flow monitoring and RPM.
Security level exceptions
- Roles, Services, and Authentication: Level 3
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 5499, 5500, 5501 |
| CVL | 1949, 1950 |
| DRBG | 2168, 2169, 2170 |
| ECDSA | 1475, 1478 |
| HMAC | 3648, 3649, 3650, 3651, 3652 |
| KTS | |
| KTS | |
| RSA | 2950, 2951 |
| SHS | 4407, 4408, 4409, 4410, 4411 |
| Triple-DES | 2766, 2767, 2768 |
Allowed algorithms
Diffie-Hellman (CVL Cert. #1950, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #1949 and #1950, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); NDRNG
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2019-02-28 | 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: 2019-02-28