Hey johnd, We're in the same boat. We get many vulnerability hits internally of the same type as yours. The thing to do seems to be to open a case with PAN support for each vuln. It's best to start with the ones that are blocking traffic rather than just alerting you. Then, IMHO, go for the ones that are most annoying and are most easily reproduced. PAN support will most likely ask you to reproduce the alert with packet capturing on and to add the files or other data to the case that's being transmitted when the vulnerability is identified. The end result may be surprising. We generated a case because traffic between our Microsoft SCCM servers and their clients generated many thousands of 40026: SSL Renegotiation Denial of Service vulnerabilities. We did the packet captures and submitted file samples. PAN support came back and said that, yes indeed, this is vulnerable traffic. There seemed to be no more recourse with PAN support; we could then go to Microsoft to see why they're transmitting vulnerable traffic as part of their protocols. In the end, we decided to keep the Microsoft SCCM servers running as they were and supress the alerts on the Palo Altos.
... View more