808bits

SSG 140

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

SSG 140, from Juniper Networks, Inc., holds FIPS 140-2 certificate #1171 at overall level 2. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

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 number1171
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorJuniper Networks, Inc. · website
Hardware versionsP/N SSG-140
Firmware versionsScreenOS 6.2.0r3

Module description

Quoted from the NIST CMVP entry for this certificate.

The SSG 140 is a high-performance security platform for branch offices and small/medium sized standalone businesses that want to stop internal and external attacks, prevent unauthorized access, and achieve regulatory compliance. The SSG 140 is a modular platform that delivers more than 350 Mbps of stateful firewall traffic and 100 Mbps of IPSec VPN traffic.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Cryptographic Module Ports and Interfaces: Level 3
  • Roles, Services, and Authentication: Level 3
  • Cryptographic Key Management: Level 3
  • Design Assurance: Level 3

Approved algorithms (8)

AlgorithmCAVP certificates
AES869
DSA317
ECDSA106
HMAC485
RNG499
RSA420
SHS863
Triple-DES714

Other algorithms

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

Validation history

DateTypeLab
2009-08-18InitialUL Verification Services, Inc.
2010-01-28Update
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: 2009-08-18, 2010-01-28, 2013-12-11

Source documents