808bits

Juniper Networks vSRX Virtual Firewall

FIPS 140-2 certificate #3336 · 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 number3336
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorJuniper Networks, Inc. · website
Software versionsJunos OS 17.4R1-S1

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
AES5305, 5306, 5341
CVL1771, 1772
DRBG2040, 2044, 2045
ECDSA1390, 1391
HMAC3502, 3506, 3509, 3510, 3538
KTS
KTS
RSA2840, 2841
SHS4256, 4260, 4263, 4264, 4292
Triple-DES2681, 2682, 2700

Allowed algorithms

Diffie-Hellman (CVL Certs. #1771 and #1772, key agreement; key establishment methodology provides between 112 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #1771 and #1772, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); NDRNG

Tested configurations

  • Junos OS 17.4R1-S1 on VMWare ESXi 6.0 running on a HP ProLiant DL380 Gen9 Server with Intel Xeon E5 (single-user mode)

Validation history

DateTypeLab
2018-12-03InitialAcumen 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-12-03

Source documents