Set Up the ESM to Communicate with WildFire
Table of Contents
4.2 (EoS)
Expand all | Collapse all
-
- Set Up the Endpoint Infrastructure
- Activate Traps Licenses
-
- Endpoint Infrastructure Installation Considerations
- TLS/SSL Encryption for Traps Components
- Configure the MS-SQL Server Database
- Install the Endpoint Security Manager Server Software
- Install the Endpoint Security Manager Console Software
- Manage Proxy Communication with the Endpoint Security Manager
- Load Balance Traffic to ESM Servers
-
- Malware Protection Policy Best Practices
- Malware Protection Flow
- Manage Trusted Signers
-
- Remove an Endpoint from the Health Page
- Install an End-of-Life Traps Agent Version
-
-
- Traps Troubleshooting Resources
- Traps and Endpoint Security Manager Processes
- ESM Tech Support File
-
- Access Cytool
- View the Status of the Agent Using Cytool
- View Processes Currently Protected by Traps Using Cytool
- Manage Logging of Traps Components Using Cytool
- Restore a Quarantined File Using Cytool
- View Statistics for a Protected Process Using Cytool
- View Details About the Traps Local Analysis Module Using Cy...
- View Hash Details About a File Using Cytool
Set Up the ESM to Communicate with WildFire
WildFire integration is enabled by default;
however, you must set up the ESM to communicate with WildFire.
- From the ESM Console, select SettingsESMWildFire.
- Enable WildFire communication settings:
- Select Allow External Communication with WildFire to enable the ESM to check hashes with WildFire.
- Select Allow Upload Executable Files to WildFire to enable the ESM to send files to WildFire for analysis. Clearing this upload option enables the ESM Server to check verdicts with WildFire but not send files for analysis.
- To Use Private Cloud (Requires a WF-500 appliance), see Set Up a Private WildFire Cloud.
- In the Unknown Verdicts Recheck Interval (Minutes) field, enter the frequency (in minutes) at which the ESM Server resubmits hashes to WildFire for unknown files. A file can have an unknown verdict if it is the first time an endpoint submits the hash to the server or if WildFire has not, yet, analyzed or finished analyzing the file (range is 0 to 100,000; default is 15; a value of 0 is evaluated as 1).
- In the Known Verdicts Recheck Interval (Minutes) field, enter the frequency (in minutes) at which the ESM Server rechecks with WildFire for the value of known benign or malicious hashes (range is 0 to 100,000; default is 720; a value of 0 is evaluated as 1).
- In the Upload Retry Interval (Minutes) field, enter the frequency (in minutes) at which the ESM Server attempts to re-upload any files that did not upload to WildFire successfully (range is 0 to 100,000; default is 240; a value of 0 is evaluated as 1).
- Enter the WildFire web address (for example, https://wildfire.paloaltonetworks.com) that
the ESM will use to check hashes and submit samples. To forward
samples to a local WF-500 appliance, see Set Up
a Private WildFire Cloud.The WildFire API Key is required only for a private WildFire cloud.
- By default, the ESM Server submits files up to 100MB to WildFire for analysis. To change the Maximal File Size (MB), enter a value from 1 to 100 MB. Files that exceed the maximum size are not submitted to WildFire either automatically or manually.
- Save your changes.