I had a problem with Vulnerability Protection profile.
I created Custom Vulnerability signature with exception for only one (1) IP address. But after upgrading to 6.1.1 version (from 6.0.5) this exception stopped working... I had to copletelywrite a new rule to exempt this IP from scanning...
The signature was based on 40015 (SSH Brute-force).
Was the configuration still present but not working or was the customization of the signature lost in the upgrade?
Either way, you should probably create a support case with this information so a bug can be logged and the upgrade issue corrected in future releases.
We have many exceptions setup in our signatures and it is NOT normal for the behavior to change in an upgrade. Based on your description, this is most likely a software bug that should be reported with a ticket to Palo Alto support.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!