What do you mean with efficient? So far only this comes into my mind about something like this:
Another inefficency from a network perspective is with MTU mismatches. So could you explain a little more what you exactly want to find out?
There's several different ways to approach 'optimizing' but you'll want to figure out what does and does not benefit/require optimizing
if you have no starting point, a good way is to try determine a few 'major' avenues
-can logging be optimized (some things are chatty and may not need to be logged, like DNS), reporting can also be tuned (some default reports turned off if they're not useful)
-is traffic being discarded because of errors (take a look at switch error counters for low level issues, firewall global counters for higher level errors show counter global filter severity error (look for 'obvious' high numbers) )
-do you have a very large amount of policies that can be combined/pruned/cropped, look for 'unused' rules (PAN-OS 8.1 has a really GREAT new feature that shows rule usage)
-if you draw out your network, can it be done in a pretty straight forward design or is there "excessive" complexity you could simplify
-could some features be leveraged to 'increase' throughput for a specific flow (app override, DSRI) or 'decrease' throughput to preserve bandwidth for more important applications (QoS)
I was under the impression that the order in which you put your security policies and affect the efficiency of the flow or traffic through your firewall. So you want to put the rules that pass the most traffic at the top so it doesn't have to traverse the whole firewall, thuse making it more inefficient. We are working on reordering our rules for the best performance and to aligh with the PA best pracitces guidelines and I wondered if it is possible to get a good over idea of how we are currently doing
Very awesome points as usual reaper.
Over the three years (:O) I have been working on this PA firewall we have pruned the number of policies down from 1300 to 400. Recently we removed DNS rules from being logged, changed policies to drop instead of deny, and now we have decided to try to reorder the security rules to see if we can make the over all traffic flow more efficient, by getting the high amount of traffic throught the firewall at a higher level then making it tarverse the whole firewall. We also just got a copy of the best practices and seeing how we can use it to make our PA work better for us :).
I ran the command show counter global filter severity erro and this was an obvious high number? 15032727
session_dup_pkt_drop 15032727 5 drop session resource Duplicate packet: Applies only for multi-DP platform with hardware (Tiger) broadcasting
I was under the impression that the order in which you put your security policies and affect the efficiency of the flow or traffic through your firewall.
I don't think this is the case. I've participated in proof-of-concept testing where performance was identical whether traffic was passing through the 1st rule, or the 5000th rule.
The best practices documentation mentions rule order only so far as it matters in the evaluation of the security policy:
The order of rules (with or without zones) affects which rule is matched and what action is enforced. Grouping the rules together based on zone can help "keep things straight" and reduces the possibility that traffic flows inadvertently match an unintended rule.
To get a feel for why order isn't as significant from a performance standpoint, read-up on the use of trie structures for policy evaluation. (The first link is in reference to Palo Alto Networks firewalls, while the other two are more generalized trie+security policy articles). These should give you an idea of how a "line-by-line" policy can be compiled into a more efficient structure):
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!