JUNOS-FIPS-L2 Cryptographic Module
JUNOS-FIPS-L2 Cryptographic Module, from Juniper Networks, Inc., holds FIPS 140-2 certificate #736 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.
Certificate
| Certificate number | 736 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Juniper Networks, Inc. · website |
Module description
Quoted from the NIST CMVP entry for this certificate.
The JUNOS-FIPS-L2 Cryptographic Module is a multi-chip standalone cryptographic module (for Juniper Networks T-Series and M-Series routers) that executes JUNOS-FIPS firmware. JUNOS-FIPS is a release of the JUNOS operating system, the first routing operating system designed specifically for the Internet. JUNOS is currently deployed in the largest and fastest-growing networks worldwide. A full suite of industrial-strength routing protocols, flexible policy language, and leading MPLS implementation efficiently scale to large numbers of network interfaces and routes.
Security level exceptions
- Design Assurance: Level 3
Approved algorithms (7)
| Algorithm | CAVP certificates |
|---|---|
| AES | 259, 260 |
| DSA | 137 |
| HMAC | 70, 71, 72, 73, 79 |
| RNG | 93 |
| RSA | 69 |
| SHS | 336, 337, 338, 339, 340 |
| Triple-DES | 341, 342, 343, 344 |
Other algorithms
DES (Certs. #316, #317, #318 and #319); MD5; Diffie-Hellmann (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
| Date | Type | Lab |
|---|---|---|
| 2007-02-06 | Initial | UL Verification Services, Inc. |
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: 2007-02-06