I've run into an issue with our NGFW denying SNMPv3 trap messages passing through the firewall. I've worked around the issue by creating a policy referencing the snmpv3 app-id and a custom service of udp-162.
Has anyone else run into this and raised a request to update the snmp-trap app-id (or create and snmpv3-trap app-id) with Palo support?
Just wanting to check before I kick off that process. As I said above, I've solved the problem for the moment but SNMP v3 traps seems like something the Palo should natively support, given v3 has been around for a while.
Check the Palo Alto known issues for your version and addressed issues for newer version than yours by searching for SNMP:
From what I see in the Palo Alto app center when I search for SNMP there is no app-id for snmpv3-traps, so the snmp-trap id should match v2 or v3. If it is not a bug with your palo alto PANOS version and you have updated the "Applications and Threats Content Updates" database by using dynamic updates to the latest version then palo alto needs to fix this as this is well known application and you don't have write your own custom app-id and signature for it or use the Application Override.
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!