808bits

Juniper Networks EX3300, EX4200, EX4500 Ethernet Switches

FIPS 140-2 certificate #2117 · 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: When operated in FIPS Mode and with the tamper evidence seals installed as indicated in the Security Policy

Certificate

Certificate number2117
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip standalone
VendorJuniper Networks, Inc. · website
Hardware versionsEX3300-24P, EX3300-24T, EX3300-24T-DC, EX3300-48T, EX3300-48T-BF, EX3300-48P, EX4200-24P, EX4200-24PX, EX4200-24T, EX4200-24F, EX4200-48P, EX4200-48PX, EX4200-48T, EX4500-40-FB and EX4500-40-BF with Tamper Evident Labels: 520-052564
Firmware versionsJUNOS 12.1R6.6

Module description

EX Series Ethernet switches deliver access, aggregation, and core layer switching services in branch, campus, and data center networks to ensure fast, secure, reliable delivery of data and applications. All EX Series Ethernet Switches run the same Junos operating system as other Juniper switches, routers, and security solutions, ensuring consistent, predictable behavior across the entire network infrastructure.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES2396, 2419, 2420, 2475
CVL81
DRBG324, 325, 338
DSA762
HMAC1488, 1489, 1504, 1505, 1518
RNG1187
RSA1251, 1252, 1264
SHS2058, 2059, 2076, 2077, 2094
Triple-DES1494, 1507, 1508, 1514

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 128 bits and 256 bits of encryption strength); NDRNG

Validation history

DateTypeLab
2014-03-28InitialICSA

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: 2014-03-28

Source documents