808bits

Juniper Networks vSRX Virtual Firewall

FIPS 140-2 certificate #3137 · 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

Certificate

Certificate number3137
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorJuniper Networks, Inc. · website
Software versionsJUNOS 15.1X49 - D100

Module description

The vSRX delivers a complete and integrated virtual security solution, including unified threat management(UTM), intrusion detection and prevention (IDP), granular application control and robust networking. It provides seamless automated life cycle management capabilities making it an ideal solution for Service Providers, Cloud and Enterprise deployments. The vSRX supports Juniper Networks Contrail, OpenContrail, Openstack and other third-party solutions.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES4719, 4720, 4723
CKGvendor affirmed
CVL1362, 1391
DRBG1608, 1609
ECDSA1166, 1167
HMAC3136, 3137, 3140
KTS
KTS
RSA2572, 2573
SHS3864, 3865, 3868, 3895
Triple-DES2501, 2502, 2505

Allowed algorithms

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

Tested configurations

  • JUNOS 15.1X49-D100 on VMWare ESXi 5.5 on a Server HP ProLiant DL380 Gen9 (single-user mode)

Validation history

DateTypeLab
2018-02-26InitialAcumen Security

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-02-26

Source documents