Palo Alto Networks VM-Series
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy
Certificate
| Certificate number | 3479 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Palo Alto Networks · website |
| Software versions | 8.1.3 and 8.1.6 |
Module description
The Palo Alto Networks 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
| Algorithm | CAVP certificate |
|---|---|
| AES | 5902 |
| CKG | vendor affirmed |
| CVL | 2128, 2129, 2130, 2131 |
| DRBG | 2464 |
| DSA | 1497 |
| ECDSA | 1575 |
| HMAC | 3882 |
| KAS | vendor affirmed |
| KTS | |
| KTS | |
| RSA | 3090 |
| SHS | 4658 |
Allowed algorithms
Diffie-Hellman (CVL Cert. #2128 with CVL Cert. #2130, 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 with Intel Xeon E5-2630 CPU
- Microsoft Hyper-V 2012R2 running on a Dell PowerEdge R730 with Intel Xeon E5-2640 CPU (single user mode)
- VMware ESXi v5.5 running on a Dell PowerEdge R730 with Intel Xeon E5-2640 CPU
- VMware ESXi v5.5 running on a PacStar 451 with Intel Xeon E3-1248 CPU
Validation history
| Date | Type | Lab |
|---|---|---|
| 2019-06-27 | Initial | UL Verification Services, Inc. |
| 2020-02-21 | Update | UL 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: 2019-06-27, 2020-02-21