808bits

Juniper Networks SRX345/SRX345-DUAL-AC with Junos 15.1X49-D110

FIPS 140-2 certificate #3247 · Juniper Networks, Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and with tamper-evident seals installed as indicated in the Security Policy

Certificate

Certificate number3247
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorJuniper Networks, Inc. · website
Hardware versionsSRX345, SRX345-DUAL-AC with JNPR-FIPS-TAMPER-LBLS
Firmware versionsJUNOS-FIPS-MODE 15.1X49-D110

Module description

The Juniper Networks SRX Series Services Gateways are a series of secure routers that provide essential capabilities to connect, secure, and manage work force locations sized from handfuls to hundreds of users. By consolidating fast, highly available switching, routing, security, and applications capabilities in a single device, enterprises can economically deliver new services, safe connectivity, and a satisfying end user experience.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4941, 4942, 4943
CKGvendor affirmed
CVL1542, 1543
DRBG1770
ECDSA1264, 1267
HMAC3289, 3290, 3291
KTS
KTS
RSA2688, 2693
SHS4030, 4031, 4032, 4033
Triple-DES2568, 2569, 2570

Allowed algorithms

Diffie-Hellman (CVL Certs. #1542 and #1543, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #1542 and #1543, key agreement; key establishment methodology provides 128 or 192 bits of encryption strength); NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2018-07-25InitialBAE SYSTEMS APPLIED INTELLIGENCE

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: 2018-07-25

Source documents