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

Auto-archive events matching filter #52

Open
jasonish opened this issue Jun 19, 2017 · 2 comments
Open

Auto-archive events matching filter #52

jasonish opened this issue Jun 19, 2017 · 2 comments
Labels

Comments

@jasonish
Copy link
Owner

Related comment:
#51 (comment)

Provide a way to auto-archive (mute) alerts probably matching a filter. Most likely SID, SID/src-ip, or SID/src-ip/dest-ip as thats the aggregation that EveBox uses.

Events matching this filter will never show up in the evebox and be archived immediately.

Easier done if the EveBox agent is used as events go through the server. Will have to be done periodically or on the fly for logstash/elasticsearch setups.

@torokp
Copy link

torokp commented Aug 16, 2017

Would be nice to have this feature "to the other direction" as well, to auto escalate an event based on a filter.

@demospace
Copy link

Just adding that the autoarchive would be a great feature for SIDs like 2402000 (Dshield, CINS, etc) which are useful in IPS mode but generate a ton of alerts that don't require investigation/follow up.

jasonish added a commit that referenced this issue Mar 30, 2022
If an event contains the alert metadata {"evebox-action": "archive"},
the server will automatically mark the event as archived.

This works in conjunction with the new (experimental) Suricata-Update
feature to add metadata using its own rule matching.

GitHub issue: #52

This is only done at the server for now and for Elasticsearch. It
requires that events be forwarded through the server and will not work
with Logstash, Filebeat, etc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants