808bits

Juniper Networks PTX1000 Packet Transport Router

FIPS 140-2 certificate #4504 · Juniper Networks, Inc. · data as of 2026-10-09

Juniper Networks PTX1000 Packet Transport Router, from Juniper Networks, Inc., holds FIPS 140-2 certificate #4504 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode, installed, initialized and configured as specified in Sections 1.2 and 6 of the Security Policy.

Certificate

Certificate number4504
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorJuniper Networks, Inc. · website
Hardware versionsPTX1000
Firmware versionsJunos OS 20.3X75

Module description

Quoted from the NIST CMVP entry for this certificate.

The Juniper Networks PTX1000 Packet Transport Router is a fixed-configuration router that supports 10-Gbps, 40-Gbps, and 100-Gbps port speeds in a compact 2U form factor, enabling service providers to organically distribute peering points throughout the network.

Security level exceptions

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

Approved algorithms (11)

AlgorithmCAVP certificates
AESA2359
CVLA2359
DRBGA2356, A2359
ECDSAA2359
ENT
HMACA2356, A2357, A2359
KAS
KAS-SSCA2359
KTS
RSAA2359
SHSA2356, A2357, A2359

Tested configurations

  • N/A

Validation history

DateTypeLab
2023-05-03InitialAcumen 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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2023-05-03

Source documents