Cleaning security policies

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cleaning security policies

L4 Transporter


We want to do a cleaning in our security policies because we have many rules not being used and many old objects not being used in our policies. My questions are:

-There is any way to know what policies are being used and howmany matches each rule have? in order to delete the rules not used....

-There is any way to know if any object is not being used in any policy?

Thanks a lot....


L5 Sessionator


To know which rule are matched, onthe bottom of secu policy, you have "highlight unused rule", it will show you which rule never have been matched si nce the last palo reboot.

If you want you can create a custome report to knwo which rule are the most used.

for the object, for me there is nothing inside the palo to know if the object is currently used or not (or just try to delete 🙂 if it works, mean not used)

Maybe you can do that easilly but searching object name in your config file. It can be done automatically with small script

Hope help


We use Firemon exactly for this purpose. There are no "onboard" tools available for your requirements

L4 Transporter

Unfortunately this is only working on a per Rule basis. What if one object of a certain rule has never been used but all other objects in that rule have been used ? This rule will be marked as "used" Rule which is only the half of the truth.

  • 4 replies
  • 101 Subscriptions
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!