808bits

MX240, MX480, and MX960 3D Universal Edge Routers with the Multiservices MPC and Junos 14.2X4-D10.11

FIPS 140-2 certificate #2690 · Juniper Networks, 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

Certificate

Certificate number2690
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorJuniper Networks, Inc. · website
Hardware versionsMX240, MX480 and MX960 with components identified in Security Policy Table 1
Firmware versionsJunos 14.2X4-D10.11

Module description

The MX 3D Universal Edge Routers deliver high performance, reliability, and scale to enable a cost-effective solution. 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.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES3955, 3956, 3957
CVL791, 792
DRBG1157, 1158
DSA1078, 1079
ECDSA869, 870
HMAC2575, 2576, 2577, 2578
RSA2019, 2020
SHS3261, 3262, 3263, 3264
Triple-DES2166, 2167, 2168

Other algorithms

ARCFOUR; BLOWFISH; CAST128; Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); DSA (non-compliant); EC Diffie-Hellman (key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); HMAC-MD5; HMAC-RIPEMD160; NDRNG; UMAC-128; UMAC-64

Tested configurations

  • N/A

Validation history

DateTypeLab
2016-07-28InitialUL Verification Services, Inc.
2017-05-02UpdateUL Verification Services, Inc.

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-07-28, 2017-05-02

Source documents