808bits

Palo Alto Networks VM-Series

FIPS 140-2 certificate #3144 · Palo Alto Networks · 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. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number3144
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorPalo Alto Networks · website
Software versions8.0.3, 8.0.6, 8.0.9, 8.0.12 or 8.0.13

Module description

The VM-Series allows you to protect your applications and data from cyber threats with our next-generation firewall security and advanced threat prevention features.

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
AES4526
CKGvendor affirmed
CVL1203, 1204, 1205
DRBG1486
DSA1205
ECDSA1101
HMAC2986
KASvendor affirmed
KTS
KTS
RSA2463
SHS3707

Allowed algorithms

Diffie-Hellman (CVL Certs. #1203 and #1204, key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • KVM on CentOS 7.2 running on a Dell Power Edge R730
  • Microsoft Hyper-V 2012R2 running on a Dell PowerEdge R730
  • VMware ESXi v5.5 running on a Dell PowerEdge R730
  • VMware ESXi v5.5 running on a PacStar 451 (single user mode)

Validation history

DateTypeLab
2018-03-05InitialUL Verification Services, Inc.
2018-06-18UpdateUL Verification Services, Inc.
2018-07-06UpdateUL Verification Services, Inc.
2018-10-31UpdateUL Verification Services, Inc.
2020-02-21UpdateUL 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: 2018-03-05, 2018-06-18, 2018-07-06, 2018-10-31, 2020-02-21

Source documents