WildFire Best Practices
- Follow the best practices to secure your network from Layer 4 and Layer 7 evasions to ensure reliable content identification and analysis. Specifically, make sure to implement the best practices for TCP settings () and Content-ID™ settings (DeviceSetupSessionTCP Settings).DeviceSetupContent-IDContent-ID Settings
- Use the default WildFire Analysis profile to define the traffic that the firewall should forward for WildFire analysis (). The default WildFire Analysis profile ensures complete WildFire coverage for all traffic that your Security policy allows—it specifies that all supported file types across all applications are forwarded for WildFire analysis regardless whether the files are uploaded or downloaded.ObjectsSecurity ProfilesWildFire AnalysisIf you choose to create a custom WildFire Analysis profile, it is a best practice to still set the profile to forwardanyfile type. This enables the firewall to automatically begin forwarding file types as they become supported for WildFire analysis.WildFire Action settings in the Antivirus profile may impact traffic if the traffic generates a WildFire signature that results in a reset or a drop action. You can exclude internal traffic, such as software distribution applications through which you deploy custom-built programs, to transition safely to best practices because WildFire may identify custom-built programs as malicious and generate a signature for them. Checkto see if any internal custom-built programs trigger WildFire signatures.MonitorLogsWildFire Submissions
- While you are configuring the firewall to forward files for WildFire analysis (PAN-OS 8.1, PAN-OS 9.0, PAN-OS 9.1), review the fileSize Limitfor all supported file types. Set theSize Limitfor all file types to the default limits. (Selectand edit the General Settings to adjust file size limits based on file type. You can view the Help information to find the default size limit for each file type).DeviceSetupWildFireAbout the Default File Size Limits for WildFire ForwardingThe default file size limits on the firewall are designed to include the large majority of malware in the wild (which is smaller than the default size limits) and to exclude large files that are very unlikely to be malicious and can impact WildFire file-forwarding capacity. Because the firewall has a specific capacity reserved to forward files for WildFire analysis, forwarding high numbers of large files might cause the firewall to skip forwarding some files. This condition can occur when the maximum file size limits are configured for a file type that is traversing the firewall at a high rate. In this case, a potentially malicious file might not be forwarded for WildFire analysis. Consider this possible condition if you would like to increase the size limit for files other than PEs beyond their default size limit.The following graph is a representative illustration of the distribution of file sizes for malware as observed by the Palo Alto Networks threat research team. The firewall default file size settings can be increased to the maximum file size setting to gain a relatively small increase in the malware catch rate for each file type.If you are concerned specifically about uncommonly large malicious files, then you can increase file size limits beyond the default settings. In these cases, the following settings are recommended to catch rare, very large malicious files.Selectand edit General Settings to adjust theDeviceSetupWildFireSize Limitfor each file type:File TypePAN-OS 9.0/9.1 File-Forwarding Maximum Size RecommendationsPAN-OS 8.1 File-Forwarding Maximum Size RecommendationsPAN-OS 8.0 File-Forwarding Maximum Size Recommendationspe16MB10MB10MBapk10MB10MB10MB3,072KB500KB500KBms-office16,384KB500KB500KBjar5MB5MB5MBflash5MB5MB5MBMacOSX10MB1MB1MBarchive50MB10MB10MBlinux50MB10MB10MBscript20KB20KB—
Recommended For You
Recommended videos not found.