808bits

Juniper Networks NetScreen-204 and 208

FIPS 140-2 certificate #607 · Juniper Networks, Inc. · data as of 2026-09-13

Juniper Networks NetScreen-204 and 208, from Juniper Networks, Inc., holds FIPS 140-2 certificate #607 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 number607
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorJuniper Networks, Inc. · website
Hardware versionsP/N NS-204 and NS-208 Version 0110
Firmware versionsScreenOS 5.0.0r9a.h and 5.0.0r9b.h

Module description

Quoted from the NIST CMVP entry for this certificate.

The Juniper Networks NetScreen-204 and 208 are purpose-built internet security appliances that deliver firewall, VPN, and traffic shaping optimized for the most demanding environments such as medium and large enterprise offices, e-business sites, data centers, and carrier infrastructures.

Approved algorithms (7)

AlgorithmCAVP certificates
AES11
DSA132
HMAC52
RNG33
RSA24
SHS103
Triple-DES118

Other algorithms

DES (Cert. #174); MD5; Diffie-Hellman (key agreement, key establishment methodology provides 80 bits of encryption strength; non-compliant); RSA (key wrapping, key establishment methodology provides 80 bits of encryption strength; non-compliant)

Validation history

DateTypeLab
2005-12-12InitialUL Verification Services, Inc.
2006-01-26Update
2006-05-16Update
2006-06-14Update
2006-06-20Update
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: 2005-12-12, 2006-01-26, 2006-05-16, 2006-06-14, 2006-06-20, 2013-12-11

Source documents