This message was deleted.
# neuvector-security
a
This message was deleted.
q
Network rules are matched in order. Also, rules are prioritized by Federated, CRD, learned, and user created… In that order.
👍 2
Not sure if that answers your question. 🙂
f
One specific question that I have is if a certain network call is to match two deny rules, would it only fire the first one in order and stop? As per my observations, it was so and I am curious to know why would it not evaluate further into the rest of the rules.
q
Once a condition its a match, and denies on that match, the task is done. 😉
This is generally accepted practice on things like firewalls.
👍 1
This is a bit of an aside, and also different situations require different application, but it’s generally a best practice to try to employ explicit
allow
rules and let the implicit
deny
handle the rest.
f
Agreed and yes, this was a different situation where we had to explicitly define some deny rules to catch a culprit making some malicious calls 🙂
🦜 1
m
@quaint-candle-18606 Does this apply to other rule types as well? Regarding order and proritization