808bits

Juniper Networks MX240, MX480, MX960, MX2010, MX2020 3D Universal Edge Routers and EX9204, EX9208, EX9214 Ethernet Switches with RE1800 Routing Engine

FIPS 140-2 certificate #3416 · Juniper Networks, Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode, installed, initialized and configured as specified in Section 1.2 and 6 of the Security Policy

Certificate

Certificate number3416
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorJuniper Networks, Inc. · website
Hardware versionsMX240, MX480, MX960, MX2010, MX2020, EX9204, EX9208 and EX9214 with components identified in Security Policy Table 1
Firmware versionsJunos OS 17.3R2

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 .RE1800 routing engines provide enhanced scaling and performance. Juniper Networks EX9200 series Ethernet Switches provide high performance, scalable connectivity, and carrier-class reliability for high-density environments with a a full suite of Layer 2 and Layer 3 switching capabilities along with firewall filters, multicast, hardware tunneling and Qos.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES5089
CVL1641
DRBG1895, 1896
ECDSA1319
HMAC3392, 3393, 3394
KTS
KTS
SHS4138, 4139, 4140
Triple-DES2622

Allowed algorithms

EC Diffie-Hellman (CVL Cert. #1641, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-03-25InitialAcumen 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-03-25

Source documents