808bits

Juniper Networks LN1000 Mobile Secure Router

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

Juniper Networks LN1000 Mobile Secure Router, from Juniper Networks, Inc., holds FIPS 140-2 certificate #1718 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: The tamper evident seals and security devices installed as indicated in the Security Policy

Certificate

Certificate number1718
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorJuniper Networks, Inc. · website
Hardware versionsLN1000-V with JNPR-FIPS-TAMPER-LBLS
Firmware versions11.2S4

Module description

Quoted from the NIST CMVP entry for this certificate.

Juniper Networks LN1000 Mobile Secure Router is an edge access router that delivers a high-performance routing firewall and intrusion detection service (IDS). The LN1000 addresses the growing demand for a network access presence in military, first responder and transportation vehicles, mining and exploration equipment, unmanned aircraft, and power grids.

Security level exceptions

  • Design Assurance: Level 3

Approved algorithms (7)

AlgorithmCAVP certificates
AES1956, 1957
DSA624
HMAC1178, 1179
RNG1028
RSA1013
SHS1715, 1716
Triple-DES1269, 1270

Other algorithms

RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant); Diffie-Hellman (key agreement; key establishment methodology provides 96 bits of encryption strength; non-compliant)

Validation history

DateTypeLab
2012-05-07InitialICSA
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: 2012-05-07, 2013-12-11

Source documents