Closed FlorianHeigl closed 4 months ago
I guess per logic it would make sense to penalize un-initiated connections, vs. looking at details?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This has been closed due to inactivity. If you feel this is an error, please re-open and include a justifying comment.
As the rule is intended to be generic, it defaults to 99, but this can be changed locally according to the feeds used in your deployment, or exceptions can be added to using certain fields/categories of your threat feeds or to filter out blocked events.
Link to rule
idk
Description
This rule triggers with a very high risk score (99) I have the pfsense integration set up. In there, 'internal' networks are/can be defined. I get a high risk alert for a
blocked
event from a network (public internet side of firewall) that is not on the list of internal networks.This should be a much lower risk, as
(The 99 would make sense for something like reaching out to some beacon)
Example Data
I'm very sorry that I can't suggest a modified query, i'm not competent in most of the components that need to be touched.
(gawd, so much redundant info to sanitize)