808bits

WildFire WF-500

FIPS 140-2 certificate #3102 · 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 and with the tamper evident seals and opacity shields installed as indicated in the Security Policy

Certificate

Certificate number3102
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorPalo Alto Networks · website
Hardware versionsP/N: 910-000097-00G Rev G; FIPS Kit P/N: 920-000145 Version Rev 00A
Firmware versions8.0.3, 8.0.9, 8.0.12 or 8.0.13

Module description

WildFire WF-500 identifies unknown malware, zero-day exploits, and Advanced Persistent Threats (APTs) through dynamic analysis, and automatically disseminates protection in near real-time to help security teams meet the challenge of advanced cyber-attacks

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Roles, Services, and Authentication: Level 3
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4532
CKGvendor affirmed
CVL1211, 1212, 1213, 1214
DRBG1489
DSA1207
ECDSA1103
HMAC2990
KASvendor affirmed
KTS
KTS
RSA2467
SHS3713

Allowed algorithms

Diffie-Hellman (CVL Cert. #1211 with CVL Cert. #1212, key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • N/A

Validation history

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

Source documents