808bits

MX Series 3D Universal Edge Routers with the Multiservices DPC

FIPS 140-2 certificate #2052 · Juniper Networks, Inc. · data as of 2026-08-28
Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: The tamper evident seals installed as indicated in the Security Policy

Certificate

Certificate number2052
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip standalone
VendorJuniper Networks, Inc. · website
Hardware versions[(MX240 with one to two 750-024064), (MX480 and MX960 with one to four 750-024064)] with (750-021524 and RE-S-2000-4096-S) and JNPR-FIPS-TAMPER-LBL
Firmware versionsJUNOS-FIPS 10.4R11

Module description

MX Series 3D Universal Edge Routers is a family of Ethernet routers designed to meet very large scale and medium-to-small size applications. It is capable of supporting business, mobile, and residential, services in even the fastest-growing networks and markets. With the Multiservices DPC (the MX Series) provides dedicated high-performance processing for flows and sessions, and integrates advanced security capabilities that protect the network infrastructure as well as user data.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES762, 2218, 2221, 2222
DSA688
HMAC417, 1348, 1349, 1351, 1352
RNG1112
RSA1137
SHS769, 1908, 1909, 1912, 1913
Triple-DES667, 1388, 1390, 1391

Other algorithms

RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant); Diffie-Hellman (key agreement; key establishment methodology provides 96 bits of encryption strength; non-compliant); SSH KDF (non-compliant); IKEv1 KDF (non-compliant); NDRNG; ANSI X9.62 RNG (non-compliant)

Validation history

DateTypeLab
2013-12-05InitialICSA

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: 2013-12-05

Source documents