Palo Alto custom application signature for Referer or Origin Header access to be allowed blocked?

Announcements

Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.

Reply
NikolayDimitrov
L4 Transporter

Palo Alto custom application signature for Referer or Origin Header access to be allowed blocked?

I think that the the customer application signature using Pattern Matching and context http-req-headers or http-req-origin-headers can be used to allow URL access if the Referer or ORIGIN site is allowed. Can this be confirmed ? For blocking I think that the vulnerability signature can be made using the same context (probably the application signature can also be used but not mix things to much)?

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your 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!