808bits

WildFire 9.0 WF-500

FIPS 140-2 certificate #3895 · Palo Alto Networks, Inc. · data as of 2026-10-21

WildFire 9.0 WF-500, from Palo Alto Networks, Inc., holds FIPS 140-2 certificate #3895 at overall level 2. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. Moved to historical list due to sunsetting. 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 number3895
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorPalo Alto Networks, Inc. · website
Hardware versions910-000097-00G; FIPS Kit P/N: 920-000145-00A
Firmware versions9.0.9-h1

Module description

Quoted from the NIST CMVP entry for this certificate.

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

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

Approved algorithms (12)

AlgorithmCAVP certificates
AESC1005
CKGvendor affirmed
CVLC1005
DRBGC1005
DSAC1005
ECDSAC1005
HMACC1005
KAS
KAS-SSCA2670
KTS
RSAC1005
SHSC1005

Allowed algorithms

MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2021-04-15InitialUL Verification Services, Inc.
2022-07-05UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab

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: 2021-04-15, 2022-07-05

Source documents