Juniper Networks RE1800 and RE2600 Routing Engines Cryptographic Modules
Certificate
| Certificate number | 2451 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Hardware |
| Embodiment | Multi-chip embedded |
| Vendor | Juniper Networks, Inc. · website |
| Hardware versions | P/Ns RE-S-1800X2-XXG, RE-S-1800X4-XXG, RE-S-EX9200-1800X4-XXG, RE-DUO-C1800-16G, RE-B-1800X1-4G, RE-A-1800X2-XXG, RE-DUO-C2600-16G, 520-052564 |
| Firmware versions | Junos 14.1R4 with Junos FIPS mode utilities 14.1R4 |
Module description
The Juniper Networks RE1800 and RE2600 Routing Engines, are multi-chip embedded cryptographic modules that control a router or switch's interfaces, system management, and user access to the device. The RE runs Junos 14.1R4 with the FIPS mode package. The RE is compatible with the Juniper Networks MX Series 3D Universal Edge Routers, EX Series Switches, T Series Routers, M Series Multiservice Edge Routers, and PTX Series Packet Transport Routers. These devices provide dedicated high-performance flow processing and integrate advanced security capabilities.
Security level exceptions
- Cryptographic Module Specification: Level 3
- Roles, Services, and Authentication: Level 3
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 3296 |
| CVL | 470 |
| DRBG | 752 |
| ECDSA | 639 |
| HMAC | 2092, 2094 |
| RSA | 1685 |
| SHS | 2734, 2735, 2736 |
| Triple-DES | 1879, 1880 |
Other algorithms
Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 192 bits of strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of strength); HMAC-SHA-1-96 (HMAC Certs. #2092 and #2094); NDRNG
Validation history
| Date | Type | Lab |
|---|---|---|
| 2015-09-30 | 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: 2015-09-30