SSG 520M and SSG 550M
SSG 520M and SSG 550M, from Juniper Networks, Inc., holds FIPS 140-2 certificate #1173 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 | 1173 |
|---|---|
| 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-520M (SSG 520M) and SSG-550M (SSG 550M) |
| Firmware versions | ScreenOS 6.2.0r3 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The SSG 500 Series consists of high-performance security platforms for regional branch office and medium-sized, standalone businesses that want to stop internal and external attacks, prevent unauthorized access and achieve regulatory compliance. The SSG 550/SSG 550M provides 1+ Gbps of stateful firewall performance and 500 Mbps of IPSec VPN performance, while the SSG 520/SSG 520M provides 650 Mbps of stateful firewall performance and 300 Mbps of IPSec VPN performance.
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)
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