Which Cli Command Is Used to Verify Successful File Upload to Wildfire

Verify File Forwarding

Later on the firewall is set up to Frontwards Files for WildFire Analysis, use the following options to verify the connection betwixt the firewall and the WildFire public or private cloud, and to monitor file forwarding.

Several of the options to verify that a firewall is forwarding samples for WildFire analysis are CLI commands; for details on getting started with and using the CLI, refer to the PAN-Bone CLI Quick Start Guide.

Verify that the firewall is communicating with a WildFire server(due south).

Use the

test wildfire registration

command to verify that the firewall is connected to a WildFire private cloud, the WildFire public cloud, or both.

The following instance output is for a firewall in a individual clouddeployment:



The case output confirms that the firewall is continued to the WildFire private cloud, and is not continued to the WildFire public deject (public deject registration fails).

If the firewall is configured in a hybrid cloud deployment, check that the firewall is successfully registered with and connected to both the WildFire public cloud and a WildFire private cloud.

Verify the status of the firewall connection to the WildFire public and/or private cloud, including the total number of files forwarded by the firewall for analysis.

Use the

show wildfire status

command to:

Check the condition of the WildFire public and/or private cloud to which the firewall is connected. The condition

Idle

indicates that the WildFire deject (public or private) is ready to receive files for analysis.

Confirm the configured size limits for files forwarded by the firewall ().

Monitor file forwarding, including how the total count of files forwarded by the firewall for WildFire analysis. If the firewall is in a WildFire hybrid cloud deployment, the number of files forwarded to the WildFire public cloud and the WildFire individual deject are also displayed.

The post-obit example shows the

testify wildfire status

output for a firewall in a WildFire individual deject deployment:



To view forwarding information for only the WildFire public cloud or WildFire private cloud, use the post-obit commands:

show wildfire status channel public

show wildfire status aqueduct private

View samples forwarded by the firewall according to file type (including email links).

Use this option to confirm that email links are being forwarded for WildFire analysis, since only email links that receive a malicious or phishing verdict are logged as

WildFire Submissions

entries on the firewall, even if logging for benign and grayware samples is enabled. This is due to the sheer number of WildFire Submissions entries that would be logged for benign e-mail links.

Utilise the

evidence wildfire statistics

command to ostend the file types being forwarded to the WildFire public or individual cloud:

The control displays the output of a working firewall and shows counters for each file blazon that the firewall frontward for WildFire analysis. If a counter field shows 0, the firewall is non forwarding that file type.

Confirm that email links are being forwarded for analysis by checking that the following counters do not evidence zero:

FWD_CNT_APPENDED_BATCH

—Indicates the number of e-mail links added to a batch waiting for upload to WildFire.

FWD_CNT_LOCAL_FILE

— Indicates the total number of email links uploaded to WildFire.

Verify that a specific sample was forwarded by the firewall and cheque that condition of that sample.

This option can be helpful when troubleshooting to:

Confirm that samples that have non notwithstanding received a WildFire verdict were correctly forwarded by the firewall. Because

WildFire Submissions

are logged on the firewall only when WildFire analysis is consummate and the sample has received a WildFire verdict, apply this option to verify the firewall forwarded a sample that is currently undergoing WildFire analysis.

Track the status for a unmarried file or email link that was allowed according to your security policy, matched to a WildFire Analysis profile, and and so forwarded for WildFire analysis.

Check that a firewall in a hybrid cloud deployment is forwarding the correct file types and electronic mail links to either the WildFire public cloud or a WildFire private cloud.

Execute the following CLI commands on the firewall to view samples the firewall has forwarded WildFire assay:

View all samples forwarded by the firewall with the CLI control

debug wildfire upload-log

.

View simply samples forwarded to the WildFire public deject with the CLI command

debug wildfire upload-log aqueduct public

.

View only samples forwarded to the WildFire individual cloud with the CLI control

debug wildfire upload-log channel individual

.

The post-obit example shows the output for the 3 commands listed above when issued on a firewall in a WildFire public cloud deployment:



Monitor samples successfully submitted for WildFire analysis.

Using the firewall spider web interface, select . All files forwarded by a firewall to the WildFire public or private cloud for analysis are logged on the WildFire Submissions folio.

Check the WildFire verdict for a sample:

By default, simply samples that receive malicious or phishing verdicts are displayed equally

WildFire Submissions

entries. To enable logging for benign and/or grayware samples, select .

Enable logging for benign files as a quick troubleshooting step to verify that the firewall is forwarding files. Check the

WildFire Submissions

logs to verify that files are being submitted for analysis and receiving WildFire verdicts (in this instance, a benign verdict).

Ostend the analysis location for a sample:

The

WildFire Cloud

column displays the location to which the file was forwarded and where it was analyzed (public cloud or private cloud). This is useful when deploying a hybrid cloud.

glasgowintelf.blogspot.com

Source: https://docs.paloaltonetworks.com/wildfire/8-1/wildfire-admin/submit-files-for-wildfire-analysis/verify-wildfire-submissions/verify-file-forwarding

Share this post