Hi @rKarki ,
Palo Alto NGFW and proxies are similar in that they are both designed to protect the network ... that is where the similarities end.
A proxy and a NGFW are 2 different things. Don't use a NGFW as a proxy 😉
I think the following pages explain the differences and why not to use your NGFW as a proxy.
Did you check this previous discussion on the same topic ? :
I am pretty sure I did read the comparison docs once before and I should have acknowledged from the start that "PAN is NGFW and a proxy is a proxy". At that time I just thought that I could easily replace proxy with PAN, but after knowing some of it's fact, I figured I was wrong. Every company's requirements are different so do we. Anyway, PAN is a great FW and I am not looking this discussion to go towards NGFW vs Proxy particularly.
Do anyone in this community care about the the http response code on the PAN URL logs? If you do and getting it today, then can you please let me know how you did it.
I found this workaround and have implemented also but the log is a bit mess. This is about creating vulnerability custom signatures and for sure, it fires up event/logs based on a traffic match. The problem that I am having with this is to create a report based on response and that is for URL (http/s) only. This is even harder from a remote log collector eg. Splunk.
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!