808bits

HPE Juniper Networking QFX5120-48YM

FIPS 140-3 certificate #5509 · HPE Juniper Networking · data as of 2026-09-01
Active. Sunset date 2031-08-31, 1824 days away.
Caveat: When operated in approved mode. No assurance of minimum security of SSPs (e.g., keys, bit strings) that are externally loaded, or of SSPs established with externally loaded SSPs.

Certificate

Certificate number5509
StandardFIPS 140-3
Statusactive
Sunset date2031-08-31
Overall level1
Module typeHardware
EmbodimentMultiChipStand
VendorHPE Juniper Networking · website

Module description

The HPE Juniper Networking QFX5120 Switch delivers high scale, high availability, and high performance for data center and campus deployments. The QFX5120 Switch is a versatile routing and switching platform addressing higher server access speed and campus distribution use cases while offering high-density 1GbE/10GbE/25GbE and 100GbE uplinks for collapsed spine data center or campus distribution deployments. The QFX5120-48YM is a 10GbE/25GbE/100GbE data center leaf and campus distribution switch.

Security level exceptions

  • Roles, services, and authentication: Level 3
  • Non-invasive security: N/A
  • Mitigation of other attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES-CBCA6551
AES-CBCA7286
AES-CMACA6551
AES-CTRA7286
AES-GCMAES 4545
AES-KWA6551
AES-XPNAES 4545
ECDSA KeyGen (FIPS186-4)A7286
ECDSA KeyVer (FIPS186-4)A7286
ECDSA SigGen (FIPS186-4)A7286
ECDSA SigVer (FIPS186-4)A7286
HMAC DRBGA6620
HMAC-SHA-1A7286
HMAC-SHA2-256A6620
HMAC-SHA2-256A7286
HMAC-SHA2-512A7286
KAS-ECC-SSC Sp800-56Ar3A7286
KAS-FFC-SSC Sp800-56Ar3A7286
KDF SP800-108A6551
KDF SSHA7286
RSA KeyGen (FIPS186-5)A7286
RSA SigGen (FIPS186-5)A7286
RSA SigVer (FIPS186-5)A7286
Safe Primes Key GenerationA7286
Safe Primes Key VerificationA7286
SHA-1A7286
SHA2-256A6620
SHA2-256A7286
SHA2-512A6550
SHA2-512A6620
SHA2-512A7286

Validation history

DateTypeLab
2026-09-01InitialAcumen 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-09-01: first observed by this tracker, status active
  • Validation dates on record: 2026-09-01

Source documents