SSG 5 and SSG 20
SSG 5 and SSG 20, from Juniper Networks, Inc., holds FIPS 140-2 certificate #1170 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.
Caveat: When operated in FIPS mode
Certificate
| Certificate number | 1170 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Juniper Networks, Inc. · website |
| Hardware versions | P/Ns SSG-5 (SSG 5) and SSG-20 (SSG 20) |
| Firmware versions | ScreenOS 6.2.0r3 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The SSG 5 and SSG 20 are high-performance security platforms for small branch office and standalone businesses that want to stop internal and external attacks, prevent unauthorized access and achieve regulatory compliance. Both the SSG 5 and SSG 20 deliver 160 Mbps of stateful firewall traffic and 40 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)
| Algorithm | CAVP certificates |
|---|---|
| AES | 866, 870 |
| DSA | 314, 318 |
| ECDSA | 103, 107 |
| HMAC | 482, 486 |
| RNG | 496, 500 |
| RSA | 417, 421 |
| SHS | 860, 864 |
| Triple-DES | 711, 715 |
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
| Date | Type | Lab |
|---|---|---|
| 2009-08-18 | Initial | UL Verification Services, Inc. |
| 2010-01-28 | Update | |
| 2013-12-11 | Update |
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