Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suppress Threshold Not Working Loud Large Data Sources #73

Open
OGSteve opened this issue Aug 21, 2023 · 0 comments
Open

Suppress Threshold Not Working Loud Large Data Sources #73

OGSteve opened this issue Aug 21, 2023 · 0 comments

Comments

@OGSteve
Copy link

OGSteve commented Aug 21, 2023

During testing of multiple new fingerprinting signatures it was discovered that when the source being "fingerprinted" was sending a large amount of data, Sagan would continue to generate alerts. In my observation the rule should've generated 1 alert every 12 hours but proceeded to generate 50-100s/day. It does not appear to be completely ignoring the threshold or I would've seen millions of alerts.

Here is the rule:

alert any $HOME_NET any -> $HOME_NET any (msg:"Palo Alto device detected"; meta_content:"|2c|%sagan%|2c|",THREAT,TRAFFIC,SYSTEM; meta_content:"|2c|%sagan%|2c|",data,file,flood,packet,scan,spyware,url,virus,vulnerability,wildfire,start,end,deny,drop; meta_nocase; reference:url,docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/monitor/monitor-logs/log-types; metadata: fingerprint_source logs, fingerprint_os Palo-Alto, fingerprint_expire 86400; threshold: type suppress, track by_src, seconds 43200, count 1; classtype:fingerprint; sid:848006; rev:1;)

NOTE: This was observed in multiple environments across 2 other rules as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant