808bits

Juniper Networks SRX5600 and SRX5800 Services Gateways

FIPS 140-2 certificate #1602 · 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 and security devices installed as indicated in the Security Policy

Certificate

Certificate number1602
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorJuniper Networks, Inc. · website
Hardware versions(SRX5600BASE-AC, SRX5600BASE-DC, SRX5800BASE-AC and SRX5800BASE-DC) with JNPR-FIPS-TAMPER-LBLS
Firmware versions10.4R4

Module description

Juniper Networks SRX5000 line of services gateways is the next generation solution for securing the ever increasing network infrastructure and applications requirements for both enterprise and service provider environments. Designed from the ground up to provide flexible processing scalability, I/O scalability, and services integration, the SRX5000 line can meet the network and security requirements of data center hyper-consolidation, rapid managed services deployments, and aggregation of security solutions.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES1573, 1578
DSA484
HMAC920, 924
RNG847
RSA766
SHS1393, 1397
Triple-DES1030, 1034

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)

Validation history

DateTypeLab
2011-09-20InitialICSA
2011-11-08UpdateICSA
2013-12-11Update

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: 2011-09-20, 2011-11-08, 2013-12-11

Source documents