808bits

Juniper Networks SSG 5 and SSG 20

FIPS 140-2 certificate #900 · 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

Certificate

Certificate number900
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorJuniper Networks, Inc. · website
Hardware versionsP/N SSG-5 and SSG-20
Firmware versionsScreenOS 5.4.0r4, v5.4.0r5, 5.4.0r6, 5.4.0r7, 5.4.0r8, 5.4.0r9, 5.4.0r10, 5.4.0r11, 5.4.0r12, 5.4.0r13, 5.4.0r14, 5.4.0r15, 5.4.0r16, 5.4.0r17, 5.4.0r18 and 5.4.0r19

Module description

The Juniper Networks Secure Services Gateway 5 (SSG 5) and Secure Services Gateway 20 (SSG 20) are purpose-built security appliances that deliver a perfect blend of performance, security and LAN\WAN connectivity for small branch office and small business deployments. Traffic flowing in and out of the branch office can be protected from worms, Spyware, Trojans, and malware by a complete set of Universal Threat Management (UTM) security features including Stateful firewall, IPSec VPN, IPS, Antivirus (includes Anti-Spyware, Anti-Adware, Anti-Phishing), Anti-Spam, and Web Filtering.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • EMI/EMC: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES526
DSA217
HMAC277
RNG302
RSA236
SHS599
Triple-DES533

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 97 bits of encryption strength; non-compliant); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); DES; MD5

Validation history

DateTypeLab
2008-01-16InitialICSA
2008-07-10Update
2009-05-18Update
2011-01-20UpdateICSA
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: 2008-01-16, 2008-07-10, 2009-05-18, 2011-01-20, 2013-12-11

Source documents