808bits

Juniper Networks EX4300 Ethernet Switches

FIPS 140-2 certificate #3358 · 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, installed, initialized and configured as specified in Section 1.3 and 6 of the Security Policy.

Certificate

Certificate number3358
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorJuniper Networks, Inc. · website
Hardware versions[EX4300-24P, EX4300-24T and EX4300-48T with component EX-UM-4X4SFP] and [EX4300-32F with component EX-UM-8X8SFP]
Firmware versionsJunos OS 17.4R1-S4

Module description

Juniper Networks EX4300 Ethernet Switches combine the carrier-class reliability with the economics of stackable platforms, delivering a high-performance, scalable solution for data center and campus office environments. Offering a full suite of Layer 2 and Layer 3 switching capabilities. EX4300 switches offer 24, 32 or 48-port 10/100/1000BASE-T with redundant, hot-swappable power supplies and Power over Ethernet (PoE). The EX 4300 family supports 1Gigabit and 10 Gigabit MACSec support in both FIPS mode and non FIPS mode of operation as of Junos release 17.4R1-S4.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES1269, 5332, 5506, 5509
CVL1956
DRBG2177
ECDSA1479
HMAC3663, 3664, 3665
KAS-SSCvendor affirmed
KBKDF229
KTS
KTS
KTS
RSA2956
SHS4419, 4420, 4421
Triple-DES2773

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-02-04InitialAcumen Security
2021-03-12UpdateAcumen 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-04, 2021-03-12

Source documents