Document:WildFire® Administrator’s Guide
WildFire Deployments
Last Updated:
Wed May 06 13:22:31 PDT 2020
Table of Contents
Search the Table of Contents
-
- About the WF-500 Appliance
- Configure the WF-500 Appliance
- Set Up the WF-500 Appliance VM Interface
- Virtual Machine Interface Overview
- Configure the VM Interface on the WF-500 Appliance
- Connect the Firewall to the WF-500 Appliance VM Interface
- Enable WF-500 Appliance Analysis Features
- Set Up WF-500 Appliance Content Updates
- Enable Local Signature and URL Category Generation
- Submit Locally-Discovered Malware or Reports to the WildFire Public Cloud
- Upgrade a WF-500 Appliance
-
- WildFire Best Practices
- Forward Files for WildFire Analysis
- Forward Decrypted SSL Traffic for WildFire Analysis
- Verify WildFire Submissions
- Test a Sample Malware File
- Verify File Forwarding
- Manually Upload Files to the WildFire Portal
- Submit Malware or Reports from the WF-500 Appliance
- Firewall File Forwarding Capacity by Platform
-
- About WildFire Logs and Reporting
- Use the Firewall to Monitor Malware
- Configure WildFire Submissions Log Settings
- Monitor WildFire Submissions and Analysis Reports
- Set Up Alerts for Malware
- Use the WildFire Portal to Monitor Malware
- Configure WildFire Portal Settings
- Add WildFire Portal Users
- View Reports on the WildFire Portal
- WildFire Analysis Reports—Close Up
- WildFire Example
- Use the WildFire API
-
- WF-500 Appliance Software CLI Concepts
- WF-500 Appliance Software CLI Structure
- WF-500 Appliance Software CLI Command Conventions
- WF-500 Appliance CLI Command Messages
- WF-500 Appliance Command Option Symbols
- WF-500 Appliance Privilege Levels
- WildFire CLI Command Modes
- WF-500 Appliance CLI Configuration Mode
- WF-500 Appliance CLI Operational Mode
- Access the WF-500 Appliance CLI
- Use the WF-500 Appliance CLI
- Access WF-500 Appliance Operational and Configuration Modes
- Display WF-500 Appliance Software CLI Command Options
- Restrict WF-500 Appliance CLI Command Output
- Set the Output Format for WF-500 Appliance Configuration Commands
- WF-500 Appliance Configuration Mode Command Reference
- set deviceconfig setting wildfire
- set deviceconfig system update-schedule
- set deviceconfig system vm-interface
- WF-500 Appliance Operational Mode Command Reference
- create wildfire api-key
- delete wildfire api-key
- delete wildfire-metadata
- edit wildfire api-key
- load wildfire api-key
- request system raid
- request system wildfire-vm-image
- request wf-content
- save wildfire api-key
- set wildfire portal-admin
- show system raid
- show wildfire
- test wildfire registration
You can set up a Palo Alto Networks firewall to submit unknown samples to the Palo Alto Networks-hosted WildFire global cloud, to a locally-hosted WildFire private cloud, or you can enable the firewall to forward certain samples to a WildFire global cloud and certain samples to a WildFire private cloud:
A Palo Alto Networks firewall with can forward unknown files and email links to the WildFire global cloud or to one of three WildFire regional clouds that Palo Alto Networks owns and maintains. Choose the WildFire cloud to which you want to submit samples for analysis based on your location and your organization’s needs:
Each WildFire cloud—global and regional—analyzes samples and generates malware signatures independently of the other WildFire clouds. WildFire signatures are then shared globally, enabling WildFire users worldwide to benefit from malware coverage regardless of the location the malware was first detected. Review
WildFire File Type Support
to learn more about the file types that each cloud analyzes. If you have a WF-500 appliance, you can enable a WildFire Hybrid Cloud deployment, where the firewall can forward certain files to a WildFire public cloud, and other files to a WildFire private cloud for local analysis.
In a Palo Alto Networks private cloud deployment, Palo Alto Networks firewalls forward files to a WF-500 appliance on your corporate network that is being used to host a private cloud analysis location. A WildFire private cloud can receive and analyze files from up to 100 Palo Alto Networks firewalls.
Because the WildFire private cloud is a local sandbox, benign and grayware files it analyzes never leave your network. By default, the private cloud also does not send discovered malware outside of your network; however, you can choose to automatically forward malware to the WildFire public cloud for signature generation and distribution. In this case, The WildFire public cloud re-analyzes the sample, generates a signature to identify the sample, and distributes the signature to all Palo Alto Networks firewalls with Threat Prevention and WildFire licenses.
You can also
Enable Local Signature and URL Category Generation
on the WF-500 appliance. Signatures the WF-500 appliance generates are distributed to connected firewalls so that the firewalls can effectively block the malware the next time it is detected.
A firewall in a WildFire hybrid cloud deployment can forward certain samples to the Palo Alto Networks-hosted WildFire global cloud and other samples to a WildFire private cloud hosted by a WF-500 appliance. A WildFire hybrid cloud deployment allows the flexibility to analyze private documents locally and inside your network, while the WildFire public cloud analyzes files from the Internet. For example, forward Payment Card Industry (PCI) and Protected Health Information (PHI) data exclusively to the WildFire private cloud for analysis, while forwarding Portable Executables (PEs) to the WildFire public cloud for analysis. In a WildFire hybrid cloud deployment, offloading files to the public cloud for analysis allows you benefit from a prompt verdict for files that have been previously processed in the WildFire public cloud, and also frees up the WF-500 appliance capacity to process sensitive content. Additionally, you can forward certain file types to the WildFire public cloud that are not currently supported for WF-500 appliance analysis, such as Android Application Package (APK) files.
To set up hybrid cloud forwarding, see
Forward Files for WildFire Analysis .