Did you just run into a file that is digitally signed by Palo Alto Networks? If that's the case, please read on.
You'll probably see Palo Alto Networks when double-clicking to run the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screencap shows:
You can view the additional details from the Palo Alto Networks digital signature with the following procedure:
Here's a screenshot of a file signed by Palo Alto Networks:
As you can see in the screengrab above, Windows states that "This digital signature is OK". This means that the file has been published by Palo Alto Networks and that the file has not been tampered with.
If you click the View Certificate button shown in the screengrab above, you can examine all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, and so on. You can also examine the address for Palo Alto Networks, such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA, Symantec Class 3 SHA256 Code Signing CA, VeriSign Class 3 Code Signing 2009-2 CA and DigiCert SHA2 Assured ID Code Signing CA has issued the Palo Alto Networks certificates. You can also view the details of the issuer by clicking the View Certificate button shown in the screenshot above.
The following are the Palo Alto Networks files I've gathered, thanks to the FreeFixer users.
Detection Ratio | File Name |
---|---|
0/57 | PanGPA.exe |
0/56 | pangps.exe |
0/49 | PanCredProv.dll |
0/59 | 15136aa.rbf |
0/62 | PanGPA.exe |
0/69 | pangps.exe |
The detection percentage is based on that I've collected 352 scan results for the Palo Alto Networks files. 0 of these scan results came up with some sort of detection. You can review the full details of the scan results by examining the files listed above.
The analysis is done on certificates with the following serial numbers: